Date:	Tue, 13 Aug 1996 08:20:58 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To:	Tim Olmstead <timolmst AT cyberramp DOT net>
Cc:	djgpp AT delorie DOT com
Subject:	Re: COFF2EXE / GO32 problems
In-Reply-To:	<199608121354.IAA25172@mailhost.cyberramp.net>
Message-Id:	<Pine.SUN.3.91.960813081112.28748A-100000@is>
Mime-Version:	1.0

On Mon, 12 Aug 1996, Tim Olmstead wrote:

> >> GO32 ASIMUT.EXE (I typed)
> >> GO32 v1.12
> >> unknown file type 0x14c (0514)
> 
> This is the makefile I am using. I am trying to use "ld" to link the program
> because GCC choked on it. Maybe I am not giving GCC the correct command line
> switches.

I don't recommend using ld directly.  It will get you into a lot of
trouble unless you *really* know what you are doing.  Please try again
with GCC and if that doesn't work, post the exact gcc command line (or a
Makefile with that command) and the error message(s) printed by GCC. 

> I am having a lot of difficulty with the documentation with the
> DJGPP package. I'm sure someone thinks that INFO is a good thing, but not
> me. Oh well!

Please consider posting your gripes about Info.  It just might be that 
you are missing some of its features that will make your life much 
easier, or your setup of the Info system is not quite correct.  If you 
post your problems with Info, you might get help in using it better.

> $(LOCAL_TRGBIN)\asimut.exe : $(LOCAL_OBJECTS)

I suggest to avoid using backslashes in Makefiles.  Use Unix-style forward
slashes instead.  Backslashes might sometimes work, but will bite you some
day.  Backslash is an escape character in most Unix-born versions of Make
(GNU Make is one of them), and should be used in pairs (like in
C:\\DOS\\DIR) to make sure it gets as a single backslash to the commands
issued by Make. 

- Raw text -