From: Mark Kettenis <kettenis@chello.nl>
To: Nathanael Nerode <neroden@twcny.rr.com>
Cc: gcc-patches@gcc.gnu.org, gdb-patches@sources.redhat.com,
binutils@sources.redhat.com, dj@redhat.com
Subject: Re: (top level patch) Autoconfiscate. (Woo!)
Date: Sat, 28 Dec 2002 07:06:00 -0000 [thread overview]
Message-ID: <86smwijnhi.fsf@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: Nathanael Nerode's message of "Fri, 27 Dec 2002 22:59:43 -0500"
Nathanael Nerode <neroden@twcny.rr.com> writes:
> This autoconfiscates the top level. Tested on i686-pc-linux-gnu, produced
> a Makefile with only trivial differences from before.
Nothing serious, but...
...I get the following warning when configuring readline:
Configuring in readline
configure: WARNING: If you wanted to set the --build type, don't use --host.
If a cross compiler is detected then cross compile mode will be used.
configure: loading cache .././config.cache
checking build system type... i386-unknown-freebsd4.7
checking host system type... i386-unknown-freebsd4.7
Beginning configuration for readline-4.3 for i386-unknown-freebsd4.7
We get this warning since the readline subdirectory uses Autoconf
2.50, and toplevel passes --host, but not --build to configure.
Therefore I suspect that we'll see more of these warnings once we
start using Autoconf 2.5x for the other subdirectories too.
Anyway, as far as I can determine, the warning doesn't hurt, but we
might want to get rid of it.
Note that this is probably caused by an earlier patch, and not by this
last autoconfiscate patch, but I didn't notice it before.
Mark
P.S. Why is Makefile.tpl not included in the src CVS tree? It is
included in the gcc CVS tree.
next prev parent reply other threads:[~2002-12-28 13:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-27 20:03 Nathanael Nerode
2002-12-27 23:07 ` Alexandre Oliva
2002-12-28 7:06 ` Mark Kettenis [this message]
2002-12-28 8:24 ` Alexandre Oliva
2002-12-28 10:05 ` Alexandre Oliva
2002-12-28 10:08 ` Daniel Jacobowitz
2002-12-28 10:34 ` Alexandre Oliva
2002-12-27 23:23 Nathanael Nerode
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=86smwijnhi.fsf@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=binutils@sources.redhat.com \
--cc=dj@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--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