Re: [gentoo-amd64] Re: Unexpected side effect of GCC 4

[Peter Humphrey <prh@gotadsl.co.uk>]

On Sunday 05 November 2006 10:12, Duncan wrote:

> What about linux-headers and glibc?  The new glibc (2.5) has had some
> very strange interactions here.

Good point. On the firewall I have:
$ qpkg -v -I glibc
sys-libs/glibc-2.4-r3
$ qpkg -v -I linux-headers
sys-kernel/linux-headers-2.6.17-r1
$ uname -r
2.6.17-gentoo-r8
$ gcc-config -l
 [1] i686-pc-linux-gnu-3.4.6 *
 [2] i686-pc-linux-gnu-3.4.6-hardened
 [3] i686-pc-linux-gnu-3.4.6-hardenednopie
 [4] i686-pc-linux-gnu-3.4.6-hardenednopiessp
 [5] i686-pc-linux-gnu-3.4.6-hardenednossp
 [6] i686-pc-linux-gnu-4.1.1

and on the workstation I have:
$ qpkg -v -I glibc
/glibc-2.5
$ qpkg -v -I linux-headers
/linux-headers-2.6.17-r1
$ uname -r
2.6.18-gentoo-r1
$ gcc-config -l
 [1] x86_64-pc-linux-gnu-4.1.1 *
(I don't know what's causing qpkg to drop the first part of the package name 
on the workstation. Is this another pointer to glibc?)

<snip description of Duncan's problem>

> One of these days I'll do a full emerge --emptytree, and see if that
> fixes it,

I couldn't get GCC upgraded to 4.1 on this workstation - I got lots of 
unexplained compilation failures, especially in KDE packages, even though I 
was following the instructions carefully and (I hope) intelligently - so in 
the end I created another partition and installed a new 2006.1 system into 
it. (I'd forgotten how many days would be needed for that, even on this 
dual-Opteron-246 box with 4 GB. KDE takes an age. Perhaps I ought to look 
into putting /tmp and /var/tmp onto tmpfs.) I still had to jump through a 
few hoops to get the system installed at all: I remember having to 
emerge --sync on first mounting the already-populated /usr/portage 
partition during the early stages, and revdep-rebuild and fixpackages among 
other things. I couldn't even create a user until after rebooting. I know 
that's how the docs say to do it, but I've always created the user just 
after setting the root password - it seems more logical to me and I don't 
have to think so much. I've probably forgotten lots of other difficulties, 
but perseverance paid off.

> Anyway, if you are running glibc 2.5 on any of the machines, how does
> the sudden return to full speed rsyncing match up with the machines with
> 2.5, if at all.  What about the machine with my CFLAGS?  If they are
> related in any way, "enquiring minds want to know!"  =8^)  If your
> mystery is glibc 2.5 related as well, well then, I'll not feel so strange
> as at least there'll be two folks with a similar glibc 2.5 related
> mystery, which makes it less of one already! =8^)

The firewall box has been untouched and continues to run with glibc-2.4-r3 
and linux-headers-2.16.7-r1; that's the box with the rsync server. The 
workstation is the one with all the changes, being in fact a new 
installation from scratch. If I boot the old system, which I think has the 
same versions of glibc and linux-headers as the firewall box (I'll try that 
in a minute and let you know if it's otherwise), that's when I get ugly, 
crippled rsync; if I boot this present system, with the versions I listed 
at the top, rsync works as advertised. In other words, if this is a 
consequence of glibc, the old version is broken and the new one isn't - the 
converse of your experience, Duncan.

-- 
Rgds
Peter
-- 
gentoo-amd64@gentoo.org mailing list