Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@gnu.org>
To: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA:] sim --sysroot=... option.
Date: Sun, 12 Dec 2004 18:18:00 -0000	[thread overview]
Message-ID: <41BC8AB5.1080601@gnu.org> (raw)
In-Reply-To: <200412071731.iB7HVFHQ006257@ignucius.se.axis.com>

Hans-Peter Nilsson wrote:
>>Date: Mon, 6 Dec 2004 17:54:12 +0100
>>From: Hans-Peter Nilsson <hp@axis.com>
> 
> 
>>	* nrun.c (main): If simulator_sysroot is not empty, chdir there.
>>	* run.c (main): Ditto.
> 
> 
> After doing a test-build of all buildable simulators in CVS,
> (covered by arm-elf frv-elf h8300-elf m32r-elf m68hc11-elf
> mcore-elf mips-elf mn10300-elf powerpc-elf v850-elf), I'd like
> to retract the run.c part, which is just for an obsolete
> interface, and doesn't include sim-config.h (or apparently the
> option handler or the other bits from sim/common).

For the moment skip testing on mcore, v850 h8300, and mn10300.  The 
corresponding GDB parts are in pieces on the floor (I note that people 
are trying to re-assemble the h8300 and mn10300).

> I'd also like to like to replace the nrun.c patch with one that
> also includes unistd.h to get the chdir prototype (else there's
> a compilation warning, but only for *some* simulators;
> presumable target header files include unistd.h in some cases).
> Sorry for the extra reading.
> 
> 	* nrun.c [HAVE_UNISTD_H]: Include unistd.h.
> 	(main): If simulator_sysroot is not empty, chdir there.

Otherwize, all ok.

Andrew

PS: You wouldn't be interested in writing a simulator section of the GDB 
manual? :-)


  reply	other threads:[~2004-12-12 18:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-06 17:39 Hans-Peter Nilsson
2004-12-07 17:33 ` Hans-Peter Nilsson
2004-12-12 18:18   ` Andrew Cagney [this message]
2004-12-15  1:28     ` Sim manual (was: Re: [RFA:] sim --sysroot=... option.) Hans-Peter Nilsson

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=41BC8AB5.1080601@gnu.org \
    --to=cagney@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=hans-peter.nilsson@axis.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