Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: brobecker@gnat.com, gdb-patches@sources.redhat.com
Subject: Re: gdbserver build broken on amd64-linux
Date: Wed, 20 Oct 2004 15:53:00 -0000	[thread overview]
Message-ID: <20041020155316.GA17828@nevyn.them.org> (raw)
In-Reply-To: <200410201547.i9KFl8i6022712@elgar.sibelius.xs4all.nl>

On Wed, Oct 20, 2004 at 05:47:08PM +0200, Mark Kettenis wrote:
>    Date: Wed, 20 Oct 2004 08:24:41 -0700
>    From: Joel Brobecker <brobecker@gnat.com>
> 
>    > How about ths instead?
>    > 
>    > #ifndef ARCH_GET_FS
>    > #define ARCH_SET_GS 0x1001
>    > #define ARCH_SET_FS 0x1002
>    > #define ARCH_GET_FS 0x1003
>    > #define ARCH_GET_GS 0x1004
>    > #endif
> 
> That's better, since it's dangerous to include kernel headers
> directly.
> 
>    Yes, that should work too. I'm curious as to why these macros are not
>    defined for me, or said differently how it is that they are defined for
>    others (assuming others can build this code on amd64-linux unmodified).
> 
> It all depends on the combination of installed kernel headers and
> glibc headers whether it'll work or not.  There are broken
> combinations out there, even on i386.  It's inherent to the way
> GNU/Linux is developped since there is no real attempt to keep kernel
> and libc in sync.  Learn to live with or <plug> switch to a free
> operating system with decent release management </plug>.

While your accusation is generally valid, in this case Joel hit the
salient point:

	(assuming others can build this code on amd64-linux unmodified)

Since I wrote that code before I got an amd64-linux machine (long time
ago), and didn't test it on one before I checked it in, it's my own
stupid fault.  I assumed that <linux/prctl.h> would include
<asm/prctl.h>, whch does not seem to be the case.

Joel, could you test the #ifndef version and check it in?

-- 
Daniel Jacobowitz


  reply	other threads:[~2004-10-20 15:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-20  5:32 Joel Brobecker
2004-10-20 14:26 ` Daniel Jacobowitz
2004-10-20 15:24   ` Joel Brobecker
2004-10-20 15:47     ` Mark Kettenis
2004-10-20 15:53       ` Daniel Jacobowitz [this message]
2004-10-21  4:15         ` Joel Brobecker
2004-10-21  4:38           ` Joel Brobecker
2004-10-21 13:48             ` Daniel Jacobowitz
2004-10-21 17:27               ` Joel Brobecker
2004-10-21 13:49           ` Daniel Jacobowitz
2004-10-21 17:33             ` Joel Brobecker
2004-10-21 17:36               ` Daniel Jacobowitz
2004-10-21 18:09                 ` Joel Brobecker

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=20041020155316.GA17828@nevyn.them.org \
    --to=drow@false.org \
    --cc=brobecker@gnat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mark.kettenis@xs4all.nl \
    /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