public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Brian Dessent <brian@dessent.net>
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: Sat, 05 Apr 2008 23:53:00 -0000	[thread overview]
Message-ID: <47F7EDD2.59D0B943@dessent.net> (raw)
In-Reply-To: <fe03ae8f0804050210y55ef9c5fvdfc9472a72086a46@mail.gmail.com>

Dennis Wassel wrote:

> What strikes me about this is the fact that ATLAS' configure (all by
> itself, no options given) thinks that using -m64 on a 32-bit system
> might be a good idea (not to actually link something executable,
> probably just some low-level assembler-ish stuff, no clue), since I'm
> using a 64-bit compiler - am I up to something here, or do you think
> it's just One Of Those Things?

It seems common for numeric computation libraries to have configure
checks to detect the specific processor variant so that they will be
built with the best optimization, cf. gmp/mpfr.  The problem is that
they tend to do this without regard for the flavor of operating system. 
For example I seem to recall a recent PR in which gmp was configured on
e.g. sparc-sun-solaris2.10 but it detected that the machine was really
sparc64-* and built binaries of the wrong flavor, leading to an error in
the gcc build when it tried to link the stage 1 xgcc.

I think in all these cases you can simply spell out the --host=
explicitly to override the autodetection logic.

Brian

  reply	other threads:[~2008-04-05 21:26 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
2008-04-05  5:40 ` Brian Dessent
2008-04-05 13:01   ` Dennis Wassel
2008-04-05 23:53     ` Brian Dessent [this message]
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=47F7EDD2.59D0B943@dessent.net \
    --to=brian@dessent.net \
    --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).