Problem updating with RELENG_4_6 branch [stdio fix]

From: Wincent Colaiuta (wincentcolaiuta@mac.com)
Date: 07/31/02 

Date: Thu, 1 Aug 2002 01:07:20 +0930
From: Wincent Colaiuta <wincentcolaiuta@mac.com>
To: freebsd-security@FreeBSD.ORG

Just wondering if anyone has had any troubles updating their systems in
light of the recent security notification (FreeBSD-SA-02:23.stdio
[REVISED]).

I decided to update by rebuilding the world, and after a fresh cvsup of
the RELENG_4_6 branch, I get the following error during the "make
buildworld" in /usr/src/lib/libc:

> cc -O -pipe -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/xdr/xdr_array.c -o xdr_array.o
> /usr/src/lib/libc/../libc/xdr/xdr_array.c: In function `xdr_array':
> /usr/src/lib/libc/../libc/xdr/xdr_array.c:80: `UINT_MAX' undeclared
> (first use in this function)
> /usr/src/lib/libc/../libc/xdr/xdr_array.c:80: (Each undeclared
> identifier is reported only once
> /usr/src/lib/libc/../libc/xdr/xdr_array.c:80: for each function it
> appears in.)
> *** Error code 1
>
> Stop in /usr/src/lib/libc.
> *** Error code 1
>
> Stop in /usr/src/lib.
> *** Error code 1
>
> Stop in /usr/src.
> *** Error code 1
>
> Stop in /usr/src.
> *** Error code 1
>
> Stop in /usr/src.

I re-did the cvsup just to be sure, and did a "make clean" in /usr/src
just to be sure, but it failed again on the second attempt in the same
way... Anyone else seen this or got any pointers? Or is this a question
better posted to freebsd-questions? (apologies if this is the case).

The last make world I did was the update to 4.6.1-RELEASE #0 and that
went fine...

Cheers
Wincent

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

Relevant Pages

  • Re: Problem updating with RELENG_4_6 branch [stdio fix]
    ... Wincent Colaiuta wrote: ... >Just wondering if anyone has had any troubles updating their systems in ... >I decided to update by rebuilding the world, and after a fresh cvsup of ... with "unsubscribe freebsd-security" in the body of the message ...
    (FreeBSD-Security)
  • Re: FreeBSD Security Advisory FreeBSD-SA-02:21.tcpip
    ... | I hope that you can understand that doing a CVSup and then rebuilding the ... Some of those security advisories might not apply to you. ... with "unsubscribe freebsd-security" in the body of the message ...
    (FreeBSD-Security)