Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nathanael Nerode <neroden@twcny.rr.com>
To: gdb-patches@sources.redhat.com
Subject: Re: (toplevel) introduce host subdir configuration in Makefile
Date: Fri, 29 Nov 2002 13:51:00 -0000	[thread overview]
Message-ID: <20021129215054.GA524@doctormoo> (raw)

>>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.
This *shouldn't*, hopefully, be affected, because this doesn't require
that any other *subdirectories* be built.  The top level still 
determines the value of CC, CFLAGS, and so on and so forth, and passes 
them down to subconfigures and submakes.

> While GDB has a depencency on the SIM directory, it resolves it by 
>testing for ${srcdir)/../sim so that should be ok.
Whee.  I put a dependency in for that anyway because of the comment (in
my follow-up patch).

> 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`.
Extensive testing indicated that several subdirs with tcl/tk 
dependencies *did* require that in-source tcl/tk be configured; 
otherwise they used installed tcl/tk (or just failed). I dealt with this
in a subsequent patch (but I'm going to commit these patches as a whole,
probably, once I eventually get to them, since the follow-ups are 
effectively tweaks to the original).

> Andrew
Thanks for all the help.  This particular bit is likely to be the most 
destabilizing of my changes; most of the stuff prior to it was carefully
designed to be "behavior-change-free".

--Nathanael


             reply	other threads:[~2002-11-29 21:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-29 13:51 Nathanael Nerode [this message]
2002-11-29 14:23 ` Andrew Cagney
  -- strict thread matches above, loose matches on Subject: below --
2002-11-29 14:40 Nathanael Nerode
2002-11-29 15:16 ` Andrew Cagney
2002-11-28 14:13 Nathanael Nerode
2002-11-29  8:44 ` Andrew Cagney
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

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=20021129215054.GA524@doctormoo \
    --to=neroden@twcny.rr.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