Mine (and as far as I can see all the others) were 3.3.4. It should be smart enough to to check and upgrade properly, otherwise why make it so complex if a user has to use (and be told about) an undocumented tool to correct a standard upgrade?
Also, not all the past upgrades failed this stuff - most worked OK. BillK On Thu, 2005-01-13 at 01:10 -0600, Boyd Stephen Smith Jr. wrote: > On Thursday 13 January 2005 12:30 am, "W.Kenworthy" <[EMAIL PROTECTED]> > wrote: > > Wrong rant: instead it should be: "why doesnt the ebuild run > > 'fix_libtool_files.sh 3.3.4' properly after the upgrade?" > > Becuase your current gcc profile isn't necessarily 3.3.4? I'm not sure if > that's a problem or not. > -- [email protected] mailing list
