From: Andrew Cagney <cagney@gnu.org>
To: Mark Kettenis <kettenis@gnu.org>
Cc: gdb@sources.redhat.com
Subject: Re: NAT_FILE always required?
Date: Mon, 27 Sep 2004 14:17:00 -0000 [thread overview]
Message-ID: <415820BB.6030001@gnu.org> (raw)
In-Reply-To: <200409261900.i8QJ0iXs001344@elgar.sibelius.xs4all.nl>
> It looks as if I'm ready to get rid of NAT_FILE for *BSD/amd64.
> Except there's this funny bit of code in configure.in:
>
> if test "${nativefile}" = ""; then
> < Makefile \
> sed -e '/^NATDEPFILES[[ ]]*=.*\\$/,/[[^\\]]$/s/^/# /' \
> -e '/^NATDEPFILES[[ ]]*=/s/^/# /' \
> | sed -e '/^\(NATDEPFILES[[ ]]*[[+]]=[[ ]]*\)/s//# \1/' \
> > Makefile.tem
> mv -f Makefile.tem Makefile
> fi
>
> This code comments out the definition of NATDEPFILES if NAT_FILE isn't
> there. What's the purpose of this code?
As you imply -> it was assuming that nativefile=="" implied no native
support. Grubbing around, there was code like:
if host==target
native=`sed magic ...`
so native= for cross targets was empty and the above would have disabled
native support. The predicate was moved between 5.2 and 5.3 and my
fuzzy memory is because:
- it never really worked
- (possibly) it was realized that "one day soon" GDB would support both
native and true cross debuggers in a single binary
> Can anybody see a reason why
> this code can't be deleted?
As far as I can tell, ever since 5.3 nativefile!="" has held, and hence
the code was dead.
Andrew
next prev parent reply other threads:[~2004-09-27 14:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-26 19:00 Mark Kettenis
2004-09-27 14:17 ` Andrew Cagney [this message]
2004-09-27 17:15 ` Mark Kettenis
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=415820BB.6030001@gnu.org \
--to=cagney@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=kettenis@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).