From: Nathanael Nerode <neroden@twcny.rr.com>
To: gcc-patches@gcc.gnu.org, gdb-patches@sources.redhat.com,
binutils@sources.redhat.com, dj@redhat.com
Subject: Re: (toplevel patch) host subconfigures in Makefile, fixed version
Date: Tue, 03 Dec 2002 16:44:00 -0000 [thread overview]
Message-ID: <20021204004344.GA10151@doctormoo> (raw)
>> # gcc is the only module which uses GCC_FLAGS_TO_PASS.
>
>Could we use an automake conditional to cut down on the replication?
^^^^s/make/gen
We certainly can, and will. Bruce actually sent me a decent way of
doing this. The reason I wrote things out is that I
actually anticipate some changes for purposes of accuracy, and I
wouldn't be at all surprised if gcc's 'configure' section ought to
deviate from that of other host modules.
In my previous completed versions, there's actually a section in
Makefile.def called "flags_to_pass", with an entry for each flag,
and Makefile.tpl simply loops over them, inserting the ones appropriate
for the situation. I intend to do that eventually. (Which flags are
passed down when is a great mish-mash right now and I want to spend some
time simplifying it as much as I can.)
(My ideal layout involves adding a HOST_SUBDIR as well as BUILD_SUBDIR
and TARGET_SUBDIR, and effectively unifying all of those sections.
There's some evidence that this isn't a good idea though.)
>> +expect/Makefile: configure-tcl maybe-configure-tk
>
>No maybe here?
I believe that I tried it with TCL installed and not in the tree, and it
failed. It shouldn't have though... so you're right, that should be a
maybe. Will change.
--Nathanael
next reply other threads:[~2002-12-04 0:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-03 16:44 Nathanael Nerode [this message]
2002-12-03 17:00 ` DJ Delorie
-- strict thread matches above, loose matches on Subject: below --
2002-12-03 16:23 Nathanael Nerode
2002-12-03 16:29 ` 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=20021204004344.GA10151@doctormoo \
--to=neroden@twcny.rr.com \
--cc=binutils@sources.redhat.com \
--cc=dj@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--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