From oberman@es.net  Tue Jan 14 10:22:18 2003
Return-Path: <oberman@es.net>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id AFF7037B401
	for <FreeBSD-gnats-submit@freebsd.org>; Tue, 14 Jan 2003 10:22:18 -0800 (PST)
Received: from postal1.es.net (postal1.es.net [198.128.3.205])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1E73C43F13
	for <FreeBSD-gnats-submit@freebsd.org>; Tue, 14 Jan 2003 10:22:18 -0800 (PST)
	(envelope-from oberman@es.net)
Received: from pak.es.net ([198.128.1.13])
        by postal1.es.net (Postal Node 1) with ESMTP id MUA74016
        for <FreeBSD-gnats-submit@freebsd.org>; Tue, 14 Jan 2003 10:22:17 -0800
Received: by pak.es.net (Postfix, from userid 9381)
	id 7122022EDB; Tue, 14 Jan 2003 10:22:17 -0800 (PST)
Message-Id: <20030114182217.7122022EDB@pak.es.net>
Date: Tue, 14 Jan 2003 10:22:17 -0800 (PST)
From: Kevin Oberman <oberman@es.net>
Reply-To: Kevin Oberman <oberman@es.net>
To: FreeBSD-gnats-submit@freebsd.org
Cc:
Subject: Can't upgrade from V4 to V5 due to header conflicts
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         47063
>Category:       gnu
>Synopsis:       Can't upgrade from V4 to V5 due to header conflicts
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Jan 14 10:30:00 PST 2003
>Closed-Date:    Tue Jan 14 11:58:01 PST 2003
>Last-Modified:  Mon Apr  7 13:00:30 PDT 2003
>Originator:     Kevin Oberman
>Release:        FreeBSD 4.7-STABLE i386
>Organization:
ESnet--The Energy Sciences Network
>Environment:
System: FreeBSD kzin.es.net 4.7-STABLE FreeBSD 4.7-STABLE #22: Sat Jan  4 16:42:54 PST 2003     oberman@kzin.es.net:/usr/obj/usr/src/sys/KZIN  i386

>Description:
	When attempting to cvsup and upgrade the system from V4 to V5 I
get a fatal error building gperf/doc in the buildworld phase.
===> gnu/usr.bin/gperf/doc
c++  -O -pipe    -I/usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/lib -I/usr/src/gnu/usr.bin/gperf -c /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/bool-array.cc
In file included from /usr/include/stdio.h:44,
                 from /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/bool-array.h:57,
                 from /usr/src/gnu/usr.bin/gperf/../../../contrib/gperf/src/bool-array.cc:21:
/usr/include/sys/_types.h:77: declaration does not declare anything
*** Error code 1
It appears to be a conflict between the 4.7 header files and the 5.0
header files.

The problem first appeared between Jan. 5 when I did a successful
buildworld and Jan. 10 when the problem first bit me. I have repeated
the problem with a clean /usr/obj and /usr/src.

cvsup was run with a tag=RELENG_5_0.

>How-To-Repeat:
	cvsup a STABLE system with tag=RELENG_5_0 and buildworld.

>Fix:

None at this time. I'm looking into it as time permits.




>Release-Note:
>Audit-Trail:

From: "Kevin Oberman" <oberman@es.net>
To: FreeBSD-gnats-submit@FreeBSD.org, freebsd-bugs@FreeBSD.org
Cc:  
Subject: Re: gnu/47063: Can't upgrade from V4 to V5 due to header conflicts 
Date: Tue, 14 Jan 2003 11:14:46 -0800

 Please close this ticket. The problem was corrupt headers on the
 system due to a partial installworld that failed.
 
State-Changed-From-To: open->closed 
State-Changed-By: bmah 
State-Changed-When: Tue Jan 14 11:57:40 PST 2003 
State-Changed-Why:  
Closed by request of submitter...thanks for following up! 


http://www.freebsd.org/cgi/query-pr.cgi?pr=47063 

From: "Kevin Oberman" <oberman@es.net>
To: freebsd-gnats-submit@freebsd.org
Cc:  
Subject: Re: gnu/47063: Can't upgrade from V4 to V5 due to header conflicts
Date: Mon, 07 Apr 2003 12:53:05 -0700

 Please close. The problem was due to errors in the upgrade process. (I
 missed the "rm -rf /usr/include/g++".)
 
 R. Kevin Oberman, Network Engineer
 Energy Sciences Network (ESnet)
 Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
 E-mail: oberman@es.net			Phone: +1 510 486-8634
>Unformatted:
