Ralf Wildenhues wrote: > * Peter O'Gorman wrote on Thu, Aug 07, 2008 at 07:01:48PM CEST: >> Paolo Bonzini wrote: >>>> That said, updating in trunk is a different matter. There, the question >>>> IMHO is mostly which libtool version to update to. The git version may >>>> still have a regression or two, but 2.2.4 doesn't have the -fPIC on >>>> HP/IA patch from Steve (which would be trivial to backport of course). >>>> Alternatively GCC can wait for 2.2.6 (hopefully in the "couple of weeks >>>> at most" time frame). >>> Updating to 2.2.6 would be okay for me. >> Thanks. I'll test quickly with current libtool git now, and will test >> more thoroughly and submit a patch when libtool-2.2.6 is released. > > FWIW, a quick test with current git Libtool shows no problems on > GNU/Linux.
Yes, I tried it also - http://pogma.com/misc/gcc-libtool-git20080810.patch (Slight change to ltgcc.m4, otherwise git libtool + generated files). I plan on testing more widely next weekend and proposing a patch the following week, regardless of whether libtool-2.2.6 is released. (Unless Ralph would prefer to do it?) I'll try lighting a fire under Gary too :-) Peter -- Peter O'Gorman http://pogma.com
