public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dougsemler at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/40125] libgcc_s DLL installed in wrong directory in cross toolchain Date: Fri, 16 Apr 2010 14:53:00 -0000 [thread overview] Message-ID: <20100416145317.17287.qmail@sourceware.org> (raw) In-Reply-To: <bug-40125-230@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from dougsemler at gmail dot com 2010-04-16 14:53 ------- Right now in a cross environment, the target libraries, when built as DLLs, are also installed in the host's bindir, due to the -bindir flag now being passed to libtool. While this may be appropriate in a native compiler case, I don't think it's right in a cross environment. My opinion is that in a cross environment, the -bindir parameter should be $(toolexeclibdir), and not $(bindir). This will expand to exec_prefix/target/lib/MULTIOSSUBDIR or gcc's private dir/MULTISUBDIR when version-specific-runtime is specified. This places the DLLs in the same structure as their matching .dll.a files and separates the libs properly on multilib 64 bit mingw. I think, in a cross environment, libgcc_s should also follow this convention :) -- dougsemler at gmail dot com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dougsemler at gmail dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40125
next prev parent reply other threads:[~2010-04-16 14:53 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-05-12 20:07 [Bug target/40125] New: " jsm28 at gcc dot gnu dot org 2009-08-12 22:14 ` [Bug target/40125] " davek at gcc dot gnu dot org 2009-08-12 22:57 ` davek at gcc dot gnu dot org 2009-08-13 6:08 ` ktietz at gcc dot gnu dot org 2010-04-16 14:53 ` dougsemler at gmail dot com [this message] [not found] <bug-40125-4@http.gcc.gnu.org/bugzilla/> 2010-11-28 1:43 ` davek at gcc dot gnu.org 2010-12-04 0:29 ` davek at gcc dot gnu.org 2010-12-06 0:50 ` davek at gcc dot gnu.org 2010-12-06 0:54 ` davek at gcc dot gnu.org 2011-01-26 4:50 ` davek at gcc dot gnu.org 2011-02-02 18:05 ` dnovillo at gcc dot gnu.org 2011-02-02 18:05 ` dnovillo at gcc dot gnu.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=20100416145317.17287.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).