From: Alexey Neyman <stilor@att.net>
To: crossgcc@sourceware.org
Subject: [crosstool-ng/crosstool-ng] e697b4: Create glibc-ports symlink inside CT_SRC_DIR
Date: Tue, 16 Oct 2018 07:04:00 -0000 [thread overview]
Message-ID: <5bc58d8f2bc0a_12332ad8476fc5805851b@hookshot-fe-2cc8887.cp1-iad.github.net.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 1302 bytes --]
Branch: refs/heads/master
Home: https://github.com/crosstool-ng/crosstool-ng
Commit: e697b4694aab48334ce3984e423157a4754bb6e2
https://github.com/crosstool-ng/crosstool-ng/commit/e697b4694aab48334ce3984e423157a4754bb6e2
Author: Alexey Neyman <stilor@att.net>
Date: 2018-10-16 (Tue, 16 Oct 2018)
Changed paths:
M scripts/build/libc/glibc.sh
Log Message:
-----------
Create glibc-ports symlink inside CT_SRC_DIR
... so that it works in both "bundled" and "bundled,local" cases.
Fixes #1060.
Signed-off-by: Alexey Neyman <stilor@att.net>
Commit: 6a21d9bcfc3382a3fb722646fe9d3383452a42e5
https://github.com/crosstool-ng/crosstool-ng/commit/6a21d9bcfc3382a3fb722646fe9d3383452a42e5
Author: Alexey Neyman <stilor@att.net>
Date: 2018-10-16 (Tue, 16 Oct 2018)
Changed paths:
M scripts/build/libc/glibc.sh
Log Message:
-----------
Merge pull request #1061 from stilor/fix-glibc-ports-symlink
Create glibc-ports symlink inside CT_SRC_DIR
Compare: https://github.com/crosstool-ng/crosstool-ng/compare/d19c46f8d5d1...6a21d9bcfc33
**NOTE:** This service has been marked for deprecation: https://developer.github.com/changes/2018-04-25-github-services-deprecation/
Functionality will be removed from GitHub.com on January 31st, 2019.
reply other threads:[~2018-10-16 7:04 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=5bc58d8f2bc0a_12332ad8476fc5805851b@hookshot-fe-2cc8887.cp1-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).