Date: Wed, 12 Jul 1995 12:51:48 -0700 (PDT) From: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com> To: bde@zeta.org.au (Bruce Evans) Cc: bde@zeta.org.au, current@FreeBSD.org, freebsd-hackers@FreeBSD.org, root@debian.cps.cmich.edu Subject: Re: Help me please.. :) Message-ID: <199507121951.MAA18542@gndrsh.aac.dev.com> In-Reply-To: <199507121605.CAA31521@godzilla.zeta.org.au> from "Bruce Evans" at Jul 13, 95 02:05:28 am
next in thread | previous in thread | raw e-mail | index | archive | help
> > >> There are two bugs here: > > >There is one bug here. > > >> 1) ... > > >> 2) FreeBSD releases have /usr/include/machine populated with files. It > >> should be a symlink to /sys/i386/include to avoid update problems. > > >This is not a bug, realize that without the src release installed if we > >did this you could not use the system for compiling. Bill did that > >... > > >We need to ``enhance'' the installation of the src tree, that is where > >the bug lies. When a src tree is installed then and only then should > > There are hundreds of bugs here :-). We need to support multiple > machines someday. Then files in /usr/include/machine can't work even if > it is a symlink. A symlink is still better because it can be changed > much faster. Actually the current ``SHARED=copies'' works perfect for a shared src tree and multiple machines/archs. Just ask the folks over at CSRG. /usr is a per arch file system, symlinking from a per arch file system to a arch independent (/usr/src) file system is bad news. You just made another case for leaving it the way it is! Other solution is variant symbolic link :-). -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199507121951.MAA18542>