How is libtool updated in GCC?

How is libtool updated in GCC?

[FX]

Hi,

libtool just released a new version to add support for OS X Yosemite (the old libtool had a poorly designed globbing pattern). It really is a one-line change (see https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63610#c7), but we need to incorporate it into the GCC code base and rebuild all our configure’s.

How is libtool handled in GCC? Do we import from upstream, or merge the changes that we need? It looks like it’s done manually and selectively, but I’d like confirmation of that.

Thanks,
FX

Re: How is libtool updated in GCC?

[Joseph Myers]

[-- Attachment #1: Type: text/plain, Size: 643 bytes --]

On Mon, 10 Nov 2014, FX wrote:

> How is libtool handled in GCC? Do we import from upstream, or merge the 
> changes that we need? It looks like it’s done manually and selectively, 
> but I’d like confirmation of that.

If you import rather than selectively merging one change you need (I 
think) to revert libtool commit 3334f7ed5851ef1e96b052f2984c4acdbf39e20c 
(incompatible with GCC handling of sysroots), as well as updating all 
three relevant repositories (GCC, binutils-gdb, src - I'm not sure if 
anything in binutils-gdb actually uses libtool but it has the files at 
toplevel).

-- 
Joseph S. Myers
joseph@codesourcery.com

Re: How is libtool updated in GCC?

[FX]

> If you import rather than selectively merging one change you need (I 
> think) to revert libtool commit 3334f7ed5851ef1e96b052f2984c4acdbf39e20c 
> (incompatible with GCC handling of sysroots), as well as updating all 
> three relevant repositories (GCC, binutils-gdb, src - I'm not sure if 
> anything in binutils-gdb actually uses libtool but it has the files at 
> toplevel).

So I’ve actually chosen to avoid the mess and selectly merge the one change that we need. Looking at the history of libtool.m4 in our tree, it looks like others have done that in the past, too.

Thanks for the feedback. On the src repository, is it documented somewhere how to change it? (I have probably done it in the past, but don’t remember)

FX

Re: How is libtool updated in GCC?

[Joseph Myers]

[-- Attachment #1: Type: text/plain, Size: 1082 bytes --]

On Tue, 11 Nov 2014, FX wrote:

> > If you import rather than selectively merging one change you need (I 
> > think) to revert libtool commit 3334f7ed5851ef1e96b052f2984c4acdbf39e20c 
> > (incompatible with GCC handling of sysroots), as well as updating all 
> > three relevant repositories (GCC, binutils-gdb, src - I'm not sure if 
> > anything in binutils-gdb actually uses libtool but it has the files at 
> > toplevel).
> 
> So I’ve actually chosen to avoid the mess and selectly merge the one 
> change that we need. Looking at the history of libtool.m4 in our tree, 
> it looks like others have done that in the past, too.
> 
> Thanks for the feedback. On the src repository, is it documented 
> somewhere how to change it? (I have probably done it in the past, but 
> don’t remember)

The src repository in this context is about newlib / libgloss.  Update the 
shared files, regenerate affected files in subdirectories with whatever 
version of auto* was previously used (which may not be fully consistent 
everywhere).

-- 
Joseph S. Myers
joseph@codesourcery.com