Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sourceware.org
Subject: Re: [ob] Check for linux-gnu* in linux-dp.exp
Date: Wed, 04 May 2005 23:29:00 -0000	[thread overview]
Message-ID: <20050504232932.GA8605@nevyn.them.org> (raw)
In-Reply-To: <200505042311.j44NBkRC031298@elgar.sibelius.xs4all.nl>

On Thu, May 05, 2005 at 01:11:46AM +0200, Mark Kettenis wrote:
>    Date: Wed, 4 May 2005 17:22:28 -0400
>    From: Daniel Jacobowitz <drow@false.org>
> 
>    I built a mips64-unknown-linux-gnuabi64 toolchain and noticed that
>    it didn't run this test
> 
> There's nothing wrong with your patch, but what does
> mips64-unknown-linux-gnuabi64 mean?  Is that just someone's local
> invention or is it really a canonical GNU system quadruplet?  Is this
> what config.guess returns on a specific system?

It is not returned by config.guess.  It's checked by glibc's configure
script, however - it means that the compiler (and options) being
configured with target an n64 environment rather than n32.  It's the
result of a lot of arguing between Uli, Roland, and Alex Oliva - in
other words, not my fault :-)

Nothing but glibc cares.  Everything is supposed to match for gnu*.

> It seems to me that there is something seriously wrong with canonical
> names for 64-bit Linux systems.  The current situation seems to be
> that you can't really tell whether a Linux system is really 64-bit or
> just has a 64-bit kernel and is otherwise completely 32-bit.  My SuSE
> 9.2 Athlon 64 desktop system seems to be fully 64-bit, but we also
> have a Debian-based Opteron cluster that's complete 32-bit.  Yet on
> both systems config.guess returns x86_64-unknown-linux-gnu.

That's a problem with config.guess which I saw discussed on autoconf@
earlier today, and the poster was suggested to take it to
config.patches.  It's a hard question what config.guess should return.
If you want it to return i686 instead, from a practical least-effort
point of view, use the 'linux32' wrapper program.

-- 
Daniel Jacobowitz
CodeSourcery, LLC


      reply	other threads:[~2005-05-04 23:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-04 21:22 Daniel Jacobowitz
2005-05-04 23:12 ` Mark Kettenis
2005-05-04 23:29   ` Daniel Jacobowitz [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=20050504232932.GA8605@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=mark.kettenis@xs4all.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