Re: compilation flags per object file

[Mark D. Baushke]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ralf Wildenhues <address@hidden> writes:

> Hello Bruno, Mark,
> 
> * Mark D. Baushke wrote on Fri, Aug 25, 2006 at 06:01:03PM CEST:
> > 
> > There should be no ambiguity if you add the $(ext) to the
> > makefile macro name:
> > 
> > localcharset($ext)_CPPFLAGS = $(AM_CPPFLAGS) -DLIBDIR=\"$(libdir)\"
> > 
> > and then use $($*$(ext)_CPPDFLAGS) in rules that need it.
> 
> It would be so nice, except that IRIX make doesn't grok it:
> | UX:make: ERROR: Unmatched closing curly braces or parenthesis in line 
> containing:
> |         $(FOO_$*).
> 
> I wonder whether that is the only `make' which has problems with this...

I have used similar idioms with GNU make and Berkeley make (NetBSD and
FreeBSD 4.x and 6.1) as well as Solaris 7, 8, 9, 10 /usr/ccs/bin/make
and AIX 5.1 /usr/bin/make with no problems.

        -- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (FreeBSD)

iD8DBQFE7zNqCg7APGsDnFERApQRAJ9rjrsD7AXdMbLo+8qzotwiFDz7gwCgrMUn
7h2S5aWlemwt/lGmXoEiVv4=
=UjTT
-----END PGP SIGNATURE-----