From: Joel Sherrill <joel.sherrill@oarcorp.com>
To: Ralf Corsepius <ralf.corsepius@rtems.org>
Cc: Mike Frysinger <vapier@gentoo.org>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: [gdb-7.5.91] mips sim fails to build on mingw32
Date: Sat, 16 Mar 2013 15:08:00 -0000 [thread overview]
Message-ID: <51448AD1.70201@oarcorp.com> (raw)
In-Reply-To: <5144169C.6060902@rtems.org>
On 3/16/2013 1:52 AM, Ralf Corsepius wrote:
> On 03/16/2013 05:33 AM, Ralf Corsepius wrote:
>> On 03/15/2013 07:37 PM, Joel Sherrill wrote:
>>> My recollection is that it did not link on CentOS 6 and was missing
>>> these symbols. Disabling it again should make it obvious.
>> Reverting your patch lets build mips-rtems*gdb-7.5.91 build
>> successfully on all hosts I am build gdb on [1]
>>
>> This is not surprising to me, as reverting the patch pushes
>> mips*gdb-7.5.91's configuration into a similar state as gdb-7.5.1 was,
>> which built for all of my build hosts.
>>
>>> But I didn't build in any particularly special way and it failed.
>> I am suspecting you were building mipstx39-rtems-gdb.
> OK, I found the original thread:
> http://www.sourceware.org/ml/gdb-patches/2012-09/msg00030.html
>
> All I can say, I can not reproduce the issue you were reporting with
> gdb-7.5.1 and gdb-7.5.91. Reverting this change brings back
> mingw32-w64/gdb-7.5.91.
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.
>
> Ralf
>
>
--
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
next prev parent reply other threads:[~2013-03-16 15:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 18:38 Joel Sherrill
[not found] ` <5143F627.3030905@rtems.org>
2013-03-16 6:56 ` Ralf Corsepius
2013-03-16 15:08 ` Joel Sherrill [this message]
2013-03-16 18:11 ` Joel Brobecker
2013-03-16 18:48 ` Joel Sherrill
2013-03-16 23:24 ` Mike Frysinger
2013-03-17 1:03 ` Joel Brobecker
2013-03-17 15:10 ` Mike Frysinger
2013-03-17 1:13 ` Joel Sherrill
2013-03-17 15:09 ` Mike Frysinger
2013-03-17 16:02 ` Joel Brobecker
2013-03-17 16:11 ` Joel Sherrill
2013-03-17 4:16 ` Ralf Corsepius
2013-03-17 16:05 ` Joel Sherrill
[not found] ` <201303181405.55098.vapier@gentoo.org>
2013-03-20 17:51 ` Joel Sherrill
2013-03-20 18:29 ` Mike Frysinger
2013-03-20 18:48 ` Joel Sherrill
2013-03-27 11:21 ` Pedro Alves
2013-03-27 17:00 ` Mike Frysinger
-- strict thread matches above, loose matches on Subject: below --
2013-03-12 23:17 GDB 7.5.91 available for testing Joel Brobecker
[not found] ` <5140894E.6000308@oarcorp.com>
2013-03-15 12:52 ` [gdb-7.5.91] mips sim fails to build on mingw32 Ralf Corsepius
2013-03-15 18:13 ` Mike Frysinger
2013-03-15 18:32 ` Ralf Corsepius
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51448AD1.70201@oarcorp.com \
--to=joel.sherrill@oarcorp.com \
--cc=gdb@sourceware.org \
--cc=ralf.corsepius@rtems.org \
--cc=vapier@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox