Date: Sun, 6 Aug 2000 09:44:36 +0300 (IDT) From: Eli Zaretskii X-Sender: eliz AT is To: Matt Lewandowsky cc: djgpp AT delorie DOT com Subject: Re: Uh oh. Another newbie. (Sorta...) In-Reply-To: <4.3.2.7.0.20000805192349.00ab2a60@mail.subdimension.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Sat, 5 Aug 2000, Matt Lewandowsky wrote: > I've set TEST_FINDS_EXE, so hopefully the finding gcc thing should be > fixed. I've just looked over the FAQ again, and didn't see any mention of > this. This seems like a easy enough thing to solve that probably comes up > often. Why is it not there? Because it doesn't come up often, contrary to your assumption, and the FAQ only holds frequent questions. The ported packages do this transparently by providing a config.site file which sets TEST_FINDS_EXE before running the script. I think at least the latest Bash release comes with a global config.site that does this as well. > configure:1198: checking for initscr in -lcurses > configure:1217: gcc -o conftest -g -O2 conftest.c -lcurses 1>&5 > d:/djgpp/bin/ld.exe: cannot find -lcurses This is your problem: why doesn't GCC find libcurses.a in your lib subdirectory? Do you have libcurses.a in there? What happens if you try the following from the command line? gcc -o foo foo.c -lcurses (where foo.c is any C source file). > This doesn't look right to me... is /djgpp/lib not in the LIBPATH by default? %DJDIR%/lib is searched by the linker by default, otherwise the configure script would not be able to link any of the programs it tries. You need to make sure that libcurses.a is in the same directory as libc.a.