From: Alexey Neyman <stilor@att.net>
To: crossgcc@sourceware.org
Subject: [crosstool-ng/crosstool-ng] 3f7fbd: Move companion tool build into a separate step.
Date: Sat, 03 Dec 2016 03:19:00 -0000 [thread overview]
Message-ID: <584239a0a26ac_1ebf73fa5109a113c6333a@hookshot-fe-6dbb0c4.cp1-iad.github.net.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 3006 bytes --]
Branch: refs/heads/master
Home: https://github.com/crosstool-ng/crosstool-ng
Commit: 3f7fbd7beda5d840cd9a15189a94aaad4a802d37
https://github.com/crosstool-ng/crosstool-ng/commit/3f7fbd7beda5d840cd9a15189a94aaad4a802d37
Author: Alexey Neyman <stilor@att.net>
Date: 2016-12-02 (Fri, 02 Dec 2016)
Changed paths:
M scripts/build/companion_tools.sh
M scripts/build/companion_tools/050-make.sh
M scripts/build/companion_tools/100-m4.sh
M scripts/build/companion_tools/200-autoconf.sh
M scripts/build/companion_tools/300-automake.sh
M scripts/build/companion_tools/400-libtool.sh
M scripts/crosstool-NG.sh.in
M steps.mk
Log Message:
-----------
Move companion tool build into a separate step.
Also, rename "build" -> "for_build", since we're going to have a "for_host"
as well.
Signed-off-by: Alexey Neyman <stilor@att.net>
Commit: cf86df688a8e7aeba28767ae0f841022a2e8347b
https://github.com/crosstool-ng/crosstool-ng/commit/cf86df688a8e7aeba28767ae0f841022a2e8347b
Author: Alexey Neyman <stilor@att.net>
Date: 2016-12-02 (Fri, 02 Dec 2016)
Changed paths:
M config/companion_tools.in
M scripts/build/companion_tools.sh
M scripts/build/companion_tools/050-make.sh
M scripts/build/companion_tools/100-m4.sh
M scripts/build/companion_tools/200-autoconf.sh
M scripts/build/companion_tools/300-automake.sh
M scripts/build/companion_tools/400-libtool.sh
M scripts/crosstool-NG.sh.in
M steps.mk
Log Message:
-----------
Add 'companion tools for host' step.
Signed-off-by: Alexey Neyman <stilor@att.net>
Commit: bf0d593639d0c9451b13be4965bc6766cc90fed9
https://github.com/crosstool-ng/crosstool-ng/commit/bf0d593639d0c9451b13be4965bc6766cc90fed9
Author: Alexey Neyman <stilor@att.net>
Date: 2016-12-02 (Fri, 02 Dec 2016)
Changed paths:
M samples/x86_64-multilib-linux-uclibc,powerpc-unknown-elf/crosstool.config
Log Message:
-----------
Add comp. tools for host in one of canadian crosses.
Signed-off-by: Alexey Neyman <stilor@att.net>
Commit: 4042269de621e166235308f139e89c92e379040d
https://github.com/crosstool-ng/crosstool-ng/commit/4042269de621e166235308f139e89c92e379040d
Author: Alexey Neyman <stilor@att.net>
Date: 2016-12-02 (Fri, 02 Dec 2016)
Changed paths:
M config/companion_tools.in
M samples/x86_64-multilib-linux-uclibc,powerpc-unknown-elf/crosstool.config
M scripts/build/companion_tools.sh
M scripts/build/companion_tools/050-make.sh
M scripts/build/companion_tools/100-m4.sh
M scripts/build/companion_tools/200-autoconf.sh
M scripts/build/companion_tools/300-automake.sh
M scripts/build/companion_tools/400-libtool.sh
M scripts/crosstool-NG.sh.in
M steps.mk
Log Message:
-----------
Merge pull request #487 from stilor/host-comp-tools
Allow for installation of companion tools for host
Compare: https://github.com/crosstool-ng/crosstool-ng/compare/a787e410dc71...4042269de621
[-- Attachment #2: Type: text/plain, Size: 71 bytes --]
--
For unsubscribe information see http://sourceware.org/lists.html#faq
reply other threads:[~2016-12-03 3:19 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=584239a0a26ac_1ebf73fa5109a113c6333a@hookshot-fe-6dbb0c4.cp1-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).