Date: Wed, 16 Jun 2004 22:21:59 -0700 From: Sean McNeil <sean@mcneil.com> To: Giorgos Keramidas <keramida@hellug.gr> Cc: freebsd-amd64@freebsd.org Subject: Re: new binutils broken for amd64 Message-ID: <1087449719.84160.2.camel@server.mcneil.com> In-Reply-To: <20040617051540.GA5680@igloo.linux.gr> References: <1087442023.22390.2.camel@server.mcneil.com> <1087448595.4494.5.camel@server.mcneil.com> <20040617051540.GA5680@igloo.linux.gr>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 2004-06-16 at 22:15, Giorgos Keramidas wrote: > On 2004-06-16 22:03, Sean McNeil <sean@mcneil.com> wrote: > > On Wed, 2004-06-16 at 20:13, Sean McNeil wrote: > > > I believe that most likely there is a config.guess issue here. It would > > > appear that the linker isn't setting > > > > > > NATIVE=yes > > > USE_LIBPATH=yes > > > > > > for freebsd/amd64. These should be set when host and target are the > > > same. This is causing all sorts of compilation problems. > > > > Actually, this appears to be a problem with the make mechanism. > > > > If I do > > > > make buildworld && make installworld > > > > it creates an improper ld. If I do > > > > cd /usr/src/gnu/usr.bin/binutils/ld > > make clean > > make > > make install > > > > Then I get an ld that works properly. > > > > Very odd. > > Hmmm, are you by any chance using a /usr/obj of older builds? > What happens if you start over with a completely clean /usr/obj? > > If 'make clean' or 'make cleandir' is what it takes to fix things, stale > object files from /usr/obj could be the source of all troubles. That is possible. I usually just rm -rf /usr/obj/* but I don't do it religiously. I'll try doing another buildworld/installworld later to see.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1087449719.84160.2.camel>