From: wes.parish@paradise.net.nz (Wesley Parish)
Subject: [TUHS] gcc-3.4.6 and old unix
Date: Mon, 24 Apr 2006 20:44:07 +1200 (NZST) [thread overview]
Message-ID: <1145868247.444c8fd727f62@www.paradise.net.nz> (raw)
In-Reply-To: <444C7F4E.7040906@icpnet.pl>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2621 bytes --]
djggp relies on a DOS extender to run its 32-bit programs in a 16-bit
operating environment on a 32-bit machine. go32 is Delorie's own DOS extender
- OpenWatcom offers at least two other DOS extenders to pull the same kind of
trick.
If the purpose is to run a 32-bit Unix C compiler in a 16-bit Unix operating
environment on a 16-bit machine, it just won't work. I've never heard of
anyone ever running djgpp on a 286, either.
Just my 0.02c
Wesley Parish
Quoting Andrzej Popielewicz <vasco at icpnet.pl>:
> Michael Davidson napisaÅ(a):
>
> >Bill Cunningham wrote:
> >
> >
> >
> >> Has anyone thought of or tried to port the gcc to the old unixes? It
> >>would have to be a very scaled down version. A C compiler that would
> work
> >>with modern c89 or c99. Something to get a C compiler working that
> would
> >>compile todays programs. The old C compilers can be kept for
> safekeeping as
> >>they don't work much anymore.
> >>
> >>
> >>
> >>
> >By "the old unixes" I assume that you mean things like V6 and V7
> >for the PDP-11.
> >
> >Both gcc and GNU binutils already support PDP-11 targets, at
> >least to some extent, so you can already do cross development
> >targeted at the PDP-11.
> >
> >Trying to actually host gcc on a 16 bit UNIX system is almost
> >certainly a completely futile and pointless exercise - it is many,
> >*many* times too big and I am pretty sure that it assumes at
> >least a 32 bit host - if you cut it down enough so that it fit it
> >isimply wouldn't be gcc any more.
> >
> >I suspect that you would also find that most of "todays programs"
> >wouldn't fit either ...
> >
> >Michael Davidson
> >
> >[ and, actually, the old C compiuers still work just fine for
> > ompiling the code that they were priginally intended for ]
> >
> >
> >_______________________________________________
> >TUHS mailing list
> >TUHS at minnie.tuhs.org
> >https://minnie.tuhs.org/mailman/listinfo/tuh s
> >
> >
> >
> What about creating "old unix" version of djgpp. djgpp compiler is 32
> bit "gcc" running in 16 bit DOS.
> Perhaps DeJorie could help.
>
> Andrzej
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/tuhs
>
"Sharpened hands are happy hands.
"Brim the tinfall with mirthful bands"
- A Deepness in the Sky, Vernor Vinge
"I me. Shape middled me. I would come out into hot!"
I from the spicy that day was overcasked mockingly - it's a symbol of the
other horizon. - emacs : meta x dissociated-press
next prev parent reply other threads:[~2006-04-24 8:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-23 23:27 Bill Cunningham
2006-04-24 0:00 ` Peter Jeremy
2006-04-24 0:33 ` Michael Davidson
2006-04-24 7:33 ` Andrzej Popielewicz
2006-04-24 7:47 ` Peter Jeremy
2006-04-24 8:44 ` Wesley Parish [this message]
2006-04-24 9:50 ` Andrzej Popielewicz
2006-04-24 13:05 ` [TUHS] [pups] " Wesley Parish
2006-04-24 16:06 ` Toby Thain
2006-04-25 6:28 ` Andrzej Popielewicz
2006-04-24 9:29 ` [TUHS] " Lars Brinkhoff
2006-04-24 12:53 ` John Cowan
2006-04-24 18:01 Jose R Valverde
2006-05-02 17:09 ` A. Wik
2006-05-02 17:57 ` M. Warner Losh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1145868247.444c8fd727f62@www.paradise.net.nz \
--to=wes.parish@paradise.net.nz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).