From: Alexey Neyman <stilor@att.net>
To: crossgcc@sourceware.org
Subject: [crosstool-ng/crosstool-ng] d6bf8e: Fix symlinking to multiarch tools on Cygwin
Date: Sun, 02 Apr 2017 02:10:00 -0000 [thread overview]
Message-ID: <58e05d799c9e6_23053fd281f9bc38955e5@hookshot-fe3-cp1-prd.iad.github.net.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 1374 bytes --]
Branch: refs/heads/master
Home: https://github.com/crosstool-ng/crosstool-ng
Commit: d6bf8e2d9866c6c3618e5053aca01df7fe7d61d0
https://github.com/crosstool-ng/crosstool-ng/commit/d6bf8e2d9866c6c3618e5053aca01df7fe7d61d0
Author: Alexey Neyman <stilor@att.net>
Date: 2017-04-01 (Sat, 01 Apr 2017)
Changed paths:
M scripts/build/binutils/binutils.sh
M scripts/functions
Log Message:
-----------
Fix symlinking to multiarch tools on Cygwin
On cygwin, creating both "foo.exe" and "foo" results in 'ln -sf'
returning an error ("File exists"). However, ln silently removes
the "foo.exe" in this case, so an attempt to re-run the same command
manually then succeeds.
Hence, make binutils.sh also create symlinks with .exe prefix,
using the new & shiny routine.
Signed-off-by: Alexey Neyman <stilor@att.net>
Commit: ba3d47b9d6b50fd60d43e0e2019dcafdd39d3c10
https://github.com/crosstool-ng/crosstool-ng/commit/ba3d47b9d6b50fd60d43e0e2019dcafdd39d3c10
Author: Alexey Neyman <stilor@att.net>
Date: 2017-04-01 (Sat, 01 Apr 2017)
Changed paths:
M scripts/build/binutils/binutils.sh
M scripts/functions
Log Message:
-----------
Merge pull request #670 from stilor/cygwin-symlink
Fix symlinking to multiarch tools on Cygwin
Compare: https://github.com/crosstool-ng/crosstool-ng/compare/88d28e6eed54...ba3d47b9d6b5
reply other threads:[~2017-04-02 2:10 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=58e05d799c9e6_23053fd281f9bc38955e5@hookshot-fe3-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).