Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Joel Sherrill <joel.sherrill@oarcorp.com>
Cc: Ralf Corsepius <ralf.corsepius@rtems.org>,
	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 18:11:00 -0000	[thread overview]
Message-ID: <20130316181049.GK4474@adacore.com> (raw)
In-Reply-To: <51448AD1.70201@oarcorp.com>

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.

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?

-- 
Joel


  reply	other threads:[~2013-03-16 18:11 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
2013-03-16 18:11       ` Joel Brobecker [this message]
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=20130316181049.GK4474@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb@sourceware.org \
    --cc=joel.sherrill@oarcorp.com \
    --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