[gdb-7.5.91] mips sim fails to build on mingw32

Joel Sherrill joel.sherrill@oarcorp.com
Sat Mar 16 18:48:00 GMT 2013


On 3/16/2013 1:10 PM, Joel Brobecker wrote:
> Joel,
>
>> It is still there if you configure correctly. On a completely up to date
>> CentOS 6.x install. I reversed the patch locally and configured like this:
>>
>> ../gdb-7.5.91/configure --target=mips-rtems4.11 \
>>    --prefix=/home/joel/test-gdb/install/ --enable-sim \
>>    --enable-sim-hardware --enable-timebase --enable-sim-trace &&
>> make
>>
>> And the build failed like this:
>>
>> -o run \
>>        nrun.o libsim.a ../../bfd/libbfd.a ../../opcodes/libopcodes.a
>> ../../libiberty/libiberty.a -lm -lm -lz -lnsl
>> libsim.a(interp.o): In function `sim_open':
>> /home/joel/test-gdb/b-gdb/sim/mips/../../../gdb-7.5.91/sim/mips/interp.c:552:
>> undefined reference to `sockser_addr'
>>
>> Sounds like it needs the same configure magic as the other architectures.
> Do I understand correctly that the patch you added is too broad and
> affects more targets than needed? If that's the case, I agree with
> Ralf that the best course is to revert your patch first, and then
> implement something that only affects CentOS.
This is not CentOS specific. The file is required when you configure with
--enable-sim-hardware.  It is just a matter of tripping the configure
command correctly.

The only workaround going on here is that we need to account for
mingw not being able to build dv-sockser.c.

FWIW I see dv-sockser.o included by a multiple targets but only but
only the bfin has logic to avoid it on mingw.  Are any of the following
buildable on mingw?

cris
frv
iq2000
m32r
m68hc11
mn10300
sh64

It would be nice to know if this is a general problem on mingw.
> Scheduled release time is 10 days away (Mar 26). It would be nice
> to have this fixed by then. Otherwise, we'll have to delay the release.
> Since you're the only one who seems to be able to reproduce, would
> you mind working on this?
>

Sure. I have a patch written based on the logic in sim/bfin and just need to
test it.

But I don't know how to regenerate the configure script in gdb. I see
I need autoconf 2.64 but what's the magic incantation.

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



More information about the Gdb mailing list