Message-Id: <199809260000.UAA17048@indy.delorie.com>
Comments: Authenticated sender is <mert0407 AT sable DOT ox DOT ac DOT uk>
From: "George Foot" <george DOT foot AT merton DOT ox DOT ac DOT uk>
To: Duncan Burch <duncanburch AT nospam DOT usa DOT net>
Date: Sat, 26 Sep 1998 00:57:46 +0000
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: RsxNt I HATE WINDOWS
Reply-to: mert0407 AT sable DOT ox DOT ac DOT uk
CC: djgpp AT delorie DOT com
Precedence: bulk

On 25 Sep 98 at 22:03, Duncan Burch wrote:

> Dalvemg wrote in message <360a6153 DOT 0 AT news1 DOT mweb DOT co DOT za>...
> >My first idea was to use RsxNT, but it won't work (I have gcc v2.8.xxx)
> >It only works with version 2.7.xxx Why? Which version is newer and where
> can
> >I get it (I thought the zip-picker would be the most up to date ?).
> 
> 
> It will work, it just needs some tweaking. If you email me I'll tell you how
> I got it to work.

I've heard from people using binutils 2.8.1 and gcc 2.8.0, 
2.8.1 or PGCC who have followed the my instructions and say 
that they work fine.  The instructions are here:

    http://www.canvaslink.com/gfoot/winallegro/how2rsx.txt

However I haven't heard anybody's opinions on my modifications
to the specs.  I posted them here a few days ago; you can also
see them here:

    http://www.canvaslink.com/gfoot/winallegro/specs

The idea behind them is to remove the modifications to
djgpp.env completely.  They also incorporate the correction
Doug Gale posted here a while ago, slightly modified.  The idea
is to ensure that when `-Zwin32' is specified none of djgpp's
own include files or libraries get used.  It also lets you use
RSXNTDJ's linker without overwriting djgpp's linker.

I'm aware of two problems.  Firstly the C++ headers won't be
found and C++ libraries won't be linked in.  I'm not sure
whether or not it is safe to use djgpp's libraries for this
anyway -- does anyone know for sure?

Secondly, the resource compiler won't be able to find Windows
header files (unless you define C_INCLUDE_PATH, which defeats
the object of the new specs file somewhat).  I don't know what
to do about this.

I'd really like to know if there are any other problems,
because several people have now installed in this way.  I
think it would be a good idea to either make a new RSXNTDJ
distribution or to make a proper patch to the existing
distribution, fixing the problems that we know about. 

-- 
george DOT foot AT merton DOT oxford DOT ac DOT uk