From: "Benda XU" <heroxbd@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-libs/glibc/files/eblits/
Date: Mon, 6 Jun 2016 13:28:10 +0000 (UTC) [thread overview]
Message-ID: <1465219691.074751b72e6b44f264e1908e603205fa63cf6863.heroxbd@gentoo> (raw)
commit: 074751b72e6b44f264e1908e603205fa63cf6863
Author: Benda Xu <heroxbd <AT> gentoo <DOT> org>
AuthorDate: Mon Jun 6 13:25:34 2016 +0000
Commit: Benda XU <heroxbd <AT> gentoo <DOT> org>
CommitDate: Mon Jun 6 13:28:11 2016 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=074751b7
sys-libs/glibc: glibc_headers_install should use $(alt_prefix).
do not hardcode /usr/${CTARGET}.
sys-libs/glibc/files/eblits/src_install.eblit | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sys-libs/glibc/files/eblits/src_install.eblit b/sys-libs/glibc/files/eblits/src_install.eblit
index f0017fa..a23173e 100644
--- a/sys-libs/glibc/files/eblits/src_install.eblit
+++ b/sys-libs/glibc/files/eblits/src_install.eblit
@@ -212,7 +212,7 @@ toolchain-glibc_headers_install() {
# Make sure we install the sys-include symlink so that when
# we build a 2nd stage cross-compiler, gcc finds the target
# system headers correctly. See gcc/doc/gccinstall.info
- dosym usr/include /usr/${CTARGET}/sys-include
+ dosym usr/include $(alt_prefix)/sys-include
}
src_strip() {
next reply other threads:[~2016-06-06 13:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-06 13:28 Benda XU [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-01-07 13:49 [gentoo-commits] repo/gentoo:master commit in: sys-libs/glibc/files/eblits/ Benda XU
2016-12-07 7:03 Mike Frysinger
2016-11-25 5:50 Mike Frysinger
2016-09-03 11:06 Michał Górny
2016-06-19 23:19 Benda XU
2016-06-02 13:26 Benda XU
2016-06-02 8:08 Benda XU
2016-01-16 8:17 Mike Frysinger
2015-12-30 20:40 Mike Frysinger
2015-10-16 18:26 Mike Frysinger
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=1465219691.074751b72e6b44f264e1908e603205fa63cf6863.heroxbd@gentoo \
--to=heroxbd@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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