From: Bryan Hundven <bryanhundven@gmail.com>
To: crossgcc@sourceware.org
Subject: [crosstool-ng/crosstool-ng] 9820e4: musl-libc: Rewrite musl.sh build script
Date: Tue, 01 Mar 2016 02:07:00 -0000 [thread overview]
Message-ID: <56d4f96434f28_2fe73fc4a86552a09192e@hookshot-fe6-cp1-prd.iad.github.net.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 1288 bytes --]
Branch: refs/heads/master
Home: https://github.com/crosstool-ng/crosstool-ng
Commit: 9820e4eea52326881b1434936bc6839934348f73
https://github.com/crosstool-ng/crosstool-ng/commit/9820e4eea52326881b1434936bc6839934348f73
Author: Bryan Hundven <bryanhundven@gmail.com>
Date: 2016-02-29 (Mon, 29 Feb 2016)
Changed paths:
M scripts/build/libc/musl.sh
Log Message:
-----------
musl-libc: Rewrite musl.sh build script
This commit moves the do_libc_configure function to do_libc_backend and
switches do_libc_start_files and do_libc_final to call do_libc_backend.
The major reason for the rewrite is that musl => 1.1.13 has had it's own
build system rewritten and can now build out-of-tree.
Signed-off-by: Bryan Hundven <bryanhundven@gmail.com>
Commit: 785dbce3510a1d0b2ec51873230d2001ed50eae7
https://github.com/crosstool-ng/crosstool-ng/commit/785dbce3510a1d0b2ec51873230d2001ed50eae7
Author: Bryan Hundven <bryanhundven@gmail.com>
Date: 2016-02-29 (Mon, 29 Feb 2016)
Changed paths:
M scripts/build/libc/musl.sh
Log Message:
-----------
Merge pull request #359 from bhundven/fix_musl_libc_build
musl-libc: Rewrite musl.sh build script
Compare: https://github.com/crosstool-ng/crosstool-ng/compare/38bac5781acf...785dbce3510a
[-- Attachment #2: Type: text/plain, Size: 71 bytes --]
--
For unsubscribe information see http://sourceware.org/lists.html#faq
reply other threads:[~2016-03-01 2:07 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=56d4f96434f28_2fe73fc4a86552a09192e@hookshot-fe6-cp1-prd.iad.github.net.mail \
--to=bryanhundven@gmail.com \
--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).