Re: Bug#336283: ara: [m68k] FTBFS
On Saturday 29 October 2005 10:06, Christian T. Steigies wrote:
> Package: ara
> Version: 1.0.10
> Severity: important
>
> Automatic build of ara_1.0.10 on aahz by sbuild/m68k 69
> [...]
> ** Using build dependencies supplied by package:
> Build-Depends: debhelper (>= 4.0.0), liblablgtk2-ocaml-dev,
> ocaml-best-compilers, m4 [...]
> touch build-indep-stamp
> touch build-stamp
> /usr/bin/fakeroot debian/rules binary-arch
> touch build-stamp
> dh_testdir
> dh_testroot
> dh_clean -k
> dh_installdirs
> mkdir -p /build/buildd/ara-1.0.10/debian/tmp
> if [ -x /usr/bin/ocamlopt -o -x /usr/bin/ocamlopt.opt ]; then \
> /usr/bin/make install DESTDIR=/build/buildd/ara-1.0.10/debian/tmp ; \
> fi
> # The arch-dependent packages are only available on archs supported by
> ocamlopt There are no native code compilers on arch m68k so this package
> arch-dependant part should not build on it. dpkg-genchanges -B
> -mDebian/m68k Build Daemon <cts-aahz@debian.org> dpkg-genchanges:
> arch-specific upload - not including arch-independent packages
> dpkg-genchanges: failure: cannot read files list file: No such file or
> directory
Well, we end up needing dpkg-genchanges and dpkg-buildpackage with support for
building only architecture-independant parts of the package and not
architecture-dependent ones (see #109794 #200454).
> If this package is not supposed to be built on m68k, please say so in your
> control file and/or stop the build right at the beginning.
I see two approaches:
for {wanna}-build{d} I should mail to Packages-arch-specific maintainers to
include ara there so that being skipped built on s390, mips, mipsel, m68k
since there are no native code compilers there. On these arches we can build
only arch-indep parts of the package.
At the user side build attempts on s390, mips, mipsel, m68k will fail again
and I leave a message to the user explaining why the built on arch-dependant
parts will fail. I'm not sure where exactly you want me to stop the built on
such cases ? Please elaborate. Better ideas welcome. Thanks.
--
pub 4096R/0E4BD0AB 2003-03-18 <people.fccf.net/danchev/key pgp.mit.edu>
fingerprint 1AE7 7C66 0A26 5BFF DF22 5D55 1C57 0C89 0E4B D0AB
Reply to: