Source: ocamlcreal
Version: 0.7-5
Severity: serious
User: [email protected]
Usertags: qa-ftbfs-20091005 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[1]: Entering directory 
> `/build/user-ocamlcreal_0.7-5-amd64-rvL7nj/ocamlcreal-0.7'
> mkdir -p 
> /build/user-ocamlcreal_0.7-5-amd64-rvL7nj/ocamlcreal-0.7/debian/libcreal-ocaml-dev/usr/lib/ocaml/creal
> cp -f creal.cma cr.cmi creal.cmi cr.mli creal.mli 
> /build/user-ocamlcreal_0.7-5-amd64-rvL7nj/ocamlcreal-0.7/debian/libcreal-ocaml-dev/usr/lib/ocaml/creal
> cp -f creal.cmxa creal.a 
> /build/user-ocamlcreal_0.7-5-amd64-rvL7nj/ocamlcreal-0.7/debian/libcreal-ocaml-dev/usr/lib/ocaml/creal
> make[1]: Leaving directory 
> `/build/user-ocamlcreal_0.7-5-amd64-rvL7nj/ocamlcreal-0.7'
> cp debian/META debian/libcreal-ocaml-dev/usr/lib/ocaml/creal
> mkdir -p debian/libcreal-ocaml-dev/usr/share/doc/libcreal-ocaml-dev/html/api
> find debian/libcreal-ocaml-dev/usr/lib/ocaml -type f -name '*.mli' -or -name 
> '*.ml' | \
>       xargs ocamldoc -I +gmp -html -d 
> debian/libcreal-ocaml-dev/usr/share/doc/libcreal-ocaml-dev/html/api
> /usr/share/ocaml/ocamldoc-api-ref-config --doc-base-generate 
> libcreal-ocaml-dev
> make: /usr/share/ocaml/ocamldoc-api-ref-config: Command not found
> make: *** [install] Error 127

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2009/10/05/ocamlcreal_0.7-5_lsid64.buildlog

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot.  Internet was not
accessible from the build systems.

-- 
| Lucas Nussbaum
| [email protected]   http://www.lucas-nussbaum.net/ |
| jabber: [email protected]             GPG: 1024D/023B3F4F |



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to