Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 19 Nov 2004 19:07:32 +0000 (UTC)
From:      "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>
To:        Sean McNeil <sean@mcneil.com>
Cc:        freebsd-amd64@freebsd.org
Subject:   Re: WITH_LIB32 still doesn't work for me
Message-ID:  <Pine.BSF.4.53.0411191904380.42526@e0-0.zab2.int.zabbadoz.net>
In-Reply-To: <1100824228.92837.2.camel@server.mcneil.com>
References:  <1100664110.333.1.camel@server.mcneil.com>  <20041117164803.6fce1c20@dolphin.local.net> <1100824228.92837.2.camel@server.mcneil.com>

next in thread | previous in thread | raw e-mail | index | archive | help
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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.53.0411191904380.42526>