From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1MyUmo-0007PB-Bm for garchives@archives.gentoo.org; Thu, 15 Oct 2009 18:10:50 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A157EE0512; Thu, 15 Oct 2009 18:10:46 +0000 (UTC) Received: from mail1.nippynetworks.com (mail.mailasail.com [212.227.250.41]) by pigeon.gentoo.org (Postfix) with ESMTP id 6ED34E0512 for ; Thu, 15 Oct 2009 18:10:46 +0000 (UTC) Received: from localhost (mail1.nippynetworks.com [127.0.2.1]) by mail1.nippynetworks.com (Postfix) with ESMTP id 706DA674116 for ; Thu, 15 Oct 2009 19:10:45 +0100 (BST) X-Virus-Scanned: amavisd-new at nippynetworks.com Received: from mail1.nippynetworks.com ([127.0.2.1]) by localhost (mail1.nippynetworks.com [127.0.2.1]) (amavisd-new, port 10024) with LMTP id 8679xEvI1znH for ; Thu, 15 Oct 2009 19:10:45 +0100 (BST) Received: from ed-wildgooses-macbook-pro.local (office.nippynetworks.com [94.194.201.187]) (Authenticated sender: edward@wildgooses.com) by mail1.nippynetworks.com (Postfix) with ESMTPSA id C4A8D67410B for ; Thu, 15 Oct 2009 19:10:44 +0100 (BST) Message-ID: <4AD765A2.4030703@wildgooses.com> Date: Thu, 15 Oct 2009 19:10:42 +0100 From: Ed W User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-hardened@lists.gentoo.org Reply-to: gentoo-hardened@lists.gentoo.org MIME-Version: 1.0 To: gentoo-hardened@lists.gentoo.org Subject: Re: [gentoo-hardened] NOTICE: GCC 4.3.4 going stable on Hardened References: <200910131602.39481.gengor@gentoo.org> <4AD60928.6090804@wildgooses.com> <4AD7435D.8070805@opensource.dyc.edu> In-Reply-To: <4AD7435D.8070805@opensource.dyc.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: da2b84f7-94d2-429e-b088-aa3a50bef66f X-Archives-Hash: 968d0882e84db40c360b35ad7f11ace6 basile wrote: > Yesterday I tried compiling gcc-4.3.2-r3 on a stock gentoo hardened > uclibc system (uclibc-0.9.28.3-r7) and hit all the bugs I remembered > hitting when I was helping Magnus with testing gcc-4* on uclibc. (Like > the fenv.h issue). > > The best success I've had is using the toolchain from the hardened-dev > overlay. This includes upgrading both gcc and uclibc: gcc-4.4.1-r2, > uclibc-0.9.30.1-r1, binutils-2.18-r3. I can emerge -e world with only > two issue, sandbox and python. Take a look at bug 275094 for some clues > on how to deal with python. I haven't really tackled sandbox yet. > Yeah, Natanael Copa wrote to me: > I have a hardened 4.4.1 working for x86 using the gentoo espf patches. I > needed 3 more patches: > > 1. work around the TLS issue (patch from PSM i think) > 2. work around the always-link-to-libgcc problem. > 3. hack to fool tell configure script that we dont have > _Unwind_getIPInfo I'm not actually sure which patches he is referencing, but it's at least one other confirmation that 4.4.1 is the best way ahead. Given we need to bump from 3.4.6, is it perhaps sensible to give a push towards 4.4.1 instead? The logic being whether it actually breaks less stuff on average than going to 4.3? Cheers Ed W