Francesco Talamona <[EMAIL PROTECTED]> writes: > On Sunday 27 March 2005 16:05, Harry Putnam wrote: >> Francesco Talamona <[EMAIL PROTECTED]> writes: >> >> 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" ? >> >> The system was installed 3 days ago from the most current 2004.3 >> livecd. I then used the stage2 approach. >> >> I ran emerge -sync yesterday >> >> gcc-config -l >> [1] i686-pc-linux-gnu-3.3.4 * > > What is the output of "emerge -p gcc", then?
Calculating dependencies ...done! [ebuild U ] sys-devel/gcc-3.3.5-r1 [3.3.4-r1] (-altivec) -bootstrap -boundschecking -build -debug +fortran* -gcj +gtk* -hardened (-ip28) (-multilib) -multislot (-n32) (-n64) +nls -nocxx -objc -static (-uclibc) 23,578 kB Total size of downloads: 23,578 kB Gack... > for a x86 "stable" box it should be > [ebuild NS ] sys-devel/gcc-3.3.5-r1 > <guessing> > You did a fresh sync, but didn't update packages > "emerge -pDuv world" should tell what to update. > </guessing> Yikes.. good guess. And maybe this is the source of some other probs I've been posting about. Can't try the remedy just now until the lenghthy compile of kde ends, which appears may be in the next millinium. But wait, I just thought... maybe it would be a good idea to kill that and take care of the updating ... seems maybe the build of kde will have problems otherwise. Do you think I should kill the kde build? It really does take a very long time.... -- [email protected] mailing list
