| 1 |
Hi Toth, |
| 2 |
|
| 3 |
You're getting that error because you have something compiled with |
| 4 |
gcc-3. Make sure you're using gcc-4.4.4-r2 with the hardened specs. If |
| 5 |
you do gcc-config -l, you should see something like this: |
| 6 |
|
| 7 |
blueness@whiteness ~ $ gcc-config -l |
| 8 |
[1] x86_64-pc-linux-gnu-4.4.4 * |
| 9 |
[2] x86_64-pc-linux-gnu-4.4.4-hardenednopie |
| 10 |
[3] x86_64-pc-linux-gnu-4.4.4-hardenednopiessp |
| 11 |
[4] x86_64-pc-linux-gnu-4.4.4-hardenednossp |
| 12 |
[5] x86_64-pc-linux-gnu-4.4.4-vanilla |
| 13 |
|
| 14 |
We're not supporting hardening on gcc-3 anymore. |
| 15 |
|
| 16 |
On 02/10/2011 07:17 AM, "Tóth Attila" wrote: |
| 17 |
> Some binaries are failing since the last glibc upgrade like this: |
| 18 |
> - |
| 19 |
> binaryname: relocation error: binaryname: symbol __guard, version |
| 20 |
> GLIBC_2.3.2 not defined in file libc.so.6 with link time reference |
| 21 |
> - |
| 22 |
> I'm actually surprised how well my machines doing despite this problem. |
| 23 |
> |
| 24 |
> For those who have the same problem, you can search for affected binaries |
| 25 |
> using this command: |
| 26 |
> - |
| 27 |
> scanelf -qRs __guard /bin /lib /sbin /usr/bin /usr/lib /usr/sbin /opt |
| 28 |
> /var/www/ |
| 29 |
> - |
| 30 |
> |
| 31 |
> - |
| 32 |
> equery belongs path/binary |
| 33 |
> - |
| 34 |
> command can be used to query for which package the binary belongs to. |
| 35 |
> |
| 36 |
> Can somebody update me on the nature of the problem? Is it an intended |
| 37 |
> movement to drop __guard? I know, that it's obsolete. I would suggest to |
| 38 |
> communicate this in an enews or whatever for all hardened users. Or I may |
| 39 |
> be the only one, who rolls the system without regular world recompiles? |
| 40 |
> |
| 41 |
> Regards: |
| 42 |
> Dwokfur |
| 43 |
|
| 44 |
|
| 45 |
-- |
| 46 |
Anthony G. Basile, Ph.D. |
| 47 |
Gentoo Developer |
Archives