GNU bug report logs -
#11642
Libtool cannot find executables
Previous Next
To reply to this bug, email your comments to 11642 AT debbugs.gnu.org.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-libtool <at> gnu.org
:
bug#11642
; Package
libtool
.
(Thu, 07 Jun 2012 00:46:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Paul Barker <paul <at> paulbarker.me.uk>
:
New bug report received and forwarded. Copy sent to
bug-libtool <at> gnu.org
.
(Thu, 07 Jun 2012 00:46:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
Hi,
Libtools cannot find executables which are on my $PATH. This happens
when cross compiling two different packages, libsndfile-1.0.25 and
alsa-lib-1.0.25 (matching version numbers is coincidental). During
'make' everything runs fine, but both packages attempt to run additional
commands during 'make install' which seem not to belong in the install
phase. For libsndfile, libtool attempts to execute
arm-angstrom-linux-gnueabi-ranlib, my cross ranlib, but cannot find it.
For alsa-lib, libtool attempts to execute arm-angstrom-linux-gnueabi-gcc
but again cannot find it, despite the fact that it has been executing
the command correctly throughout the build of the library. My path is
set in ~/.bash_profile and is exported. My only guess is that libtool is
unsetting my $PATH variable during the install phase, but I may be very
wrong.
Thanks,
Paul Barker
This bug report was last modified 13 years and 11 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.