Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 17 Jul 2002 05:04:48 +0000
From:      Dima Dorfman <dima@trit.org>
To:        Andrew Martin <ugly@inhuman.org>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: buildworld fails on getpeereid.c 
Message-ID:  <20020717050449.B29D63F45@turbine.trit.org>
In-Reply-To: <20020716205600.5f5609db.ugly@inhuman.org>; from ugly@inhuman.org on "Tue, 16 Jul 2002 20:56:00 -0400"

next in thread | previous in thread | raw e-mail | index | archive | help
Andrew Martin <ugly@inhuman.org> wrote:
> cc -O -pipe  -DLIBC_RCS -DSYSLIBC_RCS
> -I/usr/src/lib/libc_r/../libc/include -DPTHREAD_KERNEL -D_THREAD_SAFE
> -I/usr/src/lib/libc_r/uthread -I/usr/src/lib/libc_r/../../include
> -D_LOCK_DEBUG -D_PTHREADS_INVARIANTS -D__DBINTERFACE_PRIVATE -DINET6
> -DPOSIX_MISTAKE -I/usr/src/lib/libc_r/../libc/locale -DBROKEN_DES -DYP 
> -c /usr/src/lib/libc_r/../libc/gen/getpeereid.c -o getpeereid.o
> /usr/src/lib/libc_r/../libc/gen/getpeereid.c: In function `getpeereid':
> /usr/src/lib/libc_r/../libc/gen/getpeereid.c:41: storage size of `xuc'
> isn't known
> /usr/src/lib/libc_r/../libc/gen/getpeereid.c:46: `LOCAL_PEERCRED'
> undeclared (first use in this function)
> /usr/src/lib/libc_r/../libc/gen/getpeereid.c:46: (Each undeclared
> identifier is reported only once
> /usr/src/lib/libc_r/../libc/gen/getpeereid.c:46: for each function it
> appears in.)
> /usr/src/lib/libc_r/../libc/gen/getpeereid.c:49: `XUCRED_VERSION'
> undeclared (first use in this function)
> *** Error code 1

The change that's probably responsible for this (MFC of getpeereid) is
about four months old now, but some people still seem to be stumbling
over this (see, for example, PR 37498, and there have also been other,
similar, reports).  I have no idea what causes it, or how to fix it,
but it seems to be pilot error, or some combination of options that
very few people seem to use, or it would have been fixed by now.

If you have time and want it fixed, look at the aforementioned PR and
in the -stable archives for similar reports and see if you can find
what you have in common with all the other people having trouble with
this.  (Any build gurus lurking out there are free to try to figure it
out, too (hint, hint) :-]).

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020717050449.B29D63F45>