[ob] Check for linux-gnu* in linux-dp.exp

[ob] Check for linux-gnu* in linux-dp.exp

[Daniel Jacobowitz]

I built a mips64-unknown-linux-gnuabi64 toolchain and noticed that it didn't
run this test.

Committed as obvious.

-- 
Daniel Jacobowitz
CodeSourcery, LLC

2005-05-04  Daniel Jacobowitz  <dan@codesourcery.com>

	* gdb.threads/linux-dp.exp: Check for *-*-linux-gnu*.

Index: gdb.threads/linux-dp.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.threads/linux-dp.exp,v
retrieving revision 1.10
diff -u -p -r1.10 linux-dp.exp
--- gdb.threads/linux-dp.exp	15 Dec 2004 18:28:54 -0000	1.10
+++ gdb.threads/linux-dp.exp	4 May 2005 21:17:32 -0000
@@ -42,7 +42,7 @@ set prms_id 0
 set bug_id 0
 
 # This only works with Linux configurations.
-if ![istarget *-*-linux-gnu] then {
+if ![istarget *-*-linux-gnu*] then {
     return
 }
 

Re: [ob] Check for linux-gnu* in linux-dp.exp

[Mark Kettenis]

   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 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.

Mark

Re: [ob] Check for linux-gnu* in linux-dp.exp

[Daniel Jacobowitz]

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