From: Matthew Woehlke <mw_triad@users.sourceforge.net>
To: gcc-help@gcc.gnu.org
Subject: Re: how to enable -m64 on x86-linux for building ATLAS
Date: Thu, 03 Apr 2008 17:22:00 -0000 [thread overview]
Message-ID: <ft32ee$j43$1@ger.gmane.org> (raw)
In-Reply-To: <fe03ae8f0804030151n1d8b18aeo2411eedcd18e102b@mail.gmail.com>
Dennis Wassel wrote:
> Fine. I'm now going to try to build a 64-bit glibc (and worry where to
> put it later, because I'm not root), and possible the full-fledged
> binutils toolchain and so on, but now I feel this
> chicken-and-egg-problem creeping up to me - wouldn't I need 64-bit
> support in my compiler to create the corresponding glibc?
>
> D'oh!
>
> Any pointers, docs or howtos anyone? Much appreciated!
It sounds like you want to look into how to build a cross-compiler. I've
never attempted to do so, but surely there is documentation on how to
bootstrap a cross compiler targeting a clean environment.
(As far a binutils, since you want cross-binutils, you are building
32-bit binaries - i.e. your existing compiler is fine - that will
generate 64-bit binaries. I'm not sure about libc, I guess it must be
possible to build a "bare metal" cross compiler that you can use to
build a libc; maybe you have to build a bare metal cross compiler first
and then a cross compiler that uses that libc.)
Apologies for the not-very-helpful answer, but maybe this will at least
point you in the right direction to go looking for further information.
--
Matthew
I don't see what C++ has to do with keeping people from shooting
themselves in the foot. C++ will happily load the gun, offer you a
drink to steady your nerves, and help you aim. -- Peter da Silva (from
cluefire.net)
next prev parent reply other threads:[~2008-04-03 17:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-03 9:02 Dennis Wassel
2008-04-03 10:27 ` Andrew Haley
2008-04-03 17:22 ` Matthew Woehlke [this message]
2008-04-05 5:40 ` Brian Dessent
2008-04-05 13:01 ` Dennis Wassel
2008-04-05 23:53 ` Brian Dessent
2008-04-06 6:37 ` Brian Dessent
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='ft32ee$j43$1@ger.gmane.org' \
--to=mw_triad@users.sourceforge.net \
--cc=gcc-help@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).