You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@apr.apache.org by "Hyrum K. Wright" <hy...@mail.utexas.edu> on 2010/03/11 18:34:04 UTC
1.4.x build problem on OS X (bad libtool path)
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.
-Hyrum
Re: 1.4.x build problem on OS X (bad libtool path)
Posted by Dan Poirier <po...@pobox.com>.
On Thu, 11 Mar 2010 13:24 -0500, "Dan Poirier" <po...@pobox.com>
wrote:
> On Thu, 11 Mar 2010 11:34 -0600, "Hyrum K. Wright"
> <hy...@mail.utexas.edu> wrote:
> > 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
>
> https://issues.apache.org/bugzilla/show_bug.cgi?id=48776
>
> I've provided a patch that works for me, waiting for someone to look at
> it and hopefully commit it.
Actually that might be a different problem... ran out of time to check.
Re: 1.4.x build problem on OS X (bad libtool path)
Posted by Dan Poirier <po...@pobox.com>.
On Thu, 11 Mar 2010 11:34 -0600, "Hyrum K. Wright"
<hy...@mail.utexas.edu> wrote:
> 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
https://issues.apache.org/bugzilla/show_bug.cgi?id=48776
I've provided a patch that works for me, waiting for someone to look at
it and hopefully commit it.
Dan