public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "eric at ecentral dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/14316] collect2 doesnt build on windows hosts
Date: Fri, 19 Mar 2004 21:49:00 -0000	[thread overview]
Message-ID: <20040319214906.17529.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040227020715.14316.droopycom@yahoo.com>


------- Additional Comments From eric at ecentral dot com  2004-03-19 21:49 -------
(In reply to comment #10)
> Subject: Re:  collect2 doesnt build on windows hosts
> I see code to disable building fixincl if build != host (unless
> --with-sysroot is specified).  But I don't see any code to disable
> building fixincl if build == host and host != target.  So it seems to
> me that building a cross-compiler from mingw32 to something else, and
> doing the build on mingw32, will cause this problem.
> To me it seems reasonable to build fixincl whenever we have header
> files to fix.  <snip>
> Ian

How does one determine if there are header files to fix for a particular host 
and target? (and/or where does gcc determine this?)

Also, FYI, I can't test Ian's patch because it doesn't patch against a recent 
3.4 snapshot (20040310).

Thanks
Eric


-- 


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


  parent reply	other threads:[~2004-03-19 21:49 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-27  2:07 [Bug c/14316] New: " droopycom at yahoo dot com
2004-02-27  2:52 ` [Bug bootstrap/14316] " pinskia at gcc dot gnu dot org
2004-03-13  6:43 ` eric at ecentral dot com
2004-03-16 14:07 ` wintermute2k4 at ntlworld dot com
2004-03-17 15:06 ` eric at ecentral dot com
2004-03-17 15:47 ` ian at wasabisystems dot com
2004-03-17 17:04 ` eric at ecentral dot com
2004-03-17 17:13 ` ian at wasabisystems dot com
2004-03-17 17:49 ` eric at ecentral dot com
2004-03-17 20:30 ` zack at codesourcery dot com
2004-03-17 20:39 ` ian at wasabisystems dot com
2004-03-17 20:56 ` zack at codesourcery dot com
2004-03-18 20:23 ` ian at wasabisystems dot com
2004-03-19 21:49 ` eric at ecentral dot com [this message]
2004-03-19 22:50 ` ian at wasabisystems dot com
2004-03-20  0:14 ` eric at ecentral dot com
2004-06-18  4:29 ` pinskia at gcc dot gnu dot org
2004-10-14  1:07 ` aaronavay62 at aaronwl dot com
2004-10-14 11:28 ` dannysmith at users dot sourceforge dot net
2005-03-01  6:06 ` aaronavay62 at aaronwl dot com
2005-03-29 19:39 ` cvs-commit at gcc dot gnu dot org
2005-04-03 14:40 ` ian at airs dot com
2005-04-03 16:53 ` pinskia 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=20040319214906.17529.qmail@sources.redhat.com \
    --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).