public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gcc-bugzilla-spam at pgp-keys dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/13509] New: Build fails because path of ranlib is hardcoded in gcc/Makefile.in Date: Tue, 30 Dec 2003 01:09:00 -0000 [thread overview] Message-ID: <20031230005159.13509.gcc-bugzilla-spam@pgp-keys.net> (raw) 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
next reply other threads:[~2003-12-30 0:52 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-12-30 1:09 gcc-bugzilla-spam at pgp-keys dot net [this message] 2003-12-30 1:13 ` [Bug c++/13509] " pinskia at gcc dot gnu dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20031230005159.13509.gcc-bugzilla-spam@pgp-keys.net \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).