pcp
[Top] [All Lists]

Re: pmmgr build failure on 32-bit Fedora release 17 (Beefy Miracle)

To: "Frank Ch. Eigler" <fche@xxxxxxxxxx>
Subject: Re: pmmgr build failure on 32-bit Fedora release 17 (Beefy Miracle)
From: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date: Thu, 06 Mar 2014 11:16:24 +1100
Cc: pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <20140305150207.GB27666@xxxxxxxxxx>
References: <53101471.4000200@xxxxxxxxxxxxxxxx> <y0mzjlbwj2e.fsf@xxxxxxxx> <y0m4n3jw52a.fsf@xxxxxxxx> <5311157B.9010004@xxxxxxxxxxxxxxxx> <20140228231759.GA18123@xxxxxxxxxx> <5316AD5C.3030408@xxxxxxxxxxxxxxxx> <20140305150207.GB27666@xxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
Thanks Frank for continuing to help out here ...

On 06/03/14 02:02, Frank Ch. Eigler wrote:
> ...
> So something went wrong around this point.  Do you perhaps have a
> personal $HOME/.rpm* file or a modified system one?

I don't have any $HOME/.rpm* files

Not sure where the "system one" is hiding, but I've not deliberately changed 
anything related to rpm, and sniffing all the rpms with rpm in their names ...

rpm --verify rpmconf rpm-libs rpm-build rpm-build-libs rpm rpm-python rpmreaper 
deltarpm python-deltarpm

produces no output.

> I think the key is to stop overriding what are probably the proper
> system defaults; we just need to find what's doing the dirty deed.
> You should be seeing this:
> 
> % rpm --eval %_target_cpu
> i686

The answer comes back ...

$ rpm --eval %_target_cpu
i386

but

kenj@vm12:~$ uname -a
Linux vm12 3.9.10-100.fc17.i686 #1 SMP Sun Jul 14 01:40:11 UTC 2013 i686 i686 
i386 GNU/Linux

which seems a bit odd but maybe is OK.

I thought the VM config may have been (accidentally) changed at some point, and 
the CPU config had been something different at the initial install or at some 
subsequent boot or upgrade.  So I blew the VM away, and started again with kvm 
style kvm32 Model CPUs ... reinstalled Fedora 17 32-bit and all the needed 
RPMs, recloned the PCP tree, but Makepkgs dies the same way and the /etc/rpmrc 
"hack" does provide a workaround ... back to the mail thread ...

> % grep _cpu /usr/lib/rpm/macros /etc/rpm/* $HOME/.rpm*
> /usr/lib/rpm/macros:%_build_cpu                 %{_host_cpu}
> /usr/lib/rpm/macros:%_host_cpu                  i686
> /usr/lib/rpm/macros:%_target_cpu                %{_host_cpu}

kenj@vm12:~/src/pcp$ grep _cpu /usr/lib/rpm/macros /etc/rpm/* $HOME/.rpm*
/usr/lib/rpm/macros:%_target_platform   
%{_target_cpu}-%{_vendor}-%{_target_os}%{?_gnu}
/usr/lib/rpm/macros:%_build_cpu         %{_host_cpu}
/usr/lib/rpm/macros:%_host_cpu          i686
/usr/lib/rpm/macros:%_target_cpu                %{_host_cpu}
grep: /home/kenj/.rpm*: No such file or directory

So I think I'll leave the "hack" in place for now, and assume Fedora 17 will be 
retired from active QA duty at some point in the not too distant future.

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