public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ktietz at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/47142] incorrect libgcc_s_sjlj-1.dll install
Date: Fri, 04 Feb 2011 09:34:00 -0000 [thread overview]
Message-ID: <bug-47142-4-71NOaB5u5m@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47142-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47142
--- Comment #4 from Kai Tietz <ktietz at gcc dot gnu.org> 2011-02-04 09:33:58 UTC ---
Could you please check if this patch solves the issue for multilib? (It treats
multilib scenario like cross for installation of dll files).
Index: config.gcc
===================================================================
--- config.gcc (revision 169824)
+++ config.gcc (working copy)
@@ -1489,7 +1489,19 @@
fi
# Shared libgcc DLL install dir depends on cross/native build.
if test x${host} = x${target} ; then
- tmake_dlldir_file="i386/t-dlldir"
+ # Are we building multilib version?
+ if test x$enable_targets = xall; then
+ case ${target} in
+ *-w64-*)
+ tmake_dlldir_file="i386/t-dlldir-x"
+ ;;
+ *)
+ tmake_dlldir_file="i386/t-dlldir"
+ ;;
+ esac
+ else
+ tmake_dlldir_file="i386/t-dlldir"
+ fi
else
tmake_dlldir_file="i386/t-dlldir-x"
fi
next prev parent reply other threads:[~2011-02-04 9:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-01 4:15 [Bug c/47142] New: " dongsheng.song at gmail dot com
2011-02-03 18:01 ` [Bug target/47142] " ktietz at gcc dot gnu.org
2011-02-04 0:10 ` dongsheng.song at gmail dot com
2011-02-04 1:34 ` dongsheng.song at gmail dot com
2011-02-04 9:34 ` ktietz at gcc dot gnu.org [this message]
2011-02-04 13:29 ` dongsheng.song at gmail dot com
2011-02-04 14:27 ` dongsheng.song at gmail dot com
2011-02-04 15:54 ` ktietz at gcc dot gnu.org
2011-02-04 16:05 ` dongsheng.song 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=bug-47142-4-71NOaB5u5m@http.gcc.gnu.org/bugzilla/ \
--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: link
Be 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).