Date: Tue, 18 Jan 2000 21:38:56 +1100 (EST) From: Bruce Evans <bde@zeta.org.au> To: Jim Bloom <bloom@acm.org> Cc: Brian Fundakowski Feldman <green@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/gnu/usr.bin/texinfo/info Makefilesrc/gnu/usr.bin/texinfo/install-info Makefile src/gnu/usr.bin/texinfo/makeinfoMakefile src/gnu/usr.bin/texinfo/texindex Makefile Message-ID: <Pine.BSF.4.10.10001182049560.15488-100000@alphplex.bde.org> In-Reply-To: <3883C7CA.7C5F4F76@acm.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 17 Jan 2000, Jim Bloom wrote: > Brian, > > I found the problem. A buildworld gets past this problem now. > > I believe the problem has to do with the build order. You added texinfo > after the compiler was rebuilt. As such, the compilation of texinfo > used the newly compiled compiler which behaves differently than the > installed compiler. It was passing crt1.o to ld instead of > /usr/lib/crt1.o that was passed by the system compiler. There is no > path search, so this failed. > > I forgot to save the original copy of Makefile.incl, so I can't send a > diff, but you simply need to swap the order of gnu/usr.bin/cc and > gnu/usr.bin/texinfo in the cross-tools target. Tools should be be built in the host environment. Putting the path to the tools binaries in $PATH for building tools breaks this. The host environment is polluted a little whenever a new tool is installed, except it is polluted a lot when a new cc is installed. This should be handled by not putting new cross-tools binaries in $PATH while building cross-tools. In any case, texinfo is a bootstrap-tool, not a cross-tool. There should have been no problems if it had been added to the right list and tested. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.10001182049560.15488-100000>