Re: [PATCH] Add new 'AM_PROG_AR' macro, triggering the 'ar-lib' script.

[Stefano Lattarini]

Hi Peter, Hi Ralf, just a quick thought...

On Friday 17 September 2010, Peter Rosin wrote:
> Hi Ralf,
> 
> Den 2010-09-16 20:03 skrev Ralf Wildenhues:
> >> +
> >> +      if (! $seen_ar)
> >> +  {
> >> +    msg ('portability', $where,
> >> +         "`$onelib': linking libraries requires "
> >> +         . "`AM_PROG_AR' in `$configure_ac'")
> > 
> > I'm kinda wondering whether and how we can make this a bit less
> > daunting for the user.  Not sure whether to invent another
> > warning category, or mention "w32" here, or something else that
> > makes it clear that the world isn't going to end.  Below too, of
> > course.
> 
> But w32 is wrong too, since it doesn't affect GNU on w32. But I see
> your point, you want it to be just a hint, not a warning. Maybe it
> should just be a diagnostic message which doesn't cause automake
> -Wall -Werror to fail at all?
Or what about doing somethins similar to what gcc does, and add a new 
`-Wextra' category whose warnings are *not* enabled by `-Wall', but 
which, when enabled, still causes `automake -Werror' to fail?  This 
(assuming your warning will become an "extra" one) would also have the 
positive collateral effect of not forcing you to change *any* existing 
test.  WDYT?
> I'll wait for more input before I'm doing anything though, but if
> a new warning category or any other new infrastructure is needed
> I don't think I'm the top candidate for the job.
I think my proposal would only require adjusting/extending the 
existing infrastructure; I might give it a try if there's consensus.
 
Regards,
   Stefano