public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "Ralf dot Wildenhues at gmx dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/5291] Bad reference to build directory in libstdc++.la Date: Tue, 28 Feb 2006 16:53:00 -0000 [thread overview] Message-ID: <20060228162910.18242.qmail@sourceware.org> (raw) In-Reply-To: <bug-5291-50@http.gcc.gnu.org/bugzilla/> ------- Comment #16 from Ralf dot Wildenhues at gmx dot de 2006-02-28 16:29 ------- (In reply to comment #15) > > I see the same thing without the patch in the installed libstdc++.la. > The real kicker is that the -L's for the build directory come before > the -L's for the install directory. For an install, the order should > be reveresed. No. The link paths to the build tree should not be present at all. > > Also, there are an amazing number of -lm's and -lgcc_s's that are unnecessary. > It's my understanding that the extra -lm's and -lgcc_s's are added to > handle cyclical dependencies. These may not be present on all systems. Correct on both accounts. The repetitions are harmless as long as they do not pose a line length issue. I believe a newer Libtool should produce less of those. But it will (not yet) fix the build tree references issue. Cheers, Ralf -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=5291
next prev parent reply other threads:[~2006-02-28 16:29 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-5291-50@http.gcc.gnu.org/bugzilla/> 2005-11-04 1:13 ` pinskia at gcc dot gnu dot org 2005-12-12 16:54 ` Ralf dot Wildenhues at gmx dot de 2006-02-26 5:56 ` pinskia at gcc dot gnu dot org 2006-02-27 22:29 ` quanah at stanford dot edu 2006-02-28 16:00 ` dave at hiauly1 dot hia dot nrc dot ca 2006-02-28 16:53 ` Ralf dot Wildenhues at gmx dot de [this message] 2007-02-19 16:42 ` schwab at suse dot de 2007-02-22 8:58 ` peb at mppmu dot mpg dot de 2007-02-22 15:59 ` bfriesen at simple dot dallas dot tx dot us 2007-04-03 9:24 ` peb at mppmu dot mpg dot de 2007-04-03 9:27 ` peb at mppmu dot mpg dot de 2007-04-03 9:28 ` peb at mppmu dot mpg dot de 2007-04-03 9:29 ` peb at mppmu dot mpg dot de 2007-10-23 19:11 ` geir at cray dot com 2007-10-23 20:11 ` dave at hiauly1 dot hia dot nrc dot ca 2007-12-01 15:00 ` pcarlini at suse dot de 2007-12-03 10:18 ` bonzini at gnu dot org 2007-12-03 12:57 ` peb at mppmu dot mpg dot de 2007-12-03 13:18 ` bonzini at gnu dot org 2009-01-26 23:31 ` bkoz at gcc dot gnu dot org [not found] <20020106074600.5291.schwab@suse.de> 2003-07-22 2:59 ` pinskia at physics dot uc dot edu 2003-08-06 0:46 ` pinskia at physics dot uc dot edu 2004-05-01 21:42 ` pinskia at gcc dot gnu dot org 2004-05-02 17:01 ` danglin at gcc dot gnu dot org 2004-05-02 17:13 ` danglin at gcc dot gnu dot org 2004-05-03 4:18 ` aoliva at gcc dot gnu dot org 2004-09-09 2:32 ` pinskia at gcc dot gnu dot org 2005-07-01 16:24 ` peb at mppmu dot mpg dot de
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=20060228162910.18242.qmail@sourceware.org \ --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).