This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/13509] New: Build fails because path of ranlib is hardcoded in gcc/Makefile.in
- From: "gcc-bugzilla-spam at pgp-keys dot net" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 30 Dec 2003 00:52:00 -0000
- Subject: [Bug c++/13509] New: Build fails because path of ranlib is hardcoded in gcc/Makefile.in
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
My brand new ranlib (binutils 2.14) is installed in /usr/local/,
but in gcc/Makefile.in (and resulting Makefile) the path is hardcoded to
[ -f /usr/bin/ranlib -o -f /bin/ranlib ] ( line 241 )
Makefile tries to compensate by trying to do what ranlib does, but fails.
Note: by default binutils is compiled and installed to /usr/local/
if the machine has 'which', i would try a `which ranlib` when setting
RANLIB_FOR_TARGET instead of `echo ranlib` (so -f $(RANLIB_FOR_TARGET) would
work in line 239 of gcc/Makefile.in)
--
Summary: Build fails because path of ranlib is hardcoded in
gcc/Makefile.in
Product: gcc
Version: 3.3.2
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: gcc-bugzilla-spam at pgp-keys dot net
CC: gcc-bugs at gcc dot gnu dot org
GCC host triplet: any host with binutils (and specific ranlib) in
/usr/local/bin
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13509