Re: Lilo broken in gcc4 branch?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Thomas Steffen wrote:
>>from this line in my sources.list (BTW: Should I be using
>>debian-pure64-3.4?):
>
>
> Yes, maybe you should. Certainly getting the lilo package from there
> is good idea, till you have sorted out your problems.
I could only find the package as source at that location, bit it didn't
matter much. That source compiled clean, and I now have lilo again.
By the way. Should I file a bug report about this somewhere? I really
don't think that a dynamically linked 32-bit lilo was put in the amd64
gcc-3.4 repository on purpose.
/Jacob
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCbpioiAWIAI3xXVYRAoR0AKCfgofu/dMHhVj56fFW6gsmDUbj1wCfdnyn
sa1zBcYRtMefJh+utirt/M0=
=sD3S
-----END PGP SIGNATURE-----
Reply to: