Bug#230944: numerix_0.19-1(hppa/unstable): FTBFS: bad commands
On Tue, Feb 03, 2004 at 08:21:15AM -0700, lamont@debian.org wrote:
> Package: numerix
> Version: 0.19-1
> Severity: serious
>
> There was an error while trying to autobuild your package:
>
> > Automatic build of numerix_0.19-1 on sarti by sbuild/hppa 1.170.4
> > Build started at 20040202-1513
>
> [...]
>
> > ** Using build dependencies supplied by package:
> > Build-Depends: libnums-ocaml-dev | ocaml (>= 3.08), libgmp3-dev, debhelper (>> 4.0.0), dpatch, tetex-bin, tetex-extra, autotools-dev
>
> [...]
>
> > mv libmlnumx.a dllmlnumx.so lib/common
> > I lib/ocaml -c lib/ocaml/numerix.ml
> > make[1]: I: Command not found
> > make[1]: [lib/ocaml/numerix.cmx] Error 127 (ignored)
> > I lib/ocaml -c lib/ocaml/numcount.ml
> > make[1]: I: Command not found
> > make[1]: [lib/ocaml/numcount.cmx] Error 127 (ignored)
> > I lib/ocaml -c lib/ocaml/numcmp.ml
> > make[1]: I: Command not found
> > make[1]: [lib/ocaml/numcmp.cmx] Error 127 (ignored)
> > ocamlmklib -o numerix -oc mlnumx -I lib/ocaml numerix.cmx numcount.cmx numcmp.cmx -cclib -Llib/common -lgmp -cclib -lnums
> > sh: line 1: /usr/bin/ocamlopt: No such file or directory
> > make[1]: *** [lib/ocaml/numerix.cmxa] Error 2
> > make[1]: Leaving directory `/build/buildd/numerix-0.19'
> > make: *** [build-stamp] Error 2
>
> A full build log can be found at:
> http://buildd.debian.org/build.php?arch=hppa&pkg=numerix&ver=0.19-1
Medwards, this is a typical case of the upstream build system being
broken and not knowing or caring about architectures without native code
compiler, at least this is how it seemed to me from a cursory glance at
the generated Makefile. I may be wrong though.
The Makefile has indeed targets for native code .cmx and bytecode .cmo,
but seem to lack a global choosing mechanism for those, that is a call
to make lib would build the bytecode and a call to make lib_opt would
build the native code, or something such.
Could you have a look at this, and report back on what you found, so we
can go forward with fixing this RC bug ?
Friendly,
Sven Luther
Reply to: