From: Andrew Haley <aph@redhat.com>
To: Dennis Wassel <dennis.wassel@googlemail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: how to enable -m64 on x86-linux for building ATLAS
Date: Thu, 03 Apr 2008 10:27:00 -0000 [thread overview]
Message-ID: <47F49CF4.4060807@redhat.com> (raw)
In-Reply-To: <fe03ae8f0804030151n1d8b18aeo2411eedcd18e102b@mail.gmail.com>
Dennis Wassel wrote:
> I've been trying to compile the ATLAS library on an 32-bit Linux
> system with my self-compiled gcc 4.3.0, but this fails.
> It boils down to the ATLAS config utility noticing that I have a
> 64-bit processor and trying to compile some low-level stuff with -m64,
> which doesn't work because I have not compiled in 64-bit support. [I
> could force 32-bit mode, but I feel that 64-bit mode surely improves
> performance, which is what ATLAS is for in the first place]
>
> Ok, so I try and recompile gcc, telling it that I do indeed have a
> 64-bit processor, and it "profiledbootstrap"s itself merrily, until at
> some point ld whines that it cannot find a compatible libc.
>
> 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!
In the 64-bit Linux system we have a backwards compatibility mode that
allows us to run 32-bit applications. We don't have a corresponding
64-bit mode on 32-bit systems.
Andrew.
next prev parent reply other threads:[~2008-04-03 9:02 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 [this message]
2008-04-03 17:22 ` Matthew Woehlke
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=47F49CF4.4060807@redhat.com \
--to=aph@redhat.com \
--cc=dennis.wassel@googlemail.com \
--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).