Date:	Wed, 8 Feb 1995 04:17:53 -0400 (AST)
From:	Bill Davidson <bdavidson AT ra DOT isisnet DOT com>
Subject:	Re: Problems with (first compile under) djgpp/gcc
To:	Mark Hull-Richter <mhr AT sparc DOT SanDiegoCA DOT ATTGIS DOT COM>
Cc:	djgpp AT sun DOT soe DOT clarkson DOT edu

On Tue, 7 Feb 1995, Mark Hull-Richter wrote:

> on four Unix platforms and would like to have run on my PC.  I gave up on
> Turbo C and Borland C++ because they gave me just too many problems that did
> not seem to be related to the code itself (minor things like different include
> paths, sizeof(char) == 0, j += k fails, etc).  So I turnedto djgpp.

Wow, I have never seen anything like that under Turbo C!  Certainly 
simple statements like j += k never gave me problems, and sizeof(char) 
always evaluates to 1.

> What's wrong?

You indicate that djgpp is in f:\gcc, and f:\gcc\bin is at the end of 
your path.  You might try putting it at the front in case another copyof 
go32 is lurking around somewhere, but that shouldn't produce the messages 
you gave.  Did you set your DJGPP environment variable?  It should look like
SET DJGPP=f:/gcc/djgpp.env
If not, the linker won't know where to find the libraries.

> f:\gcc\bin (at the end) and I run `f:\gcc\bin\setdjgpp f:\gcc f:/gcc' as a
> prelude to running `make' on the makefile.
That should do it, but I would rather set all the variables myself just 
to be sure.
Do you, in fact, have the libraries?  Look in f:\gcc\lib.  Maybe even 
grep the files there to see if the function in question exists.

> The only difference between the PC
> makefile and my unix makefile is that the target `lh' has the "-o lh" before
> the modules list instead of after it.  There are no other "make.exe" files in

The order of arguments to gcc or ld should make no difference.

- Raw text -