Hi!
On Thu, Apr 02, 2009 at 09:37:09AM -0600, RB wrote:
> I question whether your configurations are *precisely* the same. If I
> had to guess (and I do), I'd guess that the system in question wasn't
> wholly built with the -hardened toolchain.
Yesterday servers was upgraded to sys-libs/glibc-2.8_p20080602-r1.
After that I've rebuild everything (just for the case) using:
emerge linux-headers glibc binutils gcc-config gcc &&
emerge -1 libtool &&
emerge -b glibc binutils gcc portage &&
emerge -bke system &&
emerge -ke world
The `gcc-config -l` output is same on all servers:
[1] i686-pc-linux-gnu-3.4.6 *
[2] i686-pc-linux-gnu-3.4.6-hardenednopie
[3] i686-pc-linux-gnu-3.4.6-hardenednopiessp
[4] i686-pc-linux-gnu-3.4.6-hardenednossp
[5] i686-pc-linux-gnu-3.4.6-vanilla
Here is `emerge --info`:
server with this issue: http://powerman.name/tmp/emerge-info1
server without this issue: http://powerman.name/tmp/emerge-info2
/proc/config.gz on both servers are same (except compile date):
http://powerman.name/tmp/config1
As far as I able to check - server configurations are *same*.
--
WBR, Alex.
