public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "felipe dot contreras at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/44803] LIBRARY_PATH should work on cross-compilers Date: Fri, 06 Aug 2010 07:08:00 -0000 [thread overview] Message-ID: <20100806070809.31250.qmail@sourceware.org> (raw) In-Reply-To: <bug-44803-19398@http.gcc.gnu.org/bugzilla/> [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 1220 bytes --] ------- Comment #2 from felipe dot contreras at gmail dot com 2010-08-06 07:08 ------- (In reply to comment #1) > ? (you have to give some more details) What exactly do you need? >From the manpage LIBRARY_PATH The value of LIBRARY_PATH is a colon-separated list of directories, much like PATH. When configured as a native compiler, GCC tries the directories thus specified when searching for special linker files, if it cant find them using GCC_EXEC_PREFIX. Linking using GCC also uses these directories when searching for ordinary libraries for the -l option (but directories specified with -L come first). I confirm that LIBRARY_PATH is ignored by CodeSourcery cross-compiler, and I don't see why. Wouldn't LIBRARY_PATH be specially useful for cross-comilation? -- felipe dot contreras at gmail dot com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|unassigned at gcc dot gnu |felipe dot contreras at |dot org |gmail dot com Status|WAITING |UNCONFIRMED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44803
next prev parent reply other threads:[~2010-08-06 7:08 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-07-03 13:18 [Bug c/44803] New: " felipe dot contreras at gmail dot com 2010-07-03 21:28 ` [Bug c/44803] " rguenth at gcc dot gnu dot org 2010-08-06 7:08 ` felipe dot contreras at gmail dot com [this message] [not found] <bug-44803-4@http.gcc.gnu.org/bugzilla/> 2010-09-27 10:48 ` felipe.contreras at gmail dot com
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=20100806070809.31250.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).