public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/13509] New: Build fails because path of ranlib is hardcoded in gcc/Makefile.in
@ 2003-12-30 1:09 gcc-bugzilla-spam at pgp-keys dot net
2003-12-30 1:13 ` [Bug c++/13509] " pinskia at gcc dot gnu dot org
0 siblings, 1 reply; 2+ messages in thread
From: gcc-bugzilla-spam at pgp-keys dot net @ 2003-12-30 1:09 UTC (permalink / raw)
To: gcc-bugs
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2003-12-30 1:09 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-12-30 1:09 [Bug c++/13509] New: Build fails because path of ranlib is hardcoded in gcc/Makefile.in gcc-bugzilla-spam at pgp-keys dot net
2003-12-30 1:13 ` [Bug c++/13509] " pinskia at gcc dot gnu dot org
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).