Re: Problem updating with RELENG_4_6 branch [stdio fix]

From: Erik Paulsen Skålerud (erik@pentadon.com)
Date: 07/31/02 

From: Erik Paulsen Skålerud <erik@pentadon.com>
To: "Wincent Colaiuta" <wincentcolaiuta@mac.com>, <freebsd-security@FreeBSD.ORG>
Date: Wed, 31 Jul 2002 17:51:32 +0200

paste from freebsd-stable@freebsd.org:

On Wed, Jul 31, 2002 at 03:45:51PM +0100, Nick Hilliard wrote:
> Today's xdr mfc to the security branches boobed up a little. It looks
> like xdr_array.c needs to #include <limits.h>.

Yes, sorry. I just fixed it in RELENG_4. I will fix it shortly in the
other RELENG_4_* branches, and in -CURRENT. 

-- 
Jacques A. Vidrine <n@nectar.cc>                 http://www.nectar.cc/
NTT/Verio SME          .     FreeBSD UNIX     .       Heimdal Kerberos
jvidrine@verio.net     .  nectar@FreeBSD.org  .          nectar@kth.se
----- Original Message ----- 
From: "Wincent Colaiuta" <wincentcolaiuta@mac.com>
To: <freebsd-security@FreeBSD.ORG>
Sent: Wednesday, July 31, 2002 5:37 PM
Subject: Problem updating with RELENG_4_6 branch [stdio fix]
> 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
> 
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message

Relevant Pages

  • Re: IPSEC: racoon and Win2K
    ... > OK, now I see it's majordomo, can someone fix it? ... Have a look at the headers. ... >>> Jorge Peixoto Vasquez, Elet. ... with "unsubscribe freebsd-security" in the body of the message ...
    (FreeBSD-Security)
  • Re: IPSEC: racoon and Win2K
    ... > OK, now I see it's majordomo, can someone fix it? ... Have a look at the headers. ... >>> Jorge Peixoto Vasquez, Elet. ... with "unsubscribe freebsd-security" in the body of the message ...
    (FreeBSD-Security)
  • ENOUGH!!! Re: [openssh-unix-announce] Re: Upcoming OpenSSH vulnerability (fwd)
    ... >>>Release now and let the community help you fix the bug (since ... >>>apparently it's so complicated that you can't fix it right away on your ... People don't get that what Theo is doing is very fair. ... with "unsubscribe freebsd-security" in the body of the message ...
    (FreeBSD-Security)
  • RE: IPSEC: racoon and Win2K
    ... OK, now I see it's majordomo, can someone fix it? ... >> Jorge Peixoto Vasquez, Elet. ... with "unsubscribe freebsd-security" in the body of the message ...
    (FreeBSD-Security)