-----BEGIN PGP SIGNED MESSAGE-----
I was trying to make a cross-compiling tool-chain
(powerpc-apple-darwin7.2.0 => powerpc-unknown-linux-gnu) and I
discovered that binutils, gcc, and ddd (Max Horn's package) all attempt
to install /sw/lib/libiberty.a. What is the best way to handle this?
Could/should we use update-alternatives? (I don't know much about it,
so I'm not sure) OTOH, if several packages use it, we might see if we
could make a seperate libiberty package that just installs a
/sw/lib/libiberty.a, then have anything that needs libiberty.a either
use their own but not install it or use the installed copy.
What do you all think?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (Darwin)
-----END PGP SIGNATURE-----