public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/22330] Building a cross linux->win32 incorrectly sets HAVE_GAS_SHF_MERGE true
Date: Wed, 17 Aug 2005 03:30:00 -0000	[thread overview]
Message-ID: <20050817032940.29827.qmail@sourceware.org> (raw)
In-Reply-To: <20050706210825.22330.ovidr@users.sourceforge.net>


------- Additional Comments From pinskia at gcc dot gnu dot org  2005-08-17 03:29 -------
(In reply to comment #7)
> I don't know how to do that with the current configure.
> 
> Build != Host 
> --build=i686-pc-linux-gnu --host=i686-pc-mingw32 --target=i686-pc-mingw32
> 
> From configure.ac:
> # If build != host, and we aren't building gas in-tree, we identify a
> # build->target assembler and hope that it will have the same features
> # as the host->target assembler we'll be using.
> 
> (which is wrong in this case)

Actually it better or there is something wrong as basicially you cannot really mix match the as versions 
of a Candian cross.

-- 


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


  parent reply	other threads:[~2005-08-17  3:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-06 21:08 [Bug other/22330] New: " ovidr at users dot sourceforge dot net
2005-07-06 21:10 ` [Bug libgcj/22330] " pinskia at gcc dot gnu dot org
2005-07-07 15:31 ` [Bug java/22330] " pinskia at gcc dot gnu dot org
2005-07-07 15:34 ` pinskia at gcc dot gnu dot org
2005-07-07 16:56 ` pinskia at gcc dot gnu dot org
2005-07-07 17:15 ` pinskia at gcc dot gnu dot org
2005-07-07 17:19 ` pinskia at gcc dot gnu dot org
2005-07-07 21:24 ` [Bug bootstrap/22330] " ovidr at users dot sourceforge dot net
2005-08-17  3:30 ` pinskia at gcc dot gnu dot org [this message]
     [not found] <bug-22330-7936@http.gcc.gnu.org/bugzilla/>
2005-11-04  6:41 ` membar at gcc dot gnu dot org
2008-01-26 12:04 ` rguenth 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=20050817032940.29827.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).