Re: libstdc++/5198: 3.0.3 linux x m68k build fail: invalid opcodes in c++locale.cc

[Craig Rodrigues <rodrigc@mediaone.net>]

The following reply was made to PR libstdc++/5198; it has been noted by GNATS.

From: Craig Rodrigues <rodrigc@mediaone.net>
To: Don Lindsay <lindsayd@cisco.com>
Cc: rodrigc@gcc.gnu.org, aaron@frye.com, gcc-bugs@gcc.gnu.org,
   gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Subject: Re: libstdc++/5198: 3.0.3 linux x m68k build fail: invalid opcodes in c++locale.cc
Date: Fri, 4 Jan 2002 17:24:56 -0500

 On Fri, Jan 04, 2002 at 01:53:00PM -0800, Don Lindsay wrote:
 > On Fri, 4 Jan 2002, Craig Rodrigues wrote:
 > 
 > > OK, according to your specs file, everything should be defaulting
 > > to 68020, so I don't know why the assembler is being called
 > > with the 68000 flag.
 > 
 > gcc/Makefile is specifying -m68000 on the xgcc invocation, so that's
 > passed through to the assembler. Changing the command line to -m68020 does
 > allow this command to complete OK.
 > 
 > Notice, also, that /m68000/ is in the pathname of the affected build area
 > (within the overall build subtree). This appears to be because
 > gcc/Makefile specifies m68000 in its MULTILIB_* vars. My build subtree, at
 > the time when things died, had /m68000/, /m5200/, /mcpu32/ and
 > /msoft-float/ subdirectories.
 
 Hmmm.
 What is in your multilib.h file?
 
 Since you mentioned that you configured with m68k-aout, if I
 look in config.gcc, I see that this target uses:
 m68k-*-aout*)
         tmake_file=m68k/t-m68kbare
         tm_file="m68k/m68k-aout.h libgloss.h"
         float_format=m68k
         ;;
 
 In config/m68k/t-m68kbare, if you remove m68000 from the 
 MULTILIB_OPTIONS line, does that help?
 -- 
 Craig Rodrigues        
 http://www.gis.net/~craigr    
 rodrigc@mediaone.net