From: "Anthony G. Basile" <blueness@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/hardened-dev:musl commit in: sys-devel/gcc/, sys-devel/gcc/files/
Date: Fri, 24 Oct 2014 21:51:32 +0000 (UTC) [thread overview]
Message-ID: <1414187567.62ea25d913176e609e6b0ddb21ea07e96bf5de70.blueness@gentoo> (raw)
commit: 62ea25d913176e609e6b0ddb21ea07e96bf5de70
Author: Anthony G. Basile <blueness <AT> gentoo <DOT> org>
AuthorDate: Fri Oct 24 21:52:47 2014 +0000
Commit: Anthony G. Basile <blueness <AT> gentoo <DOT> org>
CommitDate: Fri Oct 24 21:52:47 2014 +0000
URL: http://sources.gentoo.org/gitweb/?p=proj/hardened-dev.git;a=commit;h=62ea25d9
sys-devel/gcc: fix build USE=gcj, bug #526618
Package-Manager: portage-2.2.8-r2
Manifest-Sign-Key: 0xF52D4BBA
---
sys-devel/gcc/files/gcc-4.8.3-musl-fix-libc5-assumption.patch | 11 +++++++++++
sys-devel/gcc/gcc-4.8.3-r99.ebuild | 1 +
2 files changed, 12 insertions(+)
diff --git a/sys-devel/gcc/files/gcc-4.8.3-musl-fix-libc5-assumption.patch b/sys-devel/gcc/files/gcc-4.8.3-musl-fix-libc5-assumption.patch
new file mode 100644
index 0000000..65bc45e
--- /dev/null
+++ b/sys-devel/gcc/files/gcc-4.8.3-musl-fix-libc5-assumption.patch
@@ -0,0 +1,11 @@
+--- /var/tmp/portage/sys-devel/gcc-4.8.3-r99/work/gcc-4.8.3/boehm-gc/os_dep.c 2013-03-06 15:08:58.000000000 +0000
++++ gcc-4.8.3.new/boehm-gc/os_dep.c 2014-10-24 18:25:39.963379871 +0000
+@@ -41,7 +41,7 @@
+ # else /* not 2 <= __GLIBC__ */
+ /* libc5 doesn't have <sigcontext.h>: go directly with the kernel */
+ /* one. Check LINUX_VERSION_CODE to see which we should reference. */
+-# include <asm/sigcontext.h>
++//# include <asm/sigcontext.h>
+ # endif /* 2 <= __GLIBC__ */
+ # endif
+ # endif
diff --git a/sys-devel/gcc/gcc-4.8.3-r99.ebuild b/sys-devel/gcc/gcc-4.8.3-r99.ebuild
index b96acf6..deb1c76 100644
--- a/sys-devel/gcc/gcc-4.8.3-r99.ebuild
+++ b/sys-devel/gcc/gcc-4.8.3-r99.ebuild
@@ -58,6 +58,7 @@ src_prepare() {
cp -r libitm/config/generic libitm/config/linux/x86
epatch "${FILESDIR}"/${PN}-4.7.3-musl-linker-path.patch
epatch "${FILESDIR}"/${PN}-4.8.3-musl-res_state.patch
+ epatch "${FILESDIR}"/${PN}-4.8.3-musl-fix-libc5-assumption.patch
fi
use vanilla && return 0
next reply other threads:[~2014-10-24 21:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 21:51 Anthony G. Basile [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-11-04 18:53 [gentoo-commits] proj/hardened-dev:musl commit in: sys-devel/gcc/, sys-devel/gcc/files/ Anthony G. Basile
2014-08-31 16:56 Anthony G. Basile
2014-08-31 16:56 Anthony G. Basile
2014-02-27 13:15 Anthony G. Basile
2014-01-25 19:51 Anthony G. Basile
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=1414187567.62ea25d913176e609e6b0ddb21ea07e96bf5de70.blueness@gentoo \
--to=blueness@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