Date: Mon, 22 Jun 1998 09:05:50 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Sunil Rao <sunil AT raos DOT demon DOT co DOT uk>
cc: djgpp AT delorie DOT com
Subject: Re: LC-Lint
In-Reply-To: <s+$mMQB8jTj1EwjM@raos.demon.co.uk>
Message-ID: <Pine.SUN.3.91.980622090513.9130A-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Sun, 21 Jun 1998, Sunil Rao wrote:

> but it still doesn't work! it's complaining about uninitialised
> environment variables. when i try it on "hello, world"...
[snip]
>  bash$ lclint hello.c
>  LCLint 2.4 --- 14 Apr 98
> 
>  Cannot find standard library: ansi.lcd
>       Check LARCH_PATH environment variable.
>  hello.c: (in function main)
>  hello.c:5:9: Unrecognized identifier: printf

No, it complains about LARCH_PATH being not defined correctly.

>  bash$ set
> 
> <SNIP>
> 
>  LARCH_PATH = c:/djgpp/lclint-2.4/lib/
             ^ ^
Are these blanks real?  If so, you defined the variable incorrectly:
it shouldn't include blanks around the equals sign.

Also, did you remember to export LARCH_PATH?

>  LARCH_PATH = <not set> (default = .:c:/djgpp/lclint-2.4/lib/)

This might indicate another problem, which might be related or not
related to how you set LARCH_PATH and export it.  See those colons in
the default value of LARCH_PATH?  That means LC-Lint uses Unix-style
path lists for this and other environment variables.  This won't work
on DOS, since DOS pathnames like c:/djgpp/lclint-2.4/lib include a
colon after the drive letter.  You will need to change LC-Lint to use
semi-colon instead, or use directory names with no drive letter (like
in /djgpp/lclint-2.4/lib) and make sure you work on the same drive.

If all of the above doesn't help, you will need to step with a
debugger into the function which gets LARCH_PATH from the environment
and see what's wrong there.