From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: uweigand@de.ibm.com
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc] [7/9] Multi-target support: Fix GDB_OSABI_OPENBSD_AOUT problem
Date: Fri, 26 Oct 2007 09:21:00 -0000 [thread overview]
Message-ID: <200710260805.l9Q85855007631@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <200710260117.l9Q1HcWd004692@d12av02.megacenter.de.ibm.com> (uweigand@de.ibm.com)
> Date: Fri, 26 Oct 2007 03:17:38 +0200 (CEST)
> From: "Ulrich Weigand" <uweigand@de.ibm.com>
>
> Hello,
>
> this patch attempts to address a somewhat unfortunate situation
> relating to OpenBSD/a.out.
>
> i386obsd-tdep.c contains this FIXME:
>
> /* FIXME: kettenis/20021020: Since OpenBSD/i386 binaries are
> indistingushable from NetBSD/i386 a.out binaries, building a GDB
> that should support both these targets will probably not work as
> expected. */
> #define GDB_OSABI_OPENBSD_AOUT GDB_OSABI_NETBSD_AOUT
>
> In an --enable-targets=all build, this has the effect that two OSABI
> sniffers for the (numerically) same OSABI are registered, leading to
> an internal compiler error.
The last OpenBSD/i386 release that used a.out was OpenBSD 3.3, which
was released more than four years ago. I have no problem with
dropping a.out support for OpenBSD/i386 if that makes things easier.
However, OpenBSD/vax, OpenBSD/m68k and OpenBSD/m88k are still a.out,
so parts of your diff might still be required (didn't look at the
details of your diff yet).
Mark
next prev parent reply other threads:[~2007-10-26 8:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-26 1:18 Ulrich Weigand
2007-10-26 9:21 ` Mark Kettenis [this message]
2007-10-29 20:27 ` Ulrich Weigand
2007-10-29 22:53 ` Mark Kettenis
2007-10-30 21:36 ` Ulrich Weigand
2007-11-13 21:27 ` [ping] " Ulrich Weigand
2007-11-14 22:22 ` Mark Kettenis
2007-11-14 22:30 ` Mark Kettenis
2007-11-15 1:05 ` Ulrich Weigand
2007-11-16 23:29 ` Mark Kettenis
2007-11-17 1:05 ` Ulrich Weigand
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=200710260805.l9Q85855007631@brahms.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.com \
/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