pcp
[Top] [All Lists]

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

To: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Subject: Re: [pcp] pcp 3.9.5 build failure on ia64 & suse
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Fri, 27 Jun 2014 00:21:06 -0400 (EDT)
Cc: pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <074a01cf91ba$b3a9ada0$1afd08e0$@internode.on.net>
References: <04d301cf912d$fb482980$f1d87c80$@internode.on.net> <1601784038.34470385.1403828681147.JavaMail.zimbra@xxxxxxxxxx> <1907775487.34476034.1403832030935.JavaMail.zimbra@xxxxxxxxxx> <074a01cf91ba$b3a9ada0$1afd08e0$@internode.on.net>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>
Thread-index: AQK3Mo2JT9Ip6Xcd2hwMC5uPd+Go/QJ7uoGzAZggXTuZlHCXEKZYK6SG
Thread-topic: pcp 3.9.5 build failure on ia64 & suse
Hi Ken,

----- Original Message -----
> [...]
> 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?
> 

I had a look but couldn't find RPM version info as spec %variables.  pcp.spec
is built in build/rpm/GNUmakefile, so I guess $(RPMBUILD) --version could be
split apart and used?

cheers.

--
Nathan

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