From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 19 19:07:49 2004 Return-Path: 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 73CBC16A4CE for ; Fri, 19 Nov 2004 19:07:49 +0000 (GMT) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D20C43D39 for ; Fri, 19 Nov 2004 19:07:48 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 9B6811FF9AC; Fri, 19 Nov 2004 20:07:46 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id BD1251FF92F; Fri, 19 Nov 2004 20:07:44 +0100 (CET) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id 9E0431539F; Fri, 19 Nov 2004 19:07:31 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id 921B21538C; Fri, 19 Nov 2004 19:07:32 +0000 (UTC) Date: Fri, 19 Nov 2004 19:07:32 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: Sean McNeil In-Reply-To: <1100824228.92837.2.camel@server.mcneil.com> Message-ID: References: <1100664110.333.1.camel@server.mcneil.com> <20041117164803.6fce1c20@dolphin.local.net> <1100824228.92837.2.camel@server.mcneil.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de cc: freebsd-amd64@freebsd.org Subject: Re: WITH_LIB32 still doesn't work for me X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 19:07:49 -0000 On Thu, 18 Nov 2004, Sean McNeil wrote: Hi, > > > > > Unfortunately I haven't found a fix yet. > > > > > > Strange. I'm running amd64 CURRENT here, and built the lib32 stuff > > > just the other day for the first time without any problems. > > > > Oh, one more thing I discovered a while back that might be relevant > > here.. since I missed the obj step, there might be things sitting in > > the build $cwd's that are stale. cvs usually notices these, but cvsup > > might not. You might want to check if you have stray files > > under /usr/src (not /usr/obj). If you use cvsup. you might try "rm -rf > > kerberos5 secure" and re-cvsup. > > > > I saw similar failures like this very early on and it drove me crazy > > until I found a couple of .o files sitting in /usr/src. > > No Joy :( it seems I have a patch for this now. managed to pass the problematic parts. I will have to re-check some things if I can simplify it so it may take some hours for another buildworld to finish. just wanted to let you know that you hopefully don't need to spent more time on this. stay tuned... -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT