Date: Thu, 2 May 2002 23:10:10 -0700 (PDT) From: Dima Dorfman <dima@trit.org> To: freebsd-bugs@FreeBSD.org Subject: Re: bin/37498: buildworld fails due to /usr/src/lib/libc/gen/getpeereid.c Message-ID: <200205030610.g436A9f00674@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/37498; it has been noted by GNATS. From: Dima Dorfman <dima@trit.org> To: John Saunders <john@nlc.net.au> Cc: FreeBSD-gnats-submit@FreeBSD.org, imp@village.org Subject: Re: bin/37498: buildworld fails due to /usr/src/lib/libc/gen/getpeereid.c Date: Fri, 03 May 2002 06:09:37 +0000 John Saunders <john@nlc.net.au> wrote: > >Description: > > When updating your system, buildworld fails due to new function in > libc called getpeerid. The build environment doesn't include the > correct -I options to get the new ucred.h file included. > > cc -O -pipe -march=pentiumpro -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc/include -D__DBINTERFACE_PRIVATE -DINET6 -DPOSIX_MISTAKE -I/usr/src/lib/libc/../libc/locale -DBROKEN_DES -DYP -c /usr/src/lib/libc/../libc/gen/getpeereid.c -o getpeereid.o > /usr/src/lib/libc/../libc/gen/getpeereid.c: In function `getpeereid': > /usr/src/lib/libc/../libc/gen/getpeereid.c:41: storage size of `xuc' isn't known > /usr/src/lib/libc/../libc/gen/getpeereid.c:46: `LOCAL_PEERCRED' undeclared (first use in this function) > /usr/src/lib/libc/../libc/gen/getpeereid.c:46: (Each undeclared identifier is reported only once > /usr/src/lib/libc/../libc/gen/getpeereid.c:46: for each function it appears in.) > /usr/src/lib/libc/../libc/gen/getpeereid.c:49: `XUCRED_VERSION' undeclared (first use in this function) If you're using buildworld, I think the right include path should be set up for you. Since you say you are indeed using buildworld, I'm not sure what's going on, but since you're the only one to report this build failure, you must be doing something different from everyone else building -stable on -stable. Unforunately, I don't know enough about the buld process to know what that is. Is there anything particular about your environment that might be causing this? It looks like you're just building a new -stable on a pretty recent -stable; many people have done this successfully (or they've all been unusually silent since March 9th). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200205030610.g436A9f00674>