pcp
[Top] [All Lists]

RE: [pcp] pcp 3.9.5 build failure on ia64 & suse

To: "'Nathan Scott'" <nathans@xxxxxxxxxx>
Subject: RE: [pcp] pcp 3.9.5 build failure on ia64 & suse
From: "Ken McDonell" <kenj@xxxxxxxxxxxxxxxx>
Date: Fri, 27 Jun 2014 13:48:46 +1000
Cc: <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <1907775487.34476034.1403832030935.JavaMail.zimbra@xxxxxxxxxx>
References: <04d301cf912d$fb482980$f1d87c80$@internode.on.net> <1601784038.34470385.1403828681147.JavaMail.zimbra@xxxxxxxxxx> <1907775487.34476034.1403832030935.JavaMail.zimbra@xxxxxxxxxx>
Thread-index: AQK3Mo2JT9Ip6Xcd2hwMC5uPd+Go/QJ7uoGzAZggXTuZlHCXEA==
Thanks Nathan and Frank (for the initial hint).

> -----Original Message-----
> From: Nathan Scott [mailto:nathans@xxxxxxxxxx]
> Sent: Friday, 27 June 2014 11:21 AM
> To: Ken McDonell
> Cc: pcp@xxxxxxxxxxx
> Subject: Re: [pcp] pcp 3.9.5 build failure on ia64 & suse
> ...
> It seems this "BuildArch: noarch" tag requires RPM 4.6.0 or higher - is the
> SuSE build machine you are using at a lower version?  Assuming it is, I guess
> we'll need to make pcp.spec.in have a guard around it based on rpm --
> version info.  Could add this to build/rpm/GNUmakefile and drive it into
> pcp.spec.in when its generated in there?

The rpm version is 4.4.2.3 on the ia64 build machine.

Commenting out the BuildArch line lets Makepkgs run to completion ... rpms 
built and installed.

Is there some magic predefined macro in rpm-land that already provides the rpm 
version number that is the missing piece of the spell needed to fix this 
permanently?

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