Daily builds not updating Pyrex generated C source
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
High
|
Jelmer Vernooij |
Bug Description
In r5731 changes were made to the signatures of some functions in diff-delta.c and the Pyrex code in _groupcompress_
<https:/
building 'bzrlib.
gcc -pthread -fno-strict-
bzrlib/
bzrlib/
bzrlib/
bzrlib/
bzrlib/
bzrlib/
bzrlib/
bzrlib/
Cannot build extension "bzrlib.
Use "build_ext --allow-
error: command 'gcc' failed with exit status 1
dh_auto_build: python setup.py build returned exit code 1
What's confusing here is that python-pyrex is pulled in by apt, but apparently the C files are not being updated. There are messages output using `print` if there are import issues, are these perhaps being lost, unlike the `distutils.log` messages during the build?
Changed in bzr: | |
assignee: | nobody → Jelmer Vernooij (jelmer) |
Changed in bzr: | |
status: | Confirmed → In Progress |
Changed in bzr: | |
status: | In Progress → Fix Released |
<mgz> I think the daily builds start from a tarball.
or... what spiv said.
so, there's another bug about the start point being wrong perhaps, but I don't see why the build doesn't update the pyrex generated files
<spiv> I'm pretty sure this is some sort of hangover from 'debs start with a source tarball and then add packaging goo', although I'm unclear on the precise route between that fact and this problem :)
<spiv> It may be something like the timestamps of the .c files on disk in the checkout/build area aren't older than the .pyx files, so the build stuff thinks they are up to date.