pcp
[Top] [All Lists]

RE: [pcp] configure.ac issue

To: "'PCP'" <pcp@xxxxxxxxxxx>
Subject: RE: [pcp] configure.ac issue
From: "Ken McDonell" <kenj@xxxxxxxxxxxxxxxx>
Date: Sun, 5 Jul 2015 07:03:08 +1000
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <559661D1.6060905@xxxxxxxxxxxxxxxx>
References: <559661D1.6060905@xxxxxxxxxxxxxxxx>
Thread-index: AQIoDSrKAFl/bvRwseShbYnlS0lFkJ0dHqjA
> -----Original Message-----
> From: pcp-bounces@xxxxxxxxxxx [mailto:pcp-bounces@xxxxxxxxxxx] On Behalf
> Of Ken McDonell
> Sent: Friday, 3 July 2015 8:20 PM
> To: PCP
> Subject: [pcp] configure.ac issue
> 
> ./configure: line 3943: test: too many arguments
> ./configure: line 3971: test: too many arguments
> ./configure: line 4011: test: too many arguments
> 
> lines like this ... in configure.ac are not syntactically correct,
expecially when
> $cc_is_gcc appears to be undefined.
> 
>       test $cc_is_gcc -a "x$enable_ssp" != xno
> 
> Not sure where this worked, but probably needs guidance from Nathan as to
> the intent.

I had to find a fix for this as it was causing build breakage ... I've
committed the attached patch in my tree, but would really appreciate some
review eyes being cast over it.

Attachment: patch.pcp
Description: Binary data

<Prev in Thread] Current Thread [Next in Thread>