Date: Wed, 8 Nov 1995 09:50:40 +0100 (MET) From: J Wunsch <j@uriah.heep.sax.de> To: mark@grondar.za (Mark Murray) Cc: current@FreeBSD.org Subject: Re: Lint won't bootstrap... Message-ID: <199511080850.JAA16034@uriah.heep.sax.de> In-Reply-To: <199511071644.SAA27162@grumble.grondar.za> from "Mark Murray" at Nov 7, 95 06:44:17 pm
next in thread | previous in thread | raw e-mail | index | archive | help
As Mark Murray wrote: > > ===> xlint > ===> llib > lint -Cposix /a/src/usr.bin/xlint/llib/llib-lposix > llib-lposix: > types.h:60: warning: ANSI C does not support 'long long' > types.h:61: warning: ANSI C does not support 'long long' > types.h:72: warning: ANSI C does not support 'long long' > types.h:63: warning: ANSI C does not support 'long long' > types.h:64: warning: ANSI C does not support 'long long' > runetype.h:58: syntax error > runetype.h:73: syntax error > runetype.h:76: syntax error > runetype.h:76: warning: function prototype parameters must have types > runetype.h:80: syntax error > llib-lposix:123: redeclaration of fgets > llib-lposix:143: redeclaration of ftell > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > > I have done a "make includes", and I have reinstalled lint a couple of > times. Before I do any serious debugging - is there anything trivial > I can do to fix this? Sorry, i have to commit a series of minor changes in order to allow the compilation of lint's llib. You could temporarily comment out the llib subdir, and try to do something useful with lint. :) I promise to fix everything at least by next weekend. Yup, once lint is up & running, we immediately start seeig problems everywhere around in our sources (like the above). Ain't it fun? :) Does anybody have a good idea on how to make bootstrapping for the people as easy as possible? The biggest problem is that you can compile the llib subdir only after first succesfully installing from the xlint subdir, so a running version of lint(1) is around. I've already thought about .if exist .../bin/lint SUBDIRS += llib .endif but i'm not sure if it's worth the effort, since the .if statement is supposed to hit everytime but the first time. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199511080850.JAA16034>