This is the mail archive of the binutils@sourceware.org mailing list for the binutils project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Explicit architecture for m68k tests

From: Alan Modra <amodra at gmail dot com>
To: Vincent Rivière <vincent dot riviere at freesbee dot fr>
Cc: binutils at sourceware dot org
Date: Tue, 23 Nov 2010 08:06:54 +1030
Subject: Re: Explicit architecture for m68k tests
References: <4CE93874.2080004@freesbee.fr> <20101122053403.GE15607@bubble.grove.modra.org> <4CEAAC10.40102@freesbee.fr>

On Mon, Nov 22, 2010 at 06:44:48PM +0100, Vincent Rivière wrote:
> Alan Modra wrote:
> >I don't see any problem when I build an m68k-aout target, even with
> >--enable-targets=all.  How did you configure?
> 
> ../src/configure --target=m68k-aout --disable-nls
> make
> cd gas
> make check
> FAIL: gas/m68k/mcf-coproc
> FAIL: mcf-wdebug
> FAIL: cpu32
> 
> With the proposed patch, the whole gas testsuite succeeds.

I thought m68k-netbsd was aout, and running the testsuite on that
target succeeds.  Huh, mystery solved.  The difference is that
m68k-aout has a default target vector of aout0_big_vec while
m68k-netbsd uses m68knetbsd_vec.  The latter has the architecture, the
former doesn't.

Patch OK.

-- 
Alan Modra
Australia Development Lab, IBM

References:
- Explicit architecture for m68k tests
  - From: Vincent Rivière
- Re: Explicit architecture for m68k tests
  - From: Alan Modra
- Re: Explicit architecture for m68k tests
  - From: Vincent Rivière

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]