From: Alexey Neyman <stilor@att.net>
To: crossgcc@sourceware.org
Subject: [crosstool-ng/crosstool-ng] 7111f9: MinGW-W64 fixes
Date: Fri, 31 Mar 2017 17:24:00 -0000 [thread overview]
Message-ID: <58de90d775df0_7e623f9f5eb2dc24763d@hookshot-fe2-cp1-prd.iad.github.net.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 1766 bytes --]
Branch: refs/heads/master
Home: https://github.com/crosstool-ng/crosstool-ng
Commit: 7111f95dc3513e52ea0c69776432102fb6967498
https://github.com/crosstool-ng/crosstool-ng/commit/7111f95dc3513e52ea0c69776432102fb6967498
Author: Alexey Neyman <stilor@att.net>
Date: 2017-03-30 (Thu, 30 Mar 2017)
Changed paths:
M config/libc/mingw.in
M samples/x86_64-w64-mingw32/crosstool.config
M scripts/build/libc/glibc.sh
M scripts/build/libc/mingw.sh
Log Message:
-----------
MinGW-W64 fixes
- libpthread requires iteration over multilibs, unlike the core, it
does not detect and build multilibs by itself.
- Disable parallel builds for mingw-w64 components; until mingw-w64 core
builds clean, I am not trusting it.
- Make the list of tools to build configurable
- Turn on multilib in x86_64 sample.
- Make warnings about tuple less redundant. As in, "one WARN is enough,
no need to shout it three times".
- Messages about various steps/substeps are more aligned with the rest
of the components.
- Use 'make' instead of ${make} to invoke the companion make just built,
if applicable.
Signed-off-by: Alexey Neyman <stilor@att.net>
Commit: 88d28e6eed547e9992c44c6894764dd7b000b980
https://github.com/crosstool-ng/crosstool-ng/commit/88d28e6eed547e9992c44c6894764dd7b000b980
Author: Alexey Neyman <stilor@att.net>
Date: 2017-03-31 (Fri, 31 Mar 2017)
Changed paths:
M config/libc/mingw.in
M samples/x86_64-w64-mingw32/crosstool.config
M scripts/build/libc/glibc.sh
M scripts/build/libc/mingw.sh
Log Message:
-----------
Merge pull request #669 from stilor/mingw-pthread-multilib
MinGW-W64 fixes
Compare: https://github.com/crosstool-ng/crosstool-ng/compare/a7edff1820d8...88d28e6eed54
reply other threads:[~2017-03-31 17:24 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=58de90d775df0_7e623f9f5eb2dc24763d@hookshot-fe2-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).