From: Andrew Cagney <cagney@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [ob] user-regs.c build fix for arm-linux
Date: Fri, 05 Mar 2004 05:23:00 -0000 [thread overview]
Message-ID: <40480ED5.4050807@gnu.org> (raw)
In-Reply-To: <20040229165929.GG15749@nevyn.them.org>
> +/* This structure is named gdb_user_regs instead of user_regs to avoid
> + conflicts with any "struct user_regs" in system headers. For instance,
> + on ARM GNU/Linux native builds, nm-linux.h includes <signal.h> includes
> + <sys/ucontext.h> includes <sys/procfs.h> includes <sys/user.h>, which
> + declares "struc user_regs". */
Even shorter, for instance:
/* This structure is named gdb_user_regs, instead of user_regs, to avoid
a comflict with <sys/user.h> defined "struct user_regs" on ARM
GNU/Linux (included by: nm-linux.h -> <signal.h> -> <sys/ucontext.h> ->
<sys/procfs.h>). */
which is just stating the facts.
Andrew
WARNING: multiple messages have this Message-ID
From: Andrew Cagney <cagney@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [ob] user-regs.c build fix for arm-linux
Date: Fri, 19 Mar 2004 00:09:00 -0000 [thread overview]
Message-ID: <40480ED5.4050807@gnu.org> (raw)
Message-ID: <20040319000900.m4KlI9JGD_y0X6SkIWHU3sJHqTp_invOMp-57-6RvEY@z> (raw)
In-Reply-To: <20040229165929.GG15749@nevyn.them.org>
> +/* This structure is named gdb_user_regs instead of user_regs to avoid
> + conflicts with any "struct user_regs" in system headers. For instance,
> + on ARM GNU/Linux native builds, nm-linux.h includes <signal.h> includes
> + <sys/ucontext.h> includes <sys/procfs.h> includes <sys/user.h>, which
> + declares "struc user_regs". */
Even shorter, for instance:
/* This structure is named gdb_user_regs, instead of user_regs, to avoid
a comflict with <sys/user.h> defined "struct user_regs" on ARM
GNU/Linux (included by: nm-linux.h -> <signal.h> -> <sys/ucontext.h> ->
<sys/procfs.h>). */
which is just stating the facts.
Andrew
next prev parent reply other threads:[~2004-03-05 5:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-28 17:31 Daniel Jacobowitz
2004-02-28 17:36 ` Andrew Cagney
2004-02-28 18:30 ` Daniel Jacobowitz
2004-02-28 18:49 ` Andrew Cagney
2004-02-29 0:53 ` Daniel Jacobowitz
2004-02-29 16:59 ` Daniel Jacobowitz
2004-03-05 5:23 ` Andrew Cagney [this message]
2004-03-19 0:09 ` Andrew Cagney
2004-03-19 0:09 ` Daniel Jacobowitz
2004-03-09 20:05 ` Daniel Jacobowitz
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=40480ED5.4050807@gnu.org \
--to=cagney@gnu.org \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.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