Mark Haney wrote: > Duncan wrote: >> "Mark Haney" <[email protected]> posted >> [email protected], excerpted below, on Thu, 22 Jan 2009 >> 07:48:44 -0500: >> >>>> I'll try to remember to repost after today's sync and updates, with the >>>> results for 4.1.4. >> $ equery l libkdepim >> [ Searching for package 'libkdepim' in all categories among: ] >> * installed packages >> [I--] [ ~] kde-base/libkdepim-3.5.10 (3.5) >> [I--] [ ~] kde-base/libkdepim-4.1.4 (4.1) >> $ >> >> So 4.1.4 merged without issue, here. >> >> What gcc are you running? I'm running 4.3.2-r2 as my main compiler here, >> with 4.2.something as a backup I can gcc-config to if necessary. But I >> remember that the libstdc++ for 4.3 deprecated some things, including >> IIRC something about std::. It has been some time (we're talking 4.3.0 >> and as mentioned I'm on 4.3.2-r2 now, after all) and I don't recall the >> details, but it's possible that's related. >> >> BTW, the update I just did, did want to update gcc-4.2.4 to 4.2.4-r1 >> here, but failed. I've not looked into why yet, but as I said, I don't >> use 4.2 for much any more anyway, and gcc-config has the 4.3.2 slot >> selected unless I run into problems, which I haven't recently. I'll >> probably just unmerge 4.2.4 at some point (I haven't yet only because >> I've not yet done a full emerge --emptytree @system @world since I >> switched), and not worry about it if the build failure isn't something >> stupidly simple to fix. >> > > My gcc is 4.1.2. I've not updated gcc in quite a while as you can see. > Could the age of my compiler be the problem? > >
One more thing, when I looked at gcc versions available on my system 4.1.2 is the latest stable one. I take it that 4.3.2 is in ~amd64? -- Frustra laborant quotquot se calculationibus fatigant pro inventione quadraturae circuli Mark Haney Sr. Systems Administrator ERC Broadband (828) 350-2415 Call (866) ERC-7110 for after hours support
