| 1 |
On Sunday 05 November 2006 11:50, Peter Humphrey wrote: |
| 2 |
> On Sunday 05 November 2006 10:12, Duncan wrote: |
| 3 |
> > What about linux-headers and glibc? The new glibc (2.5) has had some |
| 4 |
> > very strange interactions here. |
| 5 |
> |
| 6 |
> Good point. On the firewall I have: |
| 7 |
> $ qpkg -v -I glibc |
| 8 |
> sys-libs/glibc-2.4-r3 |
| 9 |
> $ qpkg -v -I linux-headers |
| 10 |
> sys-kernel/linux-headers-2.6.17-r1 |
| 11 |
> $ uname -r |
| 12 |
> 2.6.17-gentoo-r8 |
| 13 |
> $ gcc-config -l |
| 14 |
> [1] i686-pc-linux-gnu-3.4.6 * |
| 15 |
> [2] i686-pc-linux-gnu-3.4.6-hardened |
| 16 |
> [3] i686-pc-linux-gnu-3.4.6-hardenednopie |
| 17 |
> [4] i686-pc-linux-gnu-3.4.6-hardenednopiessp |
| 18 |
> [5] i686-pc-linux-gnu-3.4.6-hardenednossp |
| 19 |
> [6] i686-pc-linux-gnu-4.1.1 |
| 20 |
> |
| 21 |
> and on the workstation I have: |
| 22 |
> $ qpkg -v -I glibc |
| 23 |
> /glibc-2.5 |
| 24 |
> $ qpkg -v -I linux-headers |
| 25 |
> /linux-headers-2.6.17-r1 |
| 26 |
> $ uname -r |
| 27 |
> 2.6.18-gentoo-r1 |
| 28 |
> $ gcc-config -l |
| 29 |
> [1] x86_64-pc-linux-gnu-4.1.1 * |
| 30 |
> (I don't know what's causing qpkg to drop the first part of the package |
| 31 |
> name on the workstation. Is this another pointer to glibc?) |
| 32 |
|
| 33 |
[...] |
| 34 |
|
| 35 |
> The firewall box has been untouched and continues to run with |
| 36 |
> glibc-2.4-r3 and linux-headers-2.16.7-r1; that's the box with the rsync |
| 37 |
> server. The workstation is the one with all the changes, being in fact a |
| 38 |
> new installation from scratch. If I boot the old system, which I think |
| 39 |
> has the same versions of glibc and linux-headers as the firewall box |
| 40 |
> (I'll try that in a minute and let you know if it's otherwise), |
| 41 |
|
| 42 |
In fact the old workstation system is like this (I'm running it now): |
| 43 |
$ qpkg -v -I glibc |
| 44 |
/glibc-2.5 |
| 45 |
$ qpkg -v -I linux-headers |
| 46 |
/linux-headers-2.6.17-r1 |
| 47 |
prh@wstn ~ $ uname -r |
| 48 |
2.6.18-gentoo-r1 |
| 49 |
prh@wstn ~ $ gcc-config -l |
| 50 |
[1] x86_64-pc-linux-gnu-3.4.6 * |
| 51 |
[2] x86_64-pc-linux-gnu-3.4.6-hardened |
| 52 |
[3] x86_64-pc-linux-gnu-3.4.6-hardenednopie |
| 53 |
[4] x86_64-pc-linux-gnu-3.4.6-hardenednopiessp |
| 54 |
[5] x86_64-pc-linux-gnu-3.4.6-hardenednossp |
| 55 |
[6] x86_64-pc-linux-gnu-4.1.1 |
| 56 |
$ emerge --info | grep FLAGS |
| 57 |
CFLAGS="-march=k8 -Os -pipe -frename-registers -fweb -freorder-blocks -freorder-blocks-and-partition -funit-at-a-time -fgcse-sm -fgcse-las -fgcse-after-reload -fmerge-all-constants" |
| 58 |
CXXFLAGS="-march=k8 -Os -pipe -frename-registers -fweb -freorder-blocks -funit-at-a-time -fgcse-sm -fgcse-las -fgcse-after-reload -fmerge-all-constants" |
| 59 |
Unset: CTARGET, INSTALL_MASK, LDFLAGS, PORTAGE_RSYNC_EXTRA_OPTS |
| 60 |
(Note the partial package name reported by qpkg.) |
| 61 |
|
| 62 |
So I have a pointer away from glibc and linux-headers. CFLAGS on the new |
| 63 |
system are as on the old but with -combine added.The old and new systems |
| 64 |
have the same versions of kernel, linux-headers and glibc, but different |
| 65 |
versions of gcc. Rsync is crippled on the old system but fine on the new |
| 66 |
one. |
| 67 |
|
| 68 |
-- |
| 69 |
Rgds |
| 70 |
Peter |
| 71 |
-- |
| 72 |
gentoo-amd64@g.o mailing list |
Archives