From: Segher Boessenkool <segher@kernel.crashing.org>
To: Sidney Cadot <sidney@jigsaw.nl>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Preventing a biarch build
Date: Sun, 25 Jun 2006 13:40:00 -0000 [thread overview]
Message-ID: <C3628138-A716-47C7-8711-510CECCFE0BE@kernel.crashing.org> (raw)
In-Reply-To: <AEE6FC30-5B55-49E4-8954-8480449C65CA@jigsaw.nl>
> When bootstrapping gcc 4.1.1 on my AMB64 system, I run into some
> troubles that seem to be connected to the linker not finding 32-bit
> versions of some libraries by the available C compiler (gcc 4.0.3
> on Kubuntu). This is the place where the make process breaks down:
> As I am not really interested in the biarch capability anyway, I am
> looking for a way to direct the bootstrap process to skip all that
> and just build me a 64-bit capable compiler. Ideally, there would
> be a ./configure flag to prevent building a biarch compiler.
>
> I looked in the docs but I cannot find an easy way to do this.
--disable-multilib
Segher
prev parent reply other threads:[~2006-06-25 13:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-25 11:43 Sidney Cadot
2006-06-25 13:40 ` Segher Boessenkool [this message]
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=C3628138-A716-47C7-8711-510CECCFE0BE@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=gcc-help@gcc.gnu.org \
--cc=sidney@jigsaw.nl \
/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).