From: Kevin Buettner <kevinb@cygnus.com>
To: Andrew Cagney <ac131313@cygnus.com>, Kevin Buettner <kevinb@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Conditionally include nlist.h in solib-legacy.c
Date: Fri, 23 Mar 2001 08:40:00 -0000 [thread overview]
Message-ID: <1010323164002.ZM20219@ocotillo.lan> (raw)
In-Reply-To: <3ABB762D.9867D7DC@cygnus.com>
On Mar 23, 11:13am, Andrew Cagney wrote:
> Looking back at this. I don't know that solib-legacy should ever be
> appearing in the list of TDEPFILES. Given it can only work in native
> builds, I think it should only be included in the NATDEPFILES.
You're right.
I put it in the TDEPFILES list for two reasons:
1) Laziness. (It was easier to just search for solib-svr4.o and add
it to each line containing this file.)
2) To avoid link errors.
My concern regarding #2 was as follows: If you put solib-legacy.o in
host A's NATDEPFILES and then you configure an A cross B debugger where
B doesn't have solib-svr4.o in its TDEPFILES, you'll end up with a link
error when you're done.
I've just recently learned, however, that this won't happen since
NATDEPFILES is commented out when building cross debuggers.
Since problem #2 is disposed of, all I need to do is overcome #1.
(I'll try to get around to looking at it over the weekend.)
> I suspect this was the real reason for the compile problems.
Probably so. However, I also think that the solib-legacy code is
better off using the autoconf supplied feature tests.
prev parent reply other threads:[~2001-03-23 8:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1010320030437.ZM8757@ocotillo.lan>
2001-03-23 8:13 ` Andrew Cagney
2001-03-23 8:40 ` Kevin Buettner [this message]
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=1010323164002.ZM20219@ocotillo.lan \
--to=kevinb@cygnus.com \
--cc=ac131313@cygnus.com \
--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