apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hyrum K. Wright" <hyrum_wri...@mail.utexas.edu>
Subject 1.4.x build problem on OS X (bad libtool path)
Date Thu, 11 Mar 2010 17:34:04 GMT
I realize folks are trying to get 1.4.2 out the door, so I'm sorry for the late arrival of
my various bugs.

When building an unmodified checkout of the 1.4.x branch, I get the following:

$ ./buildconf
$ ./configure
$ make
$ make
/bin/sh /libtool --silent --mode=compile gcc -g -O2   -DHAVE_CONFIG_H -DDARWIN -DSIGPROCMASK_SETS_THREAD_MASK
-no-cpp-precomp   -I./include -I/Users/Hyrum/dev/apr-1.4.x/include/arch/unix -I./include/arch/unix
-I/Users/Hyrum/dev/apr-1.4.x/include/arch/unix -I/Users/Hyrum/dev/apr-1.4.x/include  -o passwd/apr_getpass.lo
-c passwd/apr_getpass.c && touch passwd/apr_getpass.lo
/bin/sh: /libtool: No such file or directory
make[1]: *** [passwd/apr_getpass.lo] Error 127
make: *** [all-recursive] Error 1

Looking in build/apr_rules.mk, I see:
LIBTOOL=$(SHELL) $(top_builddir)/libtool

but it turns out that top_builddir is not defined, leading to the expansion resulting in:
/bin/sh /libtool

which causes the build failure.

IO trunk, the build succeeds, and the same line in build/apr_rules.mk is:
LIBTOOL=$(SHELL) $(apr_builddir)/libtool

If I modify apr_rules.mk on the 1.4.x branch to use apr_builddir instead of top_builddir,
everything works as expected.  I haven't yet determined where in the maze of m4 macros where
the LIBTOOL variable is set, so I'm posting here to see if somebody knows more.

View raw message