Date: Wed, 25 Apr 2001 16:18:14 +1000 (EST) From: Bruce Evans <bde@zeta.org.au> To: John Baldwin <jhb@FreeBSD.org> Cc: Jeroen Ruigrok van der Werven <asmodai@FreeBSD.org>, cvs-all@FreeBSD.org, cvs-committers@FreeBSD.org Subject: RE: cvs commit: src/usr.bin/xlint/llib Makefile Message-ID: <Pine.BSF.4.21.0104251611310.21711-100000@besplex.bde.org> In-Reply-To: <XFMail.010424133435.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 24 Apr 2001, John Baldwin wrote: > On 24-Apr-01 Jeroen Ruigrok van der Werven wrote: > > asmodai 2001/04/24 13:23:38 PDT > > > > Modified files: > > usr.bin/xlint/llib Makefile > > Log: > > Wrap lint calling in a variable. > > > > Set LINT to the obj path, since we need to use the new lint's features > > to create .ln files. We do not want to use the installed version for that, > > since that might create files according to the old lint. > > > > This is still a work in progress to clean this all up, but it gets > > through buildworld, which was the problem at hand. > > Err, isn't the point of making lint a build-tool so that you can use the build > tool here rather than the lint binary you just built? This breaks cross > builds. :( It would have to be a bootstrap tool for that. It certainly should be a bootstrap tool ... I discussed this in more detail in private mail. > You should just be able to use the 'lint' in your path since that should map to > the 'lint' program in the build-tools. Not quite. `lint' is just the driver stage. It has hard-coded paths to /usr/libexec/lint[1-2], so the new version of lint mostly doesn't get used whether or not `lint' is run from the obj dir or according to the path. 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.21.0104251611310.21711-100000>