From: Bryan Hundven <bryanhundven@gmail.com>
To: crossgcc@sourceware.org
Subject: [crosstool-ng/crosstool-ng] 10972b: binutils: make symlinks in a consistent way
Date: Sun, 18 Sep 2016 05:18:00 -0000 [thread overview]
Message-ID: <57de23ae681ba_4b5e3f893bf7b134702e1@hookshot-fe1-cp1-prd.iad.github.net.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 1614 bytes --]
Branch: refs/heads/master
Home: https://github.com/crosstool-ng/crosstool-ng
Commit: 10972baa20e2d96e77204a6d48839dc0d4f21d77
https://github.com/crosstool-ng/crosstool-ng/commit/10972baa20e2d96e77204a6d48839dc0d4f21d77
Author: Kirill K. Smirnov <kirill.k.smirnov@gmail.com>
Date: 2016-09-13 (Tue, 13 Sep 2016)
Changed paths:
M scripts/build/binutils/binutils.sh
Log Message:
-----------
binutils: make symlinks in a consistent way
On the stage "core gcc pass-2" the following layout is created:
1) buildtools/bin/TARGET-{ar,as,elf2flt,flthdr,ld,ld.bfd,ranlib,strip}
2) buildtools/TARGET/bin/{ar,as,elf2flt,flthdr,ld,ld.bfd,ranlib,strip}
3) x-tools/TARGET/bin/TARGET-{ar,as,elf2flt,flthdr,ld,ld.bfd,ranlib,strip}
4) x-tools/TARGET/TARGET/bin{ar,as,elf2flt,flthdr,ld,ld.bfd,ranlib,strip}
where both (1) and (2) are symlinks to (3). This effectively renders
core pass-2 gcc with elf2flt linker unusable.
Related elf2flt discussion:
https://github.com/crosstool-ng/crosstool-ng/pull/443
Signed-off-by: Kirill K. Smirnov <kirill.k.smirnov@gmail.com>
Commit: a24f06337c9efeea250916529c1c11e4f8b53932
https://github.com/crosstool-ng/crosstool-ng/commit/a24f06337c9efeea250916529c1c11e4f8b53932
Author: Bryan Hundven <bryanhundven@gmail.com>
Date: 2016-09-17 (Sat, 17 Sep 2016)
Changed paths:
M scripts/build/binutils/binutils.sh
Log Message:
-----------
Merge pull request #448 from KirillSmirnov/binutils-symlinks
binutils: make symlinks in a consistent way
Compare: https://github.com/crosstool-ng/crosstool-ng/compare/290ae52db3cc...a24f06337c9e
[-- Attachment #2: Type: text/plain, Size: 71 bytes --]
--
For unsubscribe information see http://sourceware.org/lists.html#faq
reply other threads:[~2016-09-18 5:18 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=57de23ae681ba_4b5e3f893bf7b134702e1@hookshot-fe1-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).