From: Andreas Schwab <schwab@linux-m68k.org>
To: Nick Alcock via Binutils <binutils@sourceware.org>
Subject: Re: how should I configure my buuild for i386-*linux*
Date: Sat, 07 May 2022 16:21:58 +0200 [thread overview]
Message-ID: <87y1zdh189.fsf@igel.home> (raw)
In-Reply-To: <87sfpl8o7s.fsf@esperi.org.uk> (Nick Alcock via Binutils's message of "Sat, 07 May 2022 14:30:15 +0100")
On Mai 07 2022, Nick Alcock via Binutils wrote:
> Thankfully the answer is pretty simple. Try configuring like this:
>
> configure CC="gcc -m32" ...
That would would conflict with the value of the --host option.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2022-05-07 14:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 23:31 Vladimir Mezentsev
2022-05-03 23:42 ` Matthias Klose
2022-05-04 7:29 ` Vladimir Mezentsev
2022-05-07 13:30 ` Nick Alcock
2022-05-07 14:21 ` Andreas Schwab [this message]
2022-05-09 12:01 ` Nick Alcock
2022-05-09 12:13 ` Christian Groessler
2022-05-17 12:33 ` Nick Alcock
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=87y1zdh189.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=binutils@sourceware.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).