From: MFLD <mfld.fr@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: ELKS <Linux-8086@Vger.Kernel.Org>
Subject: Re: We have a whole new ton of goodies to investigate...
Date: Wed, 15 Apr 2015 19:10:05 +0200 [thread overview]
Message-ID: <552E9B6D.5020908@gmail.com> (raw)
In-Reply-To: <20150403214017.2e62b257@www.etchedpixels.co.uk>
Hello,
Started to have a look to that huge stuff (not really sorted...), but
could you please explain the idea you have in mind ? Is this a suggest
to replace the DEV86 toolchain by something else ?
By the way, for the background, could you also tell what is the
toolchain you target for Fuzix on 8080/Z80 ?
Regards,
MFLD
Le 03/04/2015 22:40, Alan Cox a écrit :
> http://www.nesssoftware.com/home/mwc/source.php
>
> And in the Coherent tree there isn't just the 386 release but the 286
> release and all the compiler and tool chain pieces plus all the
> utilities, manuals, etc. The dump seems to include 8086, 286 and 386
> compilers and assemblers but not an 8086/286 linker.
>
--
To unsubscribe from this list: send the line "unsubscribe linux-8086" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-04-15 17:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-03 20:40 We have a whole new ton of goodies to investigate Alan Cox
2015-04-15 17:10 ` MFLD [this message]
2015-04-15 21:41 ` Alan Cox
2015-04-16 7:35 ` MFLD
2015-04-16 11:49 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2015-04-16 11:14 LM
2015-04-16 11:39 ` Alan Cox
2015-04-26 21:22 u-vpoa
2015-04-26 23:31 ` Alan Cox
2015-04-27 7:06 ` u-vpoa
2015-04-27 10:53 ` Alan Cox
2015-04-27 12:30 ` u-vpoa
2015-04-27 13:35 ` Alan Cox
2015-04-27 14:44 ` u-vpoa
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=552E9B6D.5020908@gmail.com \
--to=mfld.fr@gmail.com \
--cc=Linux-8086@Vger.Kernel.Org \
--cc=alan@lxorguk.ukuu.org.uk \
/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