On Fri, Mar 11, 2005 at 05:51:35PM +0100, Peter Van Eynde wrote:
rm@seid-online.de wrote:
Hi, thank's for putting up a new version, but it misserably FTBFS on my box, a Linux/PPC :-/ Here's the relevant excerpt from the build log: .. hrmm - looks like the build wants to build a multi-threaded sbcl, something that isn't currently availble on Linux/PPC. Looking at the debian/rules file everything _should_ build ak (the conditional adding of sb-threads to features did work during all previous builds). Maybe it's because the new maintainer included the file 'customize-target-features.lisp' into the source distribution ... :-)
Well if all bugreports are so good this could be easier then I thought :-).
I've uploaded a -2 to the NEW queue and to people.debian.org
Sorry, i _hate_ to do this, but there comes another error report: hobbes:/LISP/DEBS# dpkg -i sbcl-common_0.8.20.5-2_all.deb sbcl_0.8.20.5-2_powerpc.deb (Reading database ... 236445 files and directories currently installed.) Unpacking sbcl-common (from sbcl-common_0.8.20.5-2_all.deb) ... dpkg: error processing sbcl-common_0.8.20.5-2_all.deb (--install): trying to overwrite `/usr/share/doc-base/sbcl', which is also in package sbcl dpkg-deb: subprocess paste killed by signal (Broken pipe) Preparing to replace sbcl 1:0.8.20.5-2 (using sbcl_0.8.20.5-2_powerpc.deb) ... Unpacking replacement sbcl ... dpkg: dependency problems prevent configuration of sbcl: sbcl depends on sbcl-common; however: Package sbcl-common is not installed. dpkg: error processing sbcl (--install): dependency problems - leaving unconfigured Errors were encountered while processing: sbcl-common_0.8.20.5-2_all.deb sbcl hobbes:/LISP/DEBS# I think you maybe shouldn't invoke dh_installdocs for both binary-indep and binary-arch (but don'T quote me on this: i'm not a debhelper expert). The problem manifests in the (autogenerated) scripts ....postinst.debhelper. Hmm, how did this escape the allmighty build daemons? HTH RalfD Oh, one more tip (frustrating experience for me): building with SBCL 0.8.19.22 i needed to 'export LANG=en_US.UTF-8', otherwise the build would fail .... Maybe this could be checked for in the build script.
Thanks, Peter