From: Andrew Cagney <ac131313@redhat.com>
To: Nathanael Nerode <neroden@twcny.rr.com>
Cc: gdb-patches@sources.redhat.com, dj@redhat.com
Subject: Re: (toplevel) introduce host subdir configuration in Makefile
Date: Fri, 29 Nov 2002 08:44:00 -0000 [thread overview]
Message-ID: <3DE7996F.4030801@redhat.com> (raw)
In-Reply-To: <20021128221312.GA20889@doctormoo>
> At the moment it appears that 'gcc','zlib','fastjar', and 'libiberty' can
> be configured in any order relative to each other (nice and straightforward).
> If anyone knows of specific configure order dependencies, they should tell
> me. I'll be spending a while fiddling with gcc and src trying to identify
> any other real configure order dependencies.
Nathanael,
Some heads up.
GDB requires an ISO C compiler and on some systems that involves running
the compiler with specific flags (-Ae, I think, on HP/UX?). The problem
is that GDB can't test/configure this directly. By time time it has a
say in the matter, it is too late. The top level will need to do this
very early on.
While GDB has a depencency on the SIM directory, it resolves it by
testing for ${srcdir)/../sim so that should be ok.
While INSIGHT has a dependency on tcl/tk, it appears to resolve it doing
some pretty agressive hunting. It looks in both ${srcdir} and `pwd`.
Andrew
next prev parent reply other threads:[~2002-11-29 16:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-28 14:13 Nathanael Nerode
2002-11-29 8:44 ` Andrew Cagney [this message]
2002-12-02 8:18 ` Daniel Jacobowitz
2002-12-02 8:40 ` Alexandre Oliva
2002-12-02 8:52 ` Daniel Jacobowitz
2002-12-02 9:44 ` Alexandre Oliva
2002-12-02 10:23 ` Daniel Jacobowitz
2002-12-02 12:48 ` Alexandre Oliva
2002-12-02 13:43 ` DJ Delorie
2002-12-02 14:03 ` Thomas Dickey
2002-12-04 0:42 ` Samuel Tardieu
2002-12-04 3:14 ` Thomas E. Dickey
2002-12-02 10:17 ` DJ Delorie
2002-11-29 13:51 Nathanael Nerode
2002-11-29 14:23 ` Andrew Cagney
2002-11-29 14:40 Nathanael Nerode
2002-11-29 15:16 ` Andrew Cagney
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=3DE7996F.4030801@redhat.com \
--to=ac131313@redhat.com \
--cc=dj@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=neroden@twcny.rr.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