On Fri, Dec 05, 2003 at 11:25:25PM +0100, Santiago Vila wrote: > > # tar jtvf gnu-knetbsd.tar.bz2 ./lib/ld.so.1 > lrwxrwxrwx root/root 0 2003-12-04 22:23:44 ./lib/ld.so.1 -> l > > Warning: this tarball suffers from the "mysterious symlink bug" and > it's probably unusable.
It should still work, since for some reason gnu ld.so.1 is merely decorative in our port :) No, really, I tested it (although not very extensively). You can test it in a chroot if you're unsure. > Robert, I find very strange that I have never suffered from this bug myself. > Can you reproduce the symlink bug on a not self-hosting system, i.e. > a chroot inside a NetBSD system, which is what I still have here? Yes, compile about any package that sets symlinks in a long directory hierrachy. I recall seeing this bug in, at least: xfree86, netbsd, pam, glibc. (obviously netbsd is the simplest package in this list). When autobuilding packages, please try to do it in /tmp to avoid such problem. I don't recommend, though, to replace a working development system like your chroot untill you're sure the self-hosting mode works well enough. In particular, try running sshd (or inetutils-telnetd) from inside your chroot. -- Robert Millan "[..] but the delight and pride of Aule is in the deed of making, and in the thing made, and neither in possession nor in his own mastery; wherefore he gives and hoards not, and is free from care, passing ever on to some new work." -- J.R.R.T, Ainulindale (Silmarillion)
