Re: Bug#750668: python3.4 ftbfs on kfreebsd, clock() returning -1
On 05/06/14 15:33, Matthias Klose wrote:
> Is this supposed to work on kfreebsd?
Sorry, I'm not sure about that at the moment...
> It is easy to disable the pybench run itself.
Apparently not ;)
There seems to be inverted logic in debian/rules for WITHOUT_STONE,
please see attached diff. buildd logs show it didn't run on the arches
where it should have.
p.s. the "browse" link on PTS to the Bazaar VCS is 404
p.p.s. building with -j2, it seems possible for stamps/stamp-check
target to get built before stamps/stamp-build-static has done mkdir
$(buildd_shared), that can cause this:
> echo "check run disabled for this build" > /home/steven/python3.4-3.4.1/build-static/test_results
> /bin/bash: /home/steven/python3.4-3.4.1/build-static/test_results: No such file or directory
> make: *** [stamps/stamp-check] Error 1
> make: *** Waiting for unfinished jobs....
p.p.p.s. there seems to be an inadequate dependency on binutils:
> x86_64-kfreebsd-gnu-ar rc libpython3.4m.a Modules/getbuildinfo.o
> make[1]: x86_64-kfreebsd-gnu-ar: Command not found
> make[1]: *** [libpython3.4m.a] Error 127
binutils/2.24-2 does not have that file, but I think 2.24.51.20140604-1
introduced it. Probably python3.4 or one of its build-deps should have
a versioned dependency on binutils (>= 2.24.51.2014041) ?
Regards,
--
Steven Chamberlain
steven@pyro.eu.org
+++ python3.4-3.4.1/debian/rules.orig 2014-06-08 17:17:49.000000000 +0100
--- python3.4-3.4.1/debian/rules 2014-06-08 17:24:22.871401137 +0100
@@ -542,6 +542,8 @@
stamps/stamp-pystone:
ifeq ($(WITHOUT_STONE),yes)
+ @echo "pystone run disabled for this build"
+else
@echo "BEGIN pystone static"
cd $(buildd_static) && ./python ../Lib/test/pystone.py
cd $(buildd_static) && ./python ../Lib/test/pystone.py
Reply to: