public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: FX Coudert <fxcoudert@gmail.com>
To: gcc-help@gcc.gnu.org
Cc: mingw-w64-public@lists.sourceforge.net
Subject: Re: Cross-build for x86_64-pc-mingw32
Date: Sat, 01 Dec 2007 18:39:00 -0000	[thread overview]
Message-ID: <57AF140A-DB8A-4A06-9927-1CE74793959C@gmail.com> (raw)
In-Reply-To: <47519B7A.C4E7AC23@dessent.net>

> That error means that something went wrong earlier.  Look upwards at
> config.log and you will see somewhere that it tried to do a link test
> that fails, typically due to missing or improper crt*.o, and thus  
> it set
> the NO_EXECUTABLES flag.  From that point on, the next test that tries
> to link something will give that error, but the problem was whatever
> test failed originally.  The details should all be in config.log.

OK, thanks a lot for the explanation. I grepped for gcc_no_link and  
found that crt2.o was not found, because the latest mingw-win64 crt  
puts it in lib64/ while GCC expect it to be in lib/. That brings two  
questions: 1. is the lib64/ choice final, and should GCC be modified  
to find libraries there? 2. has there been any attempt at building a  
multilib -m32/-m64 mingw compiler?

Thanks,
FX

  reply	other threads:[~2007-12-01 18:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <19c433eb0711300950r43f1ccffi28ef6b7a2e51548d@mail.gmail.com>
     [not found] ` <b609cb3b0711301053g178ed7c7pb7f225f3579a4591@mail.gmail.com>
2007-12-01 17:23   ` FX Coudert
2007-12-01 17:36     ` Brian Dessent
2007-12-01 18:39       ` FX Coudert [this message]
2007-12-01 20:50         ` NightStrike
     [not found]         ` <4751c936.073a360a.4d2f.ffffd1bfSMTPIN_ADDED@mx.google.com>
2007-12-01 21:09           ` FX Coudert
2007-12-02 17:23             ` NightStrike
2007-12-02 17:37               ` FX Coudert
2007-12-23 19:54                 ` NightStrike

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=57AF140A-DB8A-4A06-9927-1CE74793959C@gmail.com \
    --to=fxcoudert@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=mingw-w64-public@lists.sourceforge.net \
    /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).