Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 18 Nov 2004 13:37:09 -0800
From:      Peter Wemm <peter@wemm.org>
To:        freebsd-amd64@freebsd.org
Subject:   Re: WITH_LIB32 still doesn't work for me
Message-ID:  <200411181337.10114.peter@wemm.org>
In-Reply-To: <20041117164803.6fce1c20@dolphin.local.net>
References:  <1100664110.333.1.camel@server.mcneil.com> <1100723437.18003.0.camel@server.mcneil.com> <20041117164803.6fce1c20@dolphin.local.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday 17 November 2004 02:48 pm, Conrad J. Sabatier wrote:
> On Wed, 17 Nov 2004 12:30:37 -0800, Sean McNeil <sean@mcneil.com> 
wrote:
> > On Wed, 2004-11-17 at 18:15 +0000, Bjoern A. Zeeb wrote:
> > > On Wed, 17 Nov 2004, Peter Wemm wrote:
> > > > On Tuesday 16 November 2004 08:01 pm, Sean McNeil wrote:
> > > > > Here is what I get with make -s buildworld:
> > > > >
> > > > > ===> libasn1 (buildincludes)
> > > > > /usr/obj/usr/src/amd64/usr/bin/ld: skipping
> > > > > incompatible /usr/obj/usr/src/amd64/usr/lib/libgcc.a when
> > > > > searching for -lgcc
> > > > > /usr/obj/usr/src/amd64/usr/bin/ld: cannot find -lgcc
> > > > > *** Error code 1
> > > > >
> > > > > Stop in /usr/src/kerberos5/tools/make-print-version.
> > > > > *** Error code 1
> > > >
> > > > 5.x or HEAD?  I haven't committed a fix to 5.x yet.
> > >
> > > I still have trouble with HEAD.
> >
> > This was in HEAD for me as well.  It is also the first time I am
> > trying this so I do not have any lib32 stuff already installed.
> >
> > > Sent you a some lines longer trace of the above yesterday evening
> > > I think it had been also complaining about Object directory not
> > > changed...
> > >
> > > 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.
-- 
Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com
"All of this is for nothing if we don't go to the stars" - JMS/B5



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