From: Alexey Neyman <stilor@att.net>
To: crossgcc@sourceware.org
Subject: [crosstool-ng/crosstool-ng] 6cdf0d: Use CHOST instead of CROSS_PREFIX
Date: Tue, 07 Mar 2017 16:51:00 -0000 [thread overview]
Message-ID: <58bee518d9f34_8633f8fc131dc3415879b@hookshot-fe5-cp1-prd.iad.github.net.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 1641 bytes --]
Branch: refs/heads/master
Home: https://github.com/crosstool-ng/crosstool-ng
Commit: 6cdf0df01be9bd4befd9509df07354c0f4461a32
https://github.com/crosstool-ng/crosstool-ng/commit/6cdf0df01be9bd4befd9509df07354c0f4461a32
Author: Alexey Neyman <stilor@att.net>
Date: 2017-03-06 (Mon, 06 Mar 2017)
Changed paths:
M scripts/build/companion_libs/050-zlib.sh
Log Message:
-----------
Use CHOST instead of CROSS_PREFIX
The latter does not prevent zlib's configure from overriding 'AR' with
/usr/bin/libtool on macos, and that breaks canadian crosses.
Signed-off-by: Alexey Neyman <stilor@att.net>
Commit: b3b94e4807f4048ce924c9f1776a1bd2df740d0b
https://github.com/crosstool-ng/crosstool-ng/commit/b3b94e4807f4048ce924c9f1776a1bd2df740d0b
Author: Alexey Neyman <stilor@att.net>
Date: 2017-03-06 (Mon, 06 Mar 2017)
Changed paths:
M scripts/build/cc/100-gcc.sh
Log Message:
-----------
Only add clang-specific flags to clang
I.e., only to CFLAGS_FOR_BUILD if the build is canadian.
Signed-off-by: Alexey Neyman <stilor@att.net>
Commit: 456cccc0a7b4410088ac22b6473dfda94a83bc86
https://github.com/crosstool-ng/crosstool-ng/commit/456cccc0a7b4410088ac22b6473dfda94a83bc86
Author: Alexey Neyman <stilor@att.net>
Date: 2017-03-07 (Tue, 07 Mar 2017)
Changed paths:
M scripts/build/cc/100-gcc.sh
M scripts/build/companion_libs/050-zlib.sh
Log Message:
-----------
Merge pull request #634 from stilor/macos-canadian
A couple of fixes for canadian samples on macos
Compare: https://github.com/crosstool-ng/crosstool-ng/compare/ea7f559ef4f4...456cccc0a7b4
reply other threads:[~2017-03-07 16:51 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=58bee518d9f34_8633f8fc131dc3415879b@hookshot-fe5-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).