From: Alexey Neyman <stilor@att.net>
To: crossgcc@sourceware.org
Subject: [crosstool-ng/crosstool-ng] 120792: Sanitize CT_PREFIX_DIR, too
Date: Tue, 07 Mar 2017 02:52:00 -0000 [thread overview]
Message-ID: <58be207cb337_64b3f82263b5c3071693@hookshot-fe5-cp1-prd.iad.github.net.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 1014 bytes --]
Branch: refs/heads/master
Home: https://github.com/crosstool-ng/crosstool-ng
Commit: 120792a97d7d00be24e9501ec350447a16c0ff8a
https://github.com/crosstool-ng/crosstool-ng/commit/120792a97d7d00be24e9501ec350447a16c0ff8a
Author: Alexey Neyman <stilor@att.net>
Date: 2017-03-05 (Sun, 05 Mar 2017)
Changed paths:
M scripts/crosstool-NG.sh.in
Log Message:
-----------
Sanitize CT_PREFIX_DIR, too
Having .. in it breaks GCC's relocatability.
Signed-off-by: Alexey Neyman <stilor@att.net>
Commit: 272c010874b47ea50b653137e0d6e83a6543c318
https://github.com/crosstool-ng/crosstool-ng/commit/272c010874b47ea50b653137e0d6e83a6543c318
Author: Alexey Neyman <stilor@att.net>
Date: 2017-03-06 (Mon, 06 Mar 2017)
Changed paths:
M scripts/crosstool-NG.sh.in
Log Message:
-----------
Merge pull request #633 from stilor/double-dot-breaks-reloc
Sanitize CT_PREFIX_DIR, too
Compare: https://github.com/crosstool-ng/crosstool-ng/compare/489ea6d6df17...272c010874b4
reply other threads:[~2017-03-07 2:52 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=58be207cb337_64b3f82263b5c3071693@hookshot-fe5-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).