From: Gordon Malm <gengor@gentoo.org>
To: gentoo-hardened@lists.gentoo.org
Subject: Re: [gentoo-hardened] NOTICE: GCC 4.3.4 going stable on Hardened
Date: Thu, 15 Oct 2009 12:06:40 -0700 [thread overview]
Message-ID: <200910151206.40340.gengor@gentoo.org> (raw)
In-Reply-To: <4AD765A2.4030703@wildgooses.com>
On Thursday, October 15, 2009 11:10:42 Ed W wrote:
> 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
GCC 4.4.x & hardened gcc + uclibc issues are being worked on by Magnus and
crew of helpful people (tinhat folks have some representation too ;). Feel
free to come by #gentoo-hardened on irc.freenode.net and help hardened/uclibc
along if you are able to contribute.
I must object to "instead" terminology. GCC 4.3.x is current stable with the
rest of Gentoo as well, many other packages still require GCC 4.4.x porting.
It comes down to perspectives and goals. Hardened has been active, but
on "life support" for almost 2 years now. Due to time+manpower constraints,
the project has been forced to concentrate on our core which is the more
mainstream/traditional x86-32 & x86-64 installations. If you are very
uclibc/embedded oriented then yeah, its broke (so come help :).
Gordon Malm (gengor)
next prev parent reply other threads:[~2009-10-15 19:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-13 23:02 [gentoo-hardened] NOTICE: GCC 4.3.4 going stable on Hardened Gordon Malm
2009-10-13 23:52 ` Michael Orlitzky
2009-10-14 17:23 ` Ed W
2009-10-15 15:44 ` basile
2009-10-15 18:10 ` Ed W
2009-10-15 19:06 ` Gordon Malm [this message]
2009-10-30 23:49 ` Ed W
2009-10-24 11:02 ` Kakou
2009-10-24 12:50 ` Ed W
2009-10-24 12:57 ` Kakou
2009-10-24 15:20 ` Magnus Granberg
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=200910151206.40340.gengor@gentoo.org \
--to=gengor@gentoo.org \
--cc=gentoo-hardened@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