Eivind Eklund said:
> On Mon, Mar 08, 1999 at 05:59:05PM -0500, John S. Dyson wrote:
> > Eivind Eklund said:
> > > If you do not know how FreeBSD works to a detailed enough level to NOT
> > > HAVE TO ASK THIS, then you should MAKE WORLD. You should NOT try to
> > > do incremental recompiles. That
On Mon, Mar 08, 1999 at 05:59:05PM -0500, John S. Dyson wrote:
> Eivind Eklund said:
> > If you do not know how FreeBSD works to a detailed enough level to NOT
> > HAVE TO ASK THIS, then you should MAKE WORLD. You should NOT try to
> > do incremental recompiles. That is reserved for those people
Eivind Eklund said:
> On Tue, Nov 17, 1998 at 09:49:31PM -0500, HighWind Software Information wrote:
> >
> > After installing the recent libc_r and libc, I'm getting:
> >
> > ld.so failed: Undefined symbol "SYS_kldsym" in
> > make:/usr/lib/aout/libc.so.3.1
> >
> > I also get it sometimes when
> When is this glue generated?
1. syscalls.h and syscall.mk is built from syscalls.master
makesyscalls.sh by when you compile a kernel
2. these files are used when you build libc, so make knows all the
syscalls so it can build the stubs.
Ex. getpgrp.S:
#include "SYS.h"
RSYSCALL(getp
So actually, I have a question about this. How is the syscall glue
generated, and when. Pretty much all the userland libraries call syscalls
using symbols of the same name rather than the syscall() wrapper,
presumably for performance and feasiability reasons (especially with
pipe()). When is th
On Tue, Nov 17, 1998 at 09:49:31PM -0500, HighWind Software Information wrote:
>
> After installing the recent libc_r and libc, I'm getting:
>
> ld.so failed: Undefined symbol "SYS_kldsym" in make:/usr/lib/aout/libc.so.3.1
>
> I also get it sometimes when I link against libc_r.
>
> "SYS_kldsym
