On Sunday 27 March 2005 14:13, Harry Putnam wrote:
> > Running genlop gcc produces:
> >
> > * sys-devel/gcc
> >
> > Wed Oct 27 17:25:47 2004 >>> sys-devel/gcc-3.3.4-r1
> > Wed Oct 27 17:34:25 2004 >>> sys-devel/gcc-3.3.4-r1
> >
> > So does it mean the same version was installed twice?
Yes, but doesn't mean necessarily that two gcc with different versions
are residing on your pc. (I don't think you are cross-compiling, you
would be aware of it!)
Ten minutes between two gcc install may mean that the second install was
issued from a precompiled package. (In my box gcc-3.3.4 took about half
an hour to compile; ok there wasn't so plenty of RAM as in signature
then, but the rest is the same)
>
> Ok, I tried running the command suggested in
> fix_libtool_files.sh
> `fix_libtool_files.sh `gcc -dumpversion` --oldarch i386-pc-linux-gnu
>
> Setting i386 as old target. And did see some `fixing' output on kde
> libs:
> * FIXING: /usr/lib/libaspell.la ... [c]
> * FIXING: /usr/lib/libpspell.la ... [c]
>
> So trying again with `emerge -v -k kdelibs'
>
> But I noticed that the portage tree does not contain my version of
> gcc gcc-3.3.4-r1 it jumps from 3.3.2 to 3.3.5
>
> Is that significant?
It is no more in portage, period.
But this make me think your system is quite dated, when did you do an
"emerge --sync" last time?
Furthermore, what is the output of "gcc-config -l" ?
Ciao
Francesco
--
Linux Version 2.6.12-rc1, Compiled #7 Sun Mar 20 08:26:19 CET 2005
One 1.53GHz AMD Athlon XP Processor, 2.5GB RAM, 3022.84 Bogomips Total
macula
--
[email protected] mailing list
