libtool-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: FYI: compensate compiler warnings and boilerplate (branch-1-5)


From: Ralf Wildenhues
Subject: Re: FYI: compensate compiler warnings and boilerplate (branch-1-5)
Date: Thu, 9 Jun 2005 19:05:14 +0200
User-agent: Mutt/1.4.1i

* Ralf Wildenhues wrote on Mon, Apr 18, 2005 at 07:07:54PM CEST:
> * Gary V. Vaughan wrote on Mon, Apr 11, 2005 at 05:08:06PM CEST:
> > Ralf Wildenhues wrote:
> 
> >>> _LT_TAGVAR(lt_simple_*_test_code, $1)="foo;\n"
> >>>
> >>> Which implies:
> >>>
> >>> # _LT_*_BOILERPLATE([TAG])
> 
> I don't have any idea how to proceed from here:

I've looked at this again, and, to tell you the truth, I don't believe
my original proposal is making matters much worse, given that I think a
clean fix would require quite a bit of work.

To put it another way: I would like permission to apply my patch as
proposed originally, to branch-2-0 and HEAD.  Evolution of
AC_LIBTOOL_LINKER_OPTION rather shows a trend away from encoding
language specifics in there, and I would love to be able to keep it that
way.  Also note that the Automake variables we use (ac_compile, for
example) work exactly the same way.

This patch is a predependence for another couple of patches I work on.

> Variable $_lt_linker_boilerplate is used from _LT_LINKER_OPTION, which
> has old name AC_LIBTOOL_LINKER_OPTION.  I assume it's published
> interface.  How can I adapt it to use TAG?

These two questions (first about published interface implied) have not
been answered.

> Set _lt_linker_boilerplate=_LT_TAGVAR(_lt_linker_boilerplate, $1) in
> _LT_LINKER_BOILERPLATE?  This would be ugly as hell again.  :(
> 
> Similar issue with AC_LIBTOOL_COMPILER_OPTION.  I don't think I can
> change these?

For the record: the proposed patch is[1].

Regards,
Ralf

[1] http://lists.gnu.org/archive/html/libtool-patches/2005-04/msg00080.html




reply via email to

[Prev in Thread] Current Thread [Next in Thread]