Hello, * Ollie Wild wrote on Fri, Nov 19, 2010 at 02:46:46AM CET: > On Wed, Nov 10, 2010 at 1:41 PM, Ralf Wildenhues wrote: > > > > I'm pushing the patch with the diff below squashed in, hope you > > don't mind. > > Ralf, being as you're a dual libtool / GCC maintainer, what is the > process for getting libtool changes pushed to GCC? Do I just wait for > a new libtool release, or is it reasonable / preferred to send > individual patches to GCC as well?
Well, we want to import the newer Libtool files in GCC, esp. in order to get LTO fixed, but the current libtool.m4 will cause --with-sysroot regressions because GCC's and Libtool's idea of that switch are different. Paolo, have you had any chance to look into this yet? Generally, importing files from Libtool to GCC is documented in <http://gcc.gnu.org/codingconventions.html>; you typically copy them over, and either do a full build with --enable-maintainer-mode, or run autoreconf -v in every directory containing a configure script. And of course test the resulting patch in every way you can conceive of it causing regressions. ;-) Changes to Libtool files should first be proposed and pushed upstream then imported into GCC, in general. Cheers, Ralf
