X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
From: "Rod Pemberton" <do_not_have AT notemailnotq DOT cpm>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Rebuilding 2.04 from source
Date: Thu, 27 Jun 2013 05:40:04 -0400
Organization: Aioe.org NNTP Server
Lines: 96
Message-ID: <kqh11l$eec$1@speranza.aioe.org>
References: <CAB9Rao_8KC6ddube7z-4AcaJJbt4BJG3i3gjwhq5y-23KEC5PQ AT mail DOT gmail DOT com> <713e6460-511d-4b27-a9a5-b07cc63fd02d AT googlegroups DOT com> <kqab83$jpa$1 AT speranza DOT aioe DOT org> <a5de500e-67da-4fc7-83d9-8842e04e8235 AT googlegroups DOT com> <kqe74c$mp7$1 AT speranza DOT aioe DOT org> <f54c7536-b2e9-46e0-b3a7-561d52bcad00 AT googlegroups DOT com>
NNTP-Posting-Host: CNsg4fVcCsvs3UaOgZtQCw.user.speranza.aioe.org
X-Complaints-To: abuse AT aioe DOT org
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.2001
X-Notice: Filtered by postfilter v. 0.8.2
X-Newsreader: Microsoft Outlook Express 6.00.2800.2001
X-Priority: 3
X-MSMail-Priority: Normal
Bytes: 4607
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

<rugxulo AT gmail DOT com> wrote in message
news:f54c7536-b2e9-46e0-b3a7-561d52bcad00 AT googlegroups DOT com...
> On Wednesday, June 26, 2013 3:05:30 AM UTC-5, Rod Pemberton
> wrote:
...

<OT>

> > If yet another DOS C compiler is needed, it might be better to
> > get the DOS versions of LCC, versions 3.5 and 3.6, working
> > again.  Then, migrate useable updates from 4.1 and 4.2 back.
>
> Detlef Reimers already ported LCC 4.2 to DOS via DJGPP.
> It uses NASM (COFF) and DJGPP's (BinUtils) ld linker
> and older libc (2.01). He deleted his website, but I
> could upload it somewhere for you. He also ported EiC
> (interpreter) to DJGPP. (I would say "just email him",
> but ....)
>

Thanks for that mention.  So, I downloaded that version of LCC too.
At some point, I may look at it.

Wow, I'd swear I saw his website previously.  It's hard to
forget...  Maybe it was in regards to EiC.
http://web.archive.org/web/20120109161243/http://detlefreimers.de/

Now, you're probably wondering how I found that without any
available reference to his non-existant website whatsoever...  :-)
Try it.  Go to Google and Yahoo.  See if you can find it using only
"Detlef Reimers" and "Detlef Reimers lcc" as I did.  Good luck.
;-)

> > Or, it might be better to de-Linux-ify TCC, e.g., remove
> > the dlopen and dlsym related code, do test compiles with
> > DJGPP, and figure out how to bootstrap later, perhaps
> > with the old TurboC.
>
> TinyC was originally Linux only, so it has some weird
> kludges in there. IIRC, even on Win32 it used ELF
> for .o files! It's not easy to rebuild (at least IMHO),
> and when I tried with DJGPP, it didn't fully work
> correctly.
>

Maybe, using DJELF and then DJGPP would be a better path.

TCC is interesting to me because it's small and fast.
LCC is interesting to me because it worked on DOS.

> Honestly, I think something like PCC would ideally be
> better to port.

PCC as in the original Portable C Compiler?  Smile...  :-)

Didn't one of the BSD projects attempt to resurrect it a few years
back as their default C compiler?  AIR, they failed.  IIRC, it has
a bunch of odd quirks, obsolete code, incomplete functionality,
etc.  They might as well have chosen Tendra.  It's probably far
more complete and upto date.  Although, then they wouldn't have
had the prized BSD license...

> But porting something like Nils Holm's
> SubC (subset) is more realistic.

I seem to recall that I didn't like ... something ... about SubC,
but I don't have any idea of what it was or was in regards to.

> > My main concern is I can't test some of the really
> > old machines HIMEMX works on.  I also can't currently test the
> > machine it was intended for.  I may get it working by this
> > fall.  So, I just don't know if I introduced any unintended
> > errors.
>
> Japheth's already replied that he can't test multiple
> blocks either.
>

Well, the existing functionality needs to be retested too.  That's
just to confirm that all of it still works for various machines.
If all the retesting falls on me to do, it could be a while even
though I have a variety of machines.  Not all of them are working
and some are packed away.  I guess I was hoping that someone
maintaining HIMEMX had a test array of computers for regression
testing.

So, it may just be better to build it, package it, and list it as
experimental, or use at your own risk for now.  I'll let you know
if I do upload it somewhere so you can grab it.  Although, it is
easy to build.


Rod Pemberton