public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nightstrike at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/38294] Enable multilib support for mingw
Date: Fri, 06 Feb 2009 04:21:00 -0000	[thread overview]
Message-ID: <20090206042131.16314.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38294-14772@http.gcc.gnu.org/bugzilla/>



------- Comment #11 from nightstrike at gmail dot com  2009-02-06 04:21 -------
Created an attachment (id=17259)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=17259&action=view)
Kai's attempt

This patch has a few caveats:

You can't use the winsup link hack to work around the issue that Corinna
injected, so you can't build libstdc++, so you can't build g++

Also, the lib directories are all fubared because of ld not allowing custom
default lib paths (it's hard coded to use /root/target/lib):
1) x86_64-pc-mingw32/lib remains the place for 64-bit mingw objects
and libraries
2) x86_64-pc-mingw32/lib64 is a link to x86_64-pc-mingw32/lib
3) x86_64-pc-mingw32/lib32 is the place for 32-bit mingw


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38294


  parent reply	other threads:[~2009-02-06  4:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-27 17:42 [Bug other/38294] New: " nightstrike at gmail dot com
2008-11-27 17:42 ` [Bug other/38294] " nightstrike at gmail dot com
2008-11-27 17:45 ` nightstrike at gmail dot com
2008-12-08  7:50 ` [Bug target/38294] " nightstrike at gmail dot com
2008-12-08 20:18 ` ktietz at gcc dot gnu dot org
2008-12-13 21:20 ` nightstrike at gmail dot com
2008-12-13 21:48 ` ktietz at gcc dot gnu dot org
2008-12-13 22:01 ` nightstrike at gmail dot com
2008-12-13 23:02 ` nightstrike at gmail dot com
2008-12-14  0:12 ` nightstrike at gmail dot com
2008-12-14  5:56 ` dannysmith at users dot sourceforge dot net
2008-12-14  7:51 ` ktietz at gcc dot gnu dot org
2009-02-06  4:21 ` nightstrike at gmail dot com [this message]
2009-08-31 19:49 ` ktietz at gcc dot gnu dot org
2009-08-31 19:52 ` ktietz 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=20090206042131.16314.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: 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).