Re: EMX on DOS

[Paul Edwards]

"Paul Edwards" <kerravon@nosppaam.w3.to> wrote in message 
news:nAqpb.176886$bo1.40724@news-server.bigpond.net.au...
> I did a general Posix one for any unspecified Posix system,
> which doesn't necessarily have a shell.

Incidentally, there are other reasons why someone
might be unable to run configure.

I spent HOURS trying to figure out why it wasn't
working on the Sun Solaris system.  Turned out that
the default .profile I was provided with had CC set
to CC, and this was overriding the "cc" program
which I expected it to use.  I think I was seeing the
CC and believing that that was config somehow
telling me that it was using an INTERNAL variable
to run the compiler, and I thought nothing of it.  I didn't
know we had a CC compiler install.

What I DID know was that we had a posix compliant
compiler in cc, and all I needed was posix source code
and a list of files to compile and I would be in business.
That's it.  Nothing more, nothing less.

Incidentally, I still haven't found out why when going
from cvs 1.11.<m> to cvs 1.11.<n> the executable jumped
in size enormously.

Small code changes don't do things like that.  A small
change to Posix compliant source code would not have
caused a change like that.  I was only expecting small
code changes, not mammoth increases in executable size.

These things are all eliminated if you just provide
Posix source code.  Very simple, very portable.  Compliant
C code is portable.  C code that depends on other software
to be installed is not.  Portable C code will compile on
EMX 0.9d.  I would never be in the position of having to
install a different C compiler, just to get the source code to
compiler.  Or a different version of bash.  Or a different
operating system.  Or a different installation of a particular
operating system.  That ain't portable!

BFN.  Paul.