installation script incompatibility with autoconf 2.68 on Arch Linux i686

[GoogleCodeExporter]

r21510 was fine on Arch Linux x86_64 with autoconf/autoheader 2.68 and automake 
1.11.1. However on Arch Linux i686, looks like it's incompatible with autoconf 
2.68. I got these warnings when running autogen.sh:

processing ./modules/vapor
configure.ac:365: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in 
body
../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2730: _AC_RUN_IFELSE is expanded from...
../../lib/m4sugar/m4sh.m4:606: AS_IF is expanded from...
../../lib/autoconf/general.m4:2749: AC_RUN_IFELSE is expanded from...
../../lib/m4sugar/m4sh.m4:606: AS_IF is expanded from...
../../lib/autoconf/general.m4:2032: AC_CACHE_VAL is expanded from...
../../lib/autoconf/general.m4:2053: AC_CACHE_CHECK is expanded from...
configure.ac:365: the top level
Running autoheader ...
configure.ac:365: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in 
body
../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2730: _AC_RUN_IFELSE is expanded from...
../../lib/m4sugar/m4sh.m4:606: AS_IF is expanded from...
../../lib/autoconf/general.m4:2749: AC_RUN_IFELSE is expanded from...
../../lib/m4sugar/m4sh.m4:606: AS_IF is expanded from...
../../lib/autoconf/general.m4:2032: AC_CACHE_VAL is expanded from...
../../lib/autoconf/general.m4:2053: AC_CACHE_CHECK is expanded from...
configure.ac:365: the top level
Running autoconf ...
configure.ac:365: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in 
body
../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2730: _AC_RUN_IFELSE is expanded from...
../../lib/m4sugar/m4sh.m4:606: AS_IF is expanded from...
../../lib/autoconf/general.m4:2749: AC_RUN_IFELSE is expanded from...
../../lib/m4sugar/m4sh.m4:606: AS_IF is expanded from...
../../lib/autoconf/general.m4:2032: AC_CACHE_VAL is expanded from...
../../lib/autoconf/general.m4:2053: AC_CACHE_CHECK is expanded from...
configure.ac:365: the top level

Then during compiling, when it creates symbolic links to vapor headers for 
later use, those links will be wrongly put in the --prefix location instead of 
instlinks of the build dir. For example, my --prefix=$HOME/opt, then I will see 
a lot of links under $HOME/opt/include, without sub dirs (all links are in 
include dir, no vpr-x.x.x, vrjuggler-x.x.x, etc.). Those should have been put 
in ./build/instlinks/include.

BTW I use "make optim".

It's interesting because the script works well on Arch Linux x86_64, and it has 
the same versions of autoconf/automake.

On other distros which usually use autoconf 2.65, I don't see any problem.

Original issue reported on code.google.com by sci.f...@gmail.com on 8 Oct 2010 at 4:25

[GoogleCodeExporter]

more info:

Also it could be related to Java. We have two workstations with Ubuntu 10.10 
x64 installed. autoconf is 2.67. One has sun java and it's working well, the 
other one has openjdk and the same issue occurred when compiling jccl (wrong 
symbolic links created, causing compiling failure due to missing vpr.h and 
other headers).

Then we removed openjdk and installed sun java, reboot. It compiled.

However we tried again on Arch x64. Neither sun java nor openjdk worked.

Just FYI.

Original comment by sci.f...@gmail.com on 12 Oct 2010 at 5:48

[GoogleCodeExporter]

Update:

This is not a bug, nothing to do with autoconf / java / etc.

The reason is that I set $INSTALL_PATH in .bashrc, but it may conflict with the 
var with the same name in installation script.

Once it's removed, everything is fine.

Original comment by sci.f...@gmail.com on 13 Oct 2010 at 4:54

[GoogleCodeExporter]

I'm glad to hear that this is not a build system problem. I had no idea how to 
address what was reported.

Original comment by patrick....@gmail.com on 13 Oct 2010 at 11:24

• Changed state: Invalid