Re: Recent simulator patches broke many sims

[Joel Sherrill <joel.sherrill@oarcorp.com>]

On 3/23/2013 7:38 PM, Hans-Peter Nilsson wrote:
>> From: Joel Sherrill <joel.sherrill@oarcorp.com>
>> Date: Sat, 23 Mar 2013 23:49:18 +0100
>> And built successfully when configured like this:
>>
>> ../gdb/configure --target=frv-elf --prefix=/home/joel/test-gdb/install
>> --enable-sim-hardware --enable-sim --enable-sim-trace
> "gdb" as in toplevel from a gdb checkout, I presume.
> (If from the gdb subdir I guess you wouldn't get very far.)
> Is that why you have to add those options?
I added those options because that is the combination that initially
tripped the failure months ago. Then last week someone spotted
that mingw failed to build. Mike Frysinger and I have been trying to
come up with a configure solution that handles mingw not supporting
dv-sockser.o and some simulators always requiring it.
> One major difference is that I use the toplevel configure after
> a checkout of *the "sim" CVS module*, so not much of gdb there,
> actually just MAINTAINERS and version.in.
I don't think that's really much of an issue. Except to increase my 
build time.

I have a fix in my local tree and posted it to the list. Here is my test 
plan.

I regenerated all of the sim directories where configure.ac includes 
acinclude.m4.
That resulted in the following set of modified files on my working git 
branch:

#    modified:   bfin/configure
#    modified:   common/acinclude.m4
#    modified:   cris/configure
#    modified:   frv/configure
#    modified:   iq2000/configure
#    modified:   lm32/configure
#    modified:   m32r/configure
#    modified:   m68hc11/configure
#    modified:   mips/configure
#    modified:   mn10300/configure
#    modified:   sh64/configure

Based on that, I put together the following list of targets:

bfin-elf
cris-elf
frv-elf
iq2000-elf
lm32-elf
m32r-elfle
m68hc11-elf
mips-elf
mipstx93-elf
mn10300-elf
sh64-elf

For each of those targets, I will build with no sim-hardware argument,
--enable-sim-hardware, and --disable-sim-hardware. If the configure
and make complete successfully, I will run make check.

Any other suggestions on how to test this?

>> I can hop on IRC if you give me a channel so we can work through
>> this quickly. Other forms of chat are OK also. I want to run this down
>> so a release can happen.
> Sometimes I'm at irc.oftc.net#gcc
>
> brgds, H-P


-- 
Joel Sherrill, Ph.D.             Director of Research & Development
joel.sherrill@OARcorp.com        On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
Support Available                (256) 722-9985