From owner-freebsd-amd64@FreeBSD.ORG  Sat Aug 21 15:47:30 2004
Return-Path: <owner-freebsd-amd64@FreeBSD.ORG>
Delivered-To: freebsd-amd64@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 6C6EC16A4CE
	for <freebsd-amd64@freebsd.org>; Sat, 21 Aug 2004 15:47:30 +0000 (GMT)
Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.198.35])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 51BB643D1F
	for <freebsd-amd64@freebsd.org>; Sat, 21 Aug 2004 15:47:30 +0000 (GMT)
	(envelope-from pscherf@acm.org)
Received: from sirius (c-24-16-153-77.client.comcast.net[24.16.153.77])
          by comcast.net (rwcrmhc11) with ESMTP
          id <2004082115472901300rb8fme>; Sat, 21 Aug 2004 15:47:29 +0000
From: Paul Scherf <pscherf@acm.org>
Organization: The Scherf Family
To: freebsd-amd64@freebsd.org
Date: Sat, 21 Aug 2004 08:45:26 -0700
User-Agent: KMail/1.6.2
References: <86r7q1e46f.fsf@duchess.twilley.org>
In-Reply-To: <86r7q1e46f.fsf@duchess.twilley.org>
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <200408210845.26164.pscherf@acm.org>
Subject: Re: -CURRENT doesn't make world lately
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Aug 2004 15:47:30 -0000

On Friday 20 August 2004 17:16, Jack Twilley wrote:
> Am I the only one who's tried to build -CURRENT recently and failed?
>
> One of the GCC info files isn't being makeinfo'ed properly, and that
> breaks the build.  I'd love to try some possible fixes for the SMP
> problems I'm having but that requires a functional world build.
>
> It breaks at gnu/usr.bin/cc/doc -- anyone else notice this?
>
> Jack.

Data Point: I built amd64-CURRENT as recently as Aug 19. A little while back I 
had to start ignoring warnings ( )-: ), but it is building. To help get 
better data, I just ran cvsup, make buildworld, and make buildkernel. They 
all worked.
-- 
Paul Scherf
pscherf@acm.org