From: Alexey Neyman <stilor@att.net>
To: crossgcc@sourceware.org
Subject: [crosstool-ng/crosstool-ng] 7a94c8: Rework configure logic wrt GNU autotools
Date: Mon, 30 Jan 2017 05:21:00 -0000 [thread overview]
Message-ID: <588d0e58932f4_3f083fa83b5d514c79673@hookshot-fe3-cp1-prd.iad.github.net.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 2562 bytes --]
Branch: refs/heads/master
Home: https://github.com/crosstool-ng/crosstool-ng
Commit: 7a94c81e5bf171d1258aa60438482fd44e5f9800
https://github.com/crosstool-ng/crosstool-ng/commit/7a94c81e5bf171d1258aa60438482fd44e5f9800
Author: Alexey Neyman <stilor@att.net>
Date: 2017-01-27 (Fri, 27 Jan 2017)
Changed paths:
M Makefile.in
M config/companion_tools.in
M config/companion_tools/autoconf.in
M config/companion_tools/automake.in
M config/companion_tools/libtool.in
M config/companion_tools/m4.in
M config/companion_tools/make.in
M configure.ac
M scripts/build/companion_tools.sh
Log Message:
-----------
Rework configure logic wrt GNU autotools
Rather than requiring them of a certain version, detect if they are present
(and have sufficient version) and select an appropriate companion tool
otherwise. The reason is that, for example, most recent gettext requires
automake 1.15, but the newest available CentOS has 1.13. Hence, the option
to "upgrade your system" does not apply, and the warning comment above
the companion tools is rather scary.
With this approach, it will work out of the box - either by using the host's
tools, or by building them as needed. Note that the user can still change
the setting in the config.
While there, propagate the new version checking macro to awk/bash/host binutils,
and switch from --with-foo=xxx to officially blessed FOO=xxx: the latter
does not require checking for bogus values (i.e., --with-foo, --without-foo)
and AC_PROG_* macros recognize the corresponding settings without further
modifications. For now, I kept --with-foo=, if only to complain and steer
people to the new way. To be cleaned up after a release.
Signed-off-by: Alexey Neyman <stilor@att.net>
Commit: 5b084c005b2669340594adeb2bf10a0d8a0fe623
https://github.com/crosstool-ng/crosstool-ng/commit/5b084c005b2669340594adeb2bf10a0d8a0fe623
Author: Alexey Neyman <stilor@att.net>
Date: 2017-01-28 (Sat, 28 Jan 2017)
Changed paths:
M Makefile.in
M config/companion_tools.in
M config/companion_tools/autoconf.in
M config/companion_tools/automake.in
M config/companion_tools/libtool.in
M config/companion_tools/m4.in
M config/companion_tools/make.in
M configure.ac
M scripts/build/companion_tools.sh
Log Message:
-----------
Merge pull request #564 from stilor/comptools-default-to-y-if-missing
Rework configure logic wrt GNU autotools
Compare: https://github.com/crosstool-ng/crosstool-ng/compare/d0682f9ad549...5b084c005b26
reply other threads:[~2017-01-28 21:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=588d0e58932f4_3f083fa83b5d514c79673@hookshot-fe3-cp1-prd.iad.github.net.mail \
--to=stilor@att.net \
--cc=crossgcc@sourceware.org \
/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).