On Thu, 4 Feb 2016, Mark Post wrote: > Do you have /usr/bin/python3 on your system? If so, you'll > likely have to remove it until after the build is finished. > I've found that even building packages without RPM sometimes > necessitates this because things like ./configure find > packages that I don't want used.
perhaps, but in a clefos 7.x environment, those versions should only sneak in if the 'epel' derived packages are present python3-pkgversion-macros.noarch python34.%{arch} The 'auto-tools' ./configure in a 'mock' build environment should be tightly constrained against such errors I note also the presence of: python34-mock.noarch python34-setuptools.noarch python34-tools.%{arch} and any of those might also 'pollute' the rpmbuild environment. But I suspect that these are not in play so much as an unintended 'back-leak' in the rpm build macros has a 'python3' expansion. In recent weeks, on the rpm-list for development of rpm, there has been some agitation out the folks out on the 'Fedora' bleeding edge to re-work 'old' macros, and there has been essentially zero concern for such trivia as backward compatibility or testing against 'enterprise' products. This may bave polluted the mock carry-forward of the relevant macros -- Russ herrold ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/