From: Tom Tromey <tom@tromey.com>
To: Simon Marchi via Gcc-patches <gcc-patches@gcc.gnu.org>
Cc: Alan Modra <amodra@gmail.com>, Jeff Law <jeffreyalaw@gmail.com>,
Simon Marchi <simon.marchi@polymtl.ca>,
gdb-patches@sourceware.org, Binutils <binutils@sourceware.org>
Subject: Re: RFC: Changing AC_PROG_CC to AC_PROG_CC_C99 in top level configure
Date: Mon, 03 May 2021 10:26:49 -0600 [thread overview]
Message-ID: <871ranvl4m.fsf@tromey.com> (raw)
In-Reply-To: <e9af4380-4c97-798e-f151-174e098e0065@polymtl.ca> (Simon Marchi via Gcc-patches's message of "Mon, 3 May 2021 10:47:15 -0400")
>>>>> "Simon" == Simon Marchi via Gcc-patches <gcc-patches@gcc.gnu.org> writes:
Simon> For GDB, it's not supported to run gdb/configure directly, you need to
Simon> use the top-level configure. Is it supported from some of the other
Simon> projects in the repo?
It can be done sometimes but I think it isn't really a scenario worth
worrying about. Normally this kind of thing is only doable for sources
that are already independent of the top-level configury -- drop-in stuff
like gmp or libiconv, or roots of the tree like libiberty and gnulib.
Simon> I just tried with ld, it doesn't work since it depends on bfd also being
Simon> built. I tried with just bfd, it doesn't work (with the default
Simon> configure options at least) because it requires zlib being built.
Yeah, most of the things that are "really" in-tree have dependencies and
can't be built independently of the rest.
Tom
next prev parent reply other threads:[~2021-05-03 16:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 11:32 Nick Clifton
2021-04-26 19:32 ` Joseph Myers
2021-04-26 20:05 ` Mike Frysinger
2021-04-26 21:31 ` Christian Biesinger
2021-04-27 10:49 ` Nick Clifton
2021-04-27 16:58 ` Joseph Myers
2021-04-30 18:36 ` Simon Marchi
2021-04-30 21:48 ` Jeff Law
2021-05-03 6:28 ` Alan Modra
2021-05-03 14:47 ` Simon Marchi
2021-05-03 16:26 ` Tom Tromey [this message]
2021-05-03 21:51 ` Alan Modra
2021-05-03 23:30 ` Simon Marchi
2021-05-04 12:42 ` Nick Clifton
2021-05-04 15:16 ` Simon Marchi
2021-05-05 0:18 ` Alan Modra
2021-05-05 7:05 ` Iain Sandoe
2021-05-05 7:20 ` Alan Modra
2021-05-05 7:23 ` Iain Sandoe
2021-05-10 8:49 ` Iain Sandoe
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=871ranvl4m.fsf@tromey.com \
--to=tom@tromey.com \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jeffreyalaw@gmail.com \
--cc=simon.marchi@polymtl.ca \
/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).