[Top][All Lists]

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

Re: can I suppress "invalid unused variable name"?

From: Steve M. Robbins
Subject: Re: can I suppress "invalid unused variable name"?
Date: Thu, 2 Aug 2001 12:49:39 -0400
User-agent: Mutt/1.3.20i

On Thu, Aug 02, 2001 at 06:15:27PM +0200, Tim Van Holder wrote:
> This is really an automake issue,

Err, yes of course it is; I mistyped the address. :-/  
> so I'm sending it there.


However, you sent to bug-automake.  I'm re-sending to the automake
discussion list, since (a) I'm not sure it is a bug, and (b) someone
in the wider audience may know a workaround.


------------------------- original query ------------------------------


I am working with a library (CGAL) that is not autoconfigured, but has
its own system that generates a makefile fragment with important make
variables defined.  In particular, it defines CGAL_LDFLAGS.

In my, I use

        include $(CGAL_MAKEFILE)
        LDADD = ... $(CGAL_LDFLAGS) ...

and automake complains: invalid unused variable name: `CGAL_LDFLAGS'

[Incidentally, there used to be a line number attached to this diagnostic,
but that suddenly stopped. (??)]

Since automake does generate the correct output, I can
live with seeing this message all the time.  However, I am concerned
that this "warning" may change to an error in the future, and my
builds will suddenly break.  Thus I wonder: what is the automake-blessed
way to deal with including makefile fragments that define variables
that automake considers its own?

I used to be able to suppress this behaviour by a dummy assign to
CGAL_LDFLAGS (before including CGAL_MAKEFILE, of course!).  But that
trick has stopped working.


by Rocket to the Moon,
by Airplane to the Rocket,
by Taxi to the Airport,
by Frontdoor to the Taxi,
by throwing back the blanket and laying down the legs ...
- They Might Be Giants

reply via email to

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