Configure broken on python check #384
Comments
ghost
assigned 
|
@coolwanglu @JoesCat could this have been caused by your recent merges? |
|
I saw it on ubuntu 12.04, then fixed it by installing pkg-config or something, let me check now. |
|
This is on Fedora 18, and I had build FF last week successfully on this machine. |
|
Did you see any error of |
|
AFAIK, PKG_CHECK_MODULES should appear in |
|
Yes, actually there is an error in autogen.sh: |
|
Yes, that was exactly what I have seen. Not sure what I have done to remove them.. |
|
Hmm! https://github.com/fontforge/fontforge/blame/master/autogen.sh says this file was last changed 6 months ago.. |
|
I thinks it's about On Wed, Mar 6, 2013 at 12:29 AM, Dave Crossland notifications@github.comwrote:
|
|
Yes, sorry, https://github.com/fontforge/fontforge/blame/master/configure.ac says these parts of the file were last changed 6 months ago.. |
|
Hmm well I guess it was introduced by @JoesCat - could you take a look? :) |
|
We can pretty well leave autoconf.sh alone, if you go upstream, it's pretty-close to the identical file. I don't see this error appear on my machine, perhaps because it is an older Mageia 1 while some of the things mentioned below suggest this is possibly more recent events. Typing "AC_FUNC_REALLOC" brings-up several things. If it's old, like 2004, it is maybe useful: I've added a pullrequest but you need to try it first since I can't see this problem. |
|
refreshed directory - no complaints from sh autogen.sh Tried "./configure --disable-python-scripting --disable-python-extension" and no errors. |
|
Note that before the error details, there is So the later messages should come from What do you get from |
|
Nothing appears to stand-out - this is literally what I got now when doing autoreconf -i -f libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, |
|
I guess @davelab may see some error output from this command. On Wed, Mar 6, 2013 at 10:02 AM, Joe notifications@github.com wrote:
|
|
Yep :( |
|
@davelab6 |
|
I have it. |
|
My suggestion is to run |
|
|
I've no idea right now :( Probably #245 is related? |
|
On a fresh Fedora 18 LXDE 64bit, with the fix in #245 |
|
@coolwanglu Thanks for figuring this out - will need to wait for Dave to confirm if it's #245 that needs to be included. |
|
As you can see above, I have the same versions of autotools (or higher) than you: I have that package installed: I will try with a fresh install. |
|
oops, I was looking at @JoesCat 's log... |
|
how about a clean git clone first |
|
Hi Dave, I tried a live Mageia3 seems to work okay. However, I did preload several libraries before starting since I was not about to install it yet, therefore I did not actually exercise the possibility of "something not found" causing an error. In your error, if you notice the "...syntax error near unexpected token..." in your error message and reading a variety of other people's messages seems to suggest PKG_CHECK_MODULES() has an issue in not finding something if it is not in an expected location and then borking. Here's one example, but there are more: Simply typing PKG_CHECK_MODULES into google seems to bring up problems and issues instead of a definition, so it may be suspect. Use a fresh git clone My suggested preload...libpangox libcairo autogen automake autoconf make libtool gcc libltdl gettext (note, choose developer versions if you get a choice of packages since you need header info to build FF). |
|
I simply use On Thursday, March 7, 2013, Joe wrote:
|
|
@JoesCat From the error message you can see that PKG_CHECK_MODULES appears in configure, which should have been substituted by autoreconf. I guess you cannot see this macro in your configure |
|
I am getting the same build error |
|
My autoconf,automake,libtool versions: |
|
I am also having the same issue My code base is latest. @davelab6 are you still facing the issue or is it resolved? |
|
On May 22, 2013 04:33:21 AM Ramesh Vel wrote:
Apparently not resolved if you have this issue. Which distro are you using? I'm guessing autoconf 2.69 instead of 2.68 or lower. Did you run sh autogen.sh first? I think it takes care of a few deficiencies |
|
@JoesCat with autoconf 2.68 and automake 1.11.3 - I got the exception Then I have compiled & installed autoconf 2.69 - and tried fontforge, got the same exception. But when i checked, automake 1.11.4 is the latest. So i removed automake by And tried fontforge again. It worked. I really dont understand how install & uninstall of automake 1.11.4 solved this issue. |
|
Is "got the old 1.11.3 version back" the actual solution to solve this problem? I bumped into the same issue and tried to install/uninstall automake 1.11.3 but it still failed. Couldn't figure out how to move on. Any advice would be really really appreciated . |
This should fix fontforge#384 in terms of AC_FUNC_MALLOC and AC_FUNC_REALLOC so if someone runs autoscan it won't get re-inserted to test for this again.
This should fix fontforge#384 in terms of AC_FUNC_MALLOC and AC_FUNC_REALLOC so if someone runs autoscan it won't get re-inserted to test for this again.
The "python" program to build these files contributed to a headache worth of problems earlier between 2012 and 2014 when Fontforge built python as an "optional" choice and not a "forced" dependency. Removing the python program allowed us to continue onto 20140101 and onwards... Example problems/issues fontforge#384, fontforge#387, fontforge#229, fontforge#565, fontforge#382, fontforge#241, fontforge#249, fontforge#233 makeutype.c already uses the Unicode list, so it can do this here too.
The "python" program to build these files contributed to a headache worth of problems earlier between 2012 and 2014 when Fontforge built python as an "optional" choice and not a "forced" dependency. Removing the python program allowed us to continue onto 20140101 and onwards... Example problems/issues fontforge#384, fontforge#387, fontforge#229, fontforge#565, fontforge#382, fontforge#241, fontforge#249, fontforge#233 makeutype.c already uses the Unicode list, so it can do this here too.
FontForge won't build for me right now, giving a python error:
The text was updated successfully, but these errors were encountered: