Bug#630320: obus: FTBFS on several architectures: can't find Dynlink

["Aaron M. Ucko" <ucko@debian.org>]

Package: obus
Version: 1.1.2-1
Severity: serious
Justification: fails to build from source

Builds of obus are failing on armel, ia64, mips, and s390 with errors
about being unable to find Dynlink; the armel build fails with

> File "_none_", line 1, characters 0-1:
> Error: No implementations provided for the following modules:
>          Dynlink referenced from /usr/lib/ocaml/camlp4/camlp4lib.cmxa(Camlp4)
> Command exited with code 2.

and the other three fail with

> File "_none_", line 1, characters 0-1:
> Error: Error while linking /usr/lib/ocaml/camlp4/camlp4lib.cma(Camlp4):
> Reference to undefined global `Dynlink'
> Command exited with code 2.

(The remaining architectures fail because they assume a writable home
directory, which I'll report separately.)

Could you please take a look?

Thanks!

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (300, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.39-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash