[Top][All Lists]

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


From: Too, Justin A.
Subject: Re: AM_PROG_UPC
Date: Sat, 30 Apr 2011 11:34:41 -0700
User-agent: Microsoft-MacOutlook/

On 4/29/11 8:57 PM, "Ralf Corsepius" <address@hidden> wrote:

>On 04/30/2011 01:16 AM, Too, Justin A. wrote:
>> Hi all,
>> In my I simply invoke: AC_PROG_UPC
>> Š
>> $ aclocal Š
>> warning: macro `AM_PROG_UPC' not found in
>> Š
>> $ autoconf
>> error: possibly undefined macro: AM_PROG_UPC
>> If this token and others are legitimate, please use m4patternallow.
>> See the Autoconf documentation.
>> Is this a non-standard macro?
>[Apart of this, AM_PROG_UPC violates auto*tools naming conventions;
>AM_*/AM_* prefixed macros are reserved for autoconf rsp. automake.]
>> Then, how can I add UPC support to my Autotools project?
>Non-standard macros need to be supplied by either the package itself or
>by other packages.
>There are several ways to do so, so answering your question would
>require knowing more details about the package you are trying to build.

Currently, I'm setting my upc file extensions to .c so that they will
compile without complaint from Automake, however it's obviously more clear
if they had a .upc extension:

foo_la_SOURCES = \

I want:

foo_la_SOURCES = \

I found this documentation:

    18.2 Handling new file extensions

So I'm assuming I can do this:

        upcc -c -o $@ $<

But this would have to be in every where I'd want to compile
UPC.  Also, I would have to do a lot of configure checking and setting up
myself so that I can use $(UPC) as the compiler in my rule, check that
upc/upcc is available, etc.  The AM_PROG_UPC macro seemed like the most
convenient method.



reply via email to

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