FTBFS in currytools/peval
When building pakcs for Debian, I get this build failure:
[...]
make[4]: Leaving directory '/<<PKGBUILDDIR>>/currytools/importcalls'
make[4]: Entering directory '/<<PKGBUILDDIR>>/currytools/optimize'
make[5]: Entering directory '/<<PKGBUILDDIR>>/currytools/optimize/binding_optimization'
rm -f /<<PKGBUILDDIR>>/currytools/optimize/bindingopt
ln -s /<<PKGBUILDDIR>>/currytools/optimize/binding_optimization/BindingOpt /<<PKGBUILDDIR>>/currytools/optimize/bindingopt
make[5]: Leaving directory '/<<PKGBUILDDIR>>/currytools/optimize/binding_optimization'
make[4]: Leaving directory '/<<PKGBUILDDIR>>/currytools/optimize'
make[4]: Entering directory '/<<PKGBUILDDIR>>/currytools/peval'
/<<PKGBUILDDIR>>/bin/curry --noreadline :set -time :load peval :save :quit
cp: cannot create regular file '/sbuild-nonexistent/.pakcsrc': No such file or directory
pakcs-frontend: peval.curry: hGetContents: invalid argument (invalid byte sequence)
ERROR occurred during parsing!
ERROR: no program loaded
Makefile:31: recipe for target 'peval' failed
make[4]: *** [peval] Error 1
make[4]: Leaving directory '/<<PKGBUILDDIR>>/currytools/peval'
Makefile:30: recipe for target 'peval' failed
make[3]: *** [peval] Error 2
make[3]: Leaving directory '/<<PKGBUILDDIR>>/currytools'
Makefile:189: recipe for target 'tools' failed
make[2]: *** [tools] Error 2
make[2]: Leaving directory '/<<PKGBUILDDIR>>'
Makefile:106: recipe for target 'install' failed
make[1]: *** [install] Error 2
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
/usr/share/cdbs/1/class/makefile.mk:103: recipe for target 'debian/stamp-makefile-install' failed
make: *** [debian/stamp-makefile-install] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
--------------------------------------------------------------------------------The location where it is failing, is this:
/<<PKGBUILDDIR>>/bin/curry --noreadline :set -time :load peval :save :quit
cp: cannot create regular file '/sbuild-nonexistent/.pakcsrc': No such file or directory
pakcs-frontend: peval.curry: hGetContents: invalid argument (invalid byte sequence)The above build logs stems from a chrooted build, in a local build (with $HOME), I do not get the cp warning about .pakcsrc not being copied.
But the local build also fails with this error: pakcs-frontend: peval.curry: hGetContents: invalid argument (invalid byte sequence).
Any clue what might be causing this? The full build log is attached to this bug.