From:	"John M. Aldrich" <fighteer AT cs DOT com>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: NT: Problems with go32
Date:	Tue, 17 Sep 1996 19:34:43 -0700
Organization:	Three pounds of chaos and a pinch of salt
Lines:	61
Message-ID:	<323F5FC3.7AD9@cs.com>
References:	<323D7B6C DOT 7789 AT po DOT uni-stuttgart DOT de> <51m4n8$uh4 AT rs18 DOT hrz DOT th-darmstadt DOT de>
Reply-To:	fighteer AT cs DOT com
NNTP-Posting-Host:	ppp211.cs.com
Mime-Version:	1.0
To:	Alexander Lehmann <lehmann AT fb0432 DOT mathematik DOT th-darmstadt DOT de>
CC:	Martin DOT Bernreuther AT po DOT uni-stuttgart DOT de
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Alexander Lehmann wrote:
> 
> Martin Bernreuther <Martin DOT Bernreuther AT po DOT uni-stuttgart DOT de> wrote:
>
> : After installing djgpp V2 on WindowsNT 3.51 I have the following problem:
> 
> : While trying to compile a simple C-file with e.g.
> : "gcc test.c", the program go32 cannot be found. After renaming
> : "go32-v2.exe" to "go32.exe" I get the following error message:
> 
> : go32/v1: cannot find v1's go32.exe
> 
> : What's going wrong? Do I need the V1 go32.exe and why?

You seem to have an old v1.x distribution around somewhere, and you are
calling its 'gcc', not v2's.  Check your PATH environment variable, and
delete any references to older DJGPP bin directories.  For that matter,
you can probably delete v1.x altogether, unless you really REALLY need
it around for compatibility.

If you made the (common) mistake of unzipping v2 over top of your old
v1.x distribution, then you have to delete everything and start over-
the two are not compatible.

However, v2 CAN run old v1.x programs, if you supply it with a copy of
the 'go32.exe' from v1.x.  The FAQ (v2/faq201b.zip from your favorite
SimTel mirror) describes how to do this in section 22.12.

> You shouldn't need go32 (either v1 nor v2), maybe you are calling a
> test program in another directory that is compiled with 1.x. Under
> unix the default name for the compiled executable is a.out, with DOS
> it's probably a.exe, which means that you will not compile a test.exe
> program with that call. Instead you should use gcc -o test test.c.

In fact, the best command line to use for all compiles in general is

gcc -Wall -g -O -o test test.c

Of course, replace test and test.c with the actual names of your
programs.

However, that didn't appear to be his problem.

> PS. on a sidenote, does djgpp include a which-like utility? (to locate
> an certain executable), this would be rather useful for such problems.

It does not, but I wrote a new version of 'whence' using DJGPP v2 a
couple
of months ago.  It works almost identically to the Unix version, AFAIK.
If you want the code, I can email it to you - it's quite small.  Please
specify binary, source, or both.

-- 
--------------------------------------------------------------------------
| John M. Aldrich, aka Fighteer I    |         fighteer AT cs DOT com          
|
| Proud owner of what might one day  |    http://www.cs.com/fighteer    
|
| be a spectacular MUD...            |  Plan: To make Bill Gates suffer 
|
--------------------------------------------------------------------------

- Raw text -