On Monday 19 January 2004 21:42, you wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Monday 19 January 2004 18:24, Thomas Mayer wrote:
> > this appears to be caused by a version mismatch between gcc and glibc
> > (been googleing around, the hint was not related to Gentoo, though).
> >
> > I had the same problem over the weekend emerging KDE-3.1.5, and did a
> >
> > # emerge glibc gcc lib-compat linux-headers
> >
> > which helped (ACCEPT_KEYWORDS="x86").
>
> hi thomas,
>
> i think i'm up to date. did you mean
> ACCEPT_KEYWORDS="~x86" ?
>
> *  sys-libs/glibc
>       Latest version available: 2.3.2-r9
>       Latest version installed: 2.3.2-r9
> *  sys-devel/gcc
>       Latest version available: 3.2.3-r3
>       Latest version installed: 3.2.3-r3
> *  sys-libs/lib-compat
>       Latest version available: 1.3
>       Latest version installed: 1.3
> *  sys-kernel/linux-headers
>       Latest version available: 2.4.19-r1
>       Latest version installed: 2.4.19-r1
>
>
> christian

Hi,

yep, obviously same versions here...

Try
 
# emerge --fetchonly glibc gcc lib-compat linux-headers

and watch out for what it does... it should download some packages/patches 
(what it did in my case)...

And, shame on me, I should have logged what I did...  I tend to stay on the 
'stable' branch, therefore, I definitely did not switch ACCEPT_KEYWORDS from 
"x86" to "~x86".

IIRC, I did a

# emerge --fetchonly  glibc gcc lib-compat linux-headers

first, which would download/update some files in /usr/portage/distfiles/, 
followed by the actual install:

# emerge glibc gcc lib-compat linux-headers

and afterwards, recompilation of arts-1.1.5 worked just fine.  Otherwise, I am 
at a loss here.

TM;-)

> - --
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.3 (GNU/Linux)
>
> iD8DBQFADEEoszmQKstIgt4RAqTSAKC9eSmEIszLpBVaScDrnp1lxD918wCfVUg3
> br6ewDw5znYwT0T9PGae8oE=
> =WtqR
> -----END PGP SIGNATURE-----


--
[EMAIL PROTECTED] mailing list

Reply via email to