Date: Sun, 23 Apr 2000 17:10:30 -0400 (EDT)
Message-Id: <200004232110.RAA20291@indy.delorie.com>
From: Eli Zaretskii <eliz AT delorie DOT com>
To: "Roger D. Hunt" <rhunt AT worldaccessnet DOT com>
CC: djgpp AT delorie DOT com
In-reply-to: <3902FD2B.D24A4B89@worldaccessnet.com> (rhunt@worldaccessnet.com)
Subject: Re: Can't get djgpp set up - help please!
References: <3901E4BE DOT CBE9C9B2 AT worldaccessnet DOT com> <200004221825 DOT OAA18872 AT indy DOT delorie DOT com> <3902FD2B DOT D24A4B89 AT worldaccessnet DOT com>
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

> Date: Sun, 23 Apr 2000 06:39:57 -0700
> From: "Roger D. Hunt" <rhunt AT worldaccessnet DOT com>
>
>        11 file(s)      7,697,464 bytes
>                      114,548,736 bytes free
> 
> C:\PROGRAMS\GCC>
> 
> Note that ZIP-PICKER states that these files should occupy
> 7,655,958 bytes total.  I don't know if that is significant.

It is not significant.

> (4) The set command shows the environment variables, etc.:
> 
> C:\PROGRAMS\GCC>set
> COMSPEC=C:\DOS\COMMAND.COM
> PROMPT=$p$g
> PATH=\DOS;\MISC;\PUBLIC;\MENUS;\PROGRAMS\CDROM;\PROGRAMS\G77\BIN;C:\PROGRAMS\GCC
> 
> \BIN;\PROGRAMS\FORTRAN\BIN;..;

This is okay, but I suggest to put the C:\PROGRAMS\GCC\BIN directory
first, before \DOS and the rest.

> DJGPP=c:\programs\gcc\djgpp.env

This is okay.

> LIBRARY_PATH=\programs\g77\lib
> LIB=\programs\fortran\lib

These two worry me (as does \PROGRAMS\G77\BIN in your PATH).  Do you
have a separate installation of g77, the GNU Fortran 77 compiler,
somewhere on this system?  If you do, it is quite possible that this
is the source of your problems: g77 relies on GCC as its back-end, so
perhaps you do have another version of gcc unbeknownst to you.

If you do have g77 and another version of GCC installed, you will have
to arrange two batch files to set up the environment for each one of
them, and take care that environment variables such as PATH, LIB, and
LIBRARY_PATH are never set up for g77 when you work with DJGPP, and
vice versa.

> C:\PROGRAMS\GCC>gcc -v hello.c
> gcc version 2.7.2.1.f.1

Note the version of GCC: it's 2.7.2.1, not 2.95.2, and it has a .f.1
suffix.  I'm now quite convinced that you *do* have another,
incompatible version of GCC on that machine.

>  cpp -lang-c -v -undef -D__GNUC__=2 -D__GNUC_MINOR__=7 -D__32BIT__ -D__EMX__ -Di
> 
> 386 -D__32BIT__ -D__EMX__ -D__i386__ -D__i386 -Asystem(unix) -Asystem(emx) -Acpu

And here's my evidence: see that -D__EMX__ switch?  It tells that you
have and EMX port of GCC, probably for the g77 version you use (or
used in the past) lurking somewhere on your disk.  Since
\PROGRAMS\G77\BIN is earlier on the PATH than the DJGPP's bin
subdirectory, when you type "gcc -v hello.c", you actually invoke that
older EMX-compiled GCC.  And that is what gives you trouble.

Solution: you need to arrange a way to switche between the g77
environment and the DJGPP environment.  They use different ports of
two different and incompatible versions of GCC.