| View previous topic :: View next topic |
| Author |
Message |
chatgris
Guru
Joined: 14 Oct 2002
Posts: 383
Location: Canada
|
 Posted: Mon Jan 27, 2003 9:12 am Post subject: autoconf bug when running php's buildconf.. help! |
 |
|
ok I'm attempting to create an extension to php... my only problem is that fcor some reason, on my php box, buildconf always gives this output
| Code: | using default Zend directory
buildconf: checking installation...
buildconf: autoconf version 2.13 (ok)
buildconf: automake version 1.4-p5 (ok)
buildconf: libtool version 1.4.2 (ok)
rebuilding configure
configure.in:562: AC_TRY_COMPILE was called before AC_AIX
configure.in:562: AC_TRY_RUN was called before AC_AIX
configure.in:562: AC_TRY_COMPILE was called before AC_AIX
configure.in:562: AC_TRY_RUN was called before AC_AIX
autoconf: Undefined macros:
***BUG in Autoconf--please report*** AC_ACVERSION
***BUG in Autoconf--please report*** AC_TRY_DLOPEN_SELF
***BUG in Autoconf--please report*** AC_TRY_DLOPEN_SELF
***BUG in Autoconf--please report*** AC_TRY_DLOPEN_SELF
***BUG in Autoconf--please report*** AC_TRY_DLOPEN_SELF
***BUG in Autoconf--please report*** AC_TRY_DLOPEN_SELF
***BUG in Autoconf--please report*** AC_TRY_DLOPEN_SELF
***BUG in Autoconf--please report*** AC_TRY_DLOPEN_SELF
***BUG in Autoconf--please report*** AC_TRY_DLOPEN_SELF
rebuilding main/php_config.h.in
configure.in:562: AC_TRY_COMPILE was called before AC_AIX
configure.in:562: AC_TRY_RUN was called before AC_AIX
configure.in:562: AC_TRY_COMPILE was called before AC_AIX
configure.in:562: AC_TRY_RUN was called before AC_AIX |
and after that I get a syntax error in the configure.
On my redhat box, it works fine.. I tried emerging libtool 1.4.2 as the redhat box had to no avail.. I tried upgrading to the latest version of autconf (2.57) and still the exact same problem... I get all those warnings and bug reports, and my configure craps out.
If anyone has ANY idea why this isn't working please add some comments.. I've been banging my head against a wall abotu this for 5 hours now.
Yet on my redhat box, I attempted to 
_________________
Open your mind. Open your source.
Due credit for avatar from http://www.aikida.net |
|
| Back to top |
|
 |
kutsuya
Retired Dev
Joined: 21 Oct 2002
Posts: 189
|
| Posted: Mon Jan 27, 2003 9:48 am Post subject: autoconf version problems? |
|
|
I have the latest autoconf-2.54 emerged but:
| Code: |
kutsuya root # autoconf --version
Autoconf version 2.13
|
It you get the same results, maybe that is the problem. Follow the link to find a solution. autoconf version mismatch?
_________________
--Kutsuya |
|
| Back to top |
|
|
chatgris
Guru
Joined: 14 Oct 2002
Posts: 383
Location: Canada
|
| Posted: Mon Jan 27, 2003 10:14 am Post subject: |
|
|
THANK YOU!!
I actually did search earlier, but I read a post that said it didn't matter if autoconf said 2.13 since it auto canged due to the suffix of a filename... but that was definately the problem..
THANKS! 
***EDIT***
I also noticed that you just switched over to apprentice... congrats =)
_________________
Open your mind. Open your source.
Due credit for avatar from http://www.aikida.net |
|
| Back to top |
|
|
kutsuya
Retired Dev
Joined: 21 Oct 2002
Posts: 189
|
| Posted: Mon Jan 27, 2003 11:23 pm Post subject: |
|
|
| chatgris wrote: | THANK YOU!!
I actually did search earlier, but I read a post that said it didn't matter if autoconf said 2.13 since it auto canged due to the suffix of a filename... but that was definately the problem..
|
You are welcome. Glad that was able to fixed the problem. I think I've heard it can change modes also, but I don't really know and don't know the exceptions. So, I'd force it into a known state.
| chatgris wrote: |
I also noticed that you just switched over to apprentice... congrats =) |
Thanks. =) Got there quicker than expected. Looks like you are only 9 post away from joining the rank . 
_________________
--Kutsuya |
|
| Back to top |
|
|
|
Portage & Programming
