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