How to create Debian GNU/Hurd packages (part III)
-----BEGIN PGP SIGNED MESSAGE-----
I have still to talk about shared lib dependencies.
When cross-compiling, there is a little problem with this.
Normally a Debian package has, in the control file, a Depends: line like
this one: "Depends: libc6" which tells dpkg that if you install this
package you have to install libc6 too. [ The control file is a file
which is inside the .deb file, and it is read by dpkg ].
This Depends (or Pre-Depends) line is generated automatically by the
debian/rules file, which uses a tool called dpkg-shlibdeps.
dpkg-shlibdeps works by using ldd on the binaries and parsing the output.
Each library package has a *.shlibs file (a small text database).
dpkg-shlibdeps uses this database and the output of ldd to decide on which
packages the package which is being built has to Depend.
However, when cross-compiling, ldd outputs nothing reasonable on Hurd
binaries, there is nothing to parse, and there is nothing to do.
I don't consider this a big problem for executables that depend *only* on
glibc2, since glibc 2.1 will be backwards compatible with glibc2, but it
may be a problem for other libraries.
For this reason, I use the ldd wrapper which says "statically linked", and
I have avoided on purpose to upload any package which depends on any other
shared library different than libc (for example, ncurses).
So it would be great to have a Linux-ldd which understand Hurd binaries,
and also to have some dpkg-shlibdeps wrapper to work with it. This way
the "cross-compiler suite" would be "complete".
If somebody believes it is possible to do something like this and it is
not too much work, please go ahead :-)
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----
To UNSUBSCRIBE, email to firstname.lastname@example.org
with a subject of "unsubscribe". Trouble? Contact email@example.com