Mail Archives: djgpp/2013/06/26/00:48:56
--bcaec5015cf73bf78a04e006ec8f
Content-Type: text/plain; charset=ISO-8859-1
So rugxulo & Rod are following. I am looking to build DJGPP completely
from scratch on a DOS box. If you reference typical GCC porting guides
[1][2][3][4], you start by building binutils, then GCC's deps (if using 3.x
or later), then GCC, all using the typical ./configure && make && make
install.
-L
[1] http://wiki.osdev.org/DJGPP
[2] http://wiki.osdev.org/C%2B%2B_Bare_Bones
[3] http://wiki.osdev.org/GCC_Cross-Compiler
[4] http://virtuallyfun.superglobalmegacorp.com/?p=333
On Tue, Jun 25, 2013 at 9:44 AM, <rugxulo AT gmail DOT com> wrote:
> Hi,
>
> On Monday, June 24, 2013 3:51:14 PM UTC-5, Rod Pemberton wrote:
> >
> > My results with configure scripts have been it either works or it
> > doesn't. When it doesn't, generally the code is using something
> > the DJGPP doesn't support. When it does, the app compiles for
> > DJGPP. I.e., if the configure script doesn't work, it's a strong
> > indication it won't compile without some work.
>
> I'd honestly rather roll my own tools than use those. Well, the fact
> that it doesn't barely work on DJGPP anyways makes that almost
> unavoidable.
>
> > MinGW in DOS with HX... Interesting. How many functions are in
> > MSVCRT? I.e., would it be easy to port MinGW to DOS?
>
> I don't think the full MinGW environment works, but I've not tried.
> Some standalone tools (or those compiled by) do work. E.g. Oxford
> Oberon or TinyC (often needing HDPMI=32 or DPMILDR=136). BTW,
> TinyC had a big update recently.
>
> MSVCRT is a "known .DLL", originally (I think?) from MSVC 6. MinGW
> and TinyC use it, but OpenWatcom (thankfully) doesn't. It's very
> proprietary, so I'm not sure (at least in Express Editions) you can
> share it with anyone. (There are other .DLLs from other MS compilers.)
> It only supports C89 as (IIRC) MS still do not intend to support
> anything newer except via C++.
>
> Like I said, newer ReactOS .DLL doesn't work, but older 0.3.14
> MSVCRT.DLL seems to work with HX, at least for the very few apps
> I tried.
>
> I don't know what "port MinGW to DOS" means, but I'm very very
> skeptical.
>
> > My first question to Louis is how could MinGW rebuild DJGPP
> > without POSIX support? CygWin has POSIX support.
>
> Presumably MinGW added a few POSIX stubs as GCC wouldn't run without
> such.
>
> > My second question is to Louis is why you're rebuilding version
> > 2.04? 2.04 doesn't work as well with DOS as 2.03. There are some
> > definate bugs with it, at least with MS-DOS v7.10. IIRC, 2.04 is
> > designed to work better in a Windows XP console ("dosbox") window,
> > not real-mode DOS.
>
> 2.04 (circa 2003) "mostly" works fine for everything I tested. Sure,
> there are some rare bugs, but they were fixed in CVS (not that I
> really tried that). The only problem with 2.04 is that it wasn't
> as heavily tested in all environments as 2.03p2. Plus, there's been
> no release manager nor major interest since it was always "good
> enough" for the main developers. At least, that's what little I
> recall understanding about it. I don't have anything against
> 2.03p2, but I'm not sure that's totally perfect either, for
> various minor reasons.
>
> > Rugxulo, I know I need to get an email account and get on "DOS
> > ain't dead forums"...
>
> No pressure! :-) I know you hate email, but perhaps GNU PG would
> help??
>
> > But, until then, could you do me another
> > favor and let Japheth know I posted a patch for HIMEMX to
> > comp.os.msdos.programmer? It supports multiple 001 E820h memory
> > blocks above 1MB. If you recall, you posted a message or two there
> > for me previously discussing the issue.
>
> Sure, but keep in mind that Japheth long ago disclaimed any hold
> over HimemX, so he's not really a maintainer (anymore, if ever).
> IIRC, he even refused the simple "jmp $+2" 386 patch. :-(
>
> Though worst case, I'll just try to mirror your patch to iBiblio.
>
> > If you do, thanks and sorry for the trouble...
>
> No trouble, but my usefulness is limited. But I've gone ahead and
> posted there, so we'll see what he says.
>
--bcaec5015cf73bf78a04e006ec8f
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">So rugxulo & Rod are following. =A0I am looking to bui=
ld DJGPP completely from scratch on a DOS box. =A0If you reference typical =
GCC porting guides [1][2][3][4], you start by building binutils, then GCC&#=
39;s deps (if using 3.x or later), then GCC, all using the typical ./config=
ure && make && make install.<div>
<br></div><div style>-L</div><div><br></div><div>[1]=A0<a href=3D"http://wi=
ki.osdev.org/DJGPP">http://wiki.osdev.org/DJGPP</a></div><div>[2] <a href=
=3D"http://wiki.osdev.org/C%2B%2B_Bare_Bones">http://wiki.osdev.org/C%2B%2B=
_Bare_Bones</a></div>
<div>[3]=A0<a href=3D"http://wiki.osdev.org/GCC_Cross-Compiler">http://wiki=
.osdev.org/GCC_Cross-Compiler</a></div><div>[4]=A0<a href=3D"http://virtual=
lyfun.superglobalmegacorp.com/?p=3D333">http://virtuallyfun.superglobalmega=
corp.com/?p=3D333</a></div>
<div><br></div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Tue, Jun 25, 2013 at 9:44 AM, <span dir=3D"ltr"><<a href=3D"=
mailto:rugxulo AT gmail DOT com" target=3D"_blank">rugxulo AT gmail DOT com</a>></span=
> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Hi,<br>
<div class=3D"im"><br>
On Monday, June 24, 2013 3:51:14 PM UTC-5, Rod Pemberton wrote:<br>
><br>
> My results with configure scripts have been it either works or it<br>
> doesn't. =A0When it doesn't, generally the code is using somet=
hing<br>
> the DJGPP doesn't support. =A0When it does, the app compiles for<b=
r>
> DJGPP. =A0I.e., if the configure script doesn't work, it's a s=
trong<br>
> indication it won't compile without some work.<br>
<br>
</div>I'd honestly rather roll my own tools than use those. Well, the f=
act<br>
that it doesn't barely work on DJGPP anyways makes that almost<br>
unavoidable.<br>
<div class=3D"im"><br>
> MinGW in DOS with HX... =A0Interesting. =A0How many functions are in<b=
r>
> MSVCRT? =A0I.e., would it be easy to port MinGW to DOS?<br>
<br>
</div>I don't think the full MinGW environment works, but I've not =
tried.<br>
Some standalone tools (or those compiled by) do work. E.g. Oxford<br>
Oberon or TinyC (often needing HDPMI=3D32 or DPMILDR=3D136). BTW,<br>
TinyC had a big update recently.<br>
<br>
MSVCRT is a "known .DLL", originally (I think?) from MSVC 6. MinG=
W<br>
and TinyC use it, but OpenWatcom (thankfully) doesn't. It's very<br=
>
proprietary, so I'm not sure (at least in Express Editions) you can<br>
share it with anyone. (There are other .DLLs from other MS compilers.)<br>
It only supports C89 as (IIRC) MS still do not intend to support<br>
anything newer except via C++.<br>
<br>
Like I said, newer ReactOS .DLL doesn't work, but older 0.3.14<br>
MSVCRT.DLL seems to work with HX, at least for the very few apps<br>
I tried.<br>
<br>
I don't know what "port MinGW to DOS" means, but I'm very=
very<br>
skeptical.<br>
<div class=3D"im"><br>
> My first question to Louis is how could MinGW rebuild DJGPP<br>
> without POSIX support? =A0CygWin has POSIX support.<br>
<br>
</div>Presumably MinGW added a few POSIX stubs as GCC wouldn't run with=
out<br>
such.<br>
<div class=3D"im"><br>
> My second question is to Louis is why you're rebuilding version<br=
>
> 2.04? =A02.04 doesn't work as well with DOS as 2.03. =A0There are =
some<br>
> definate bugs with it, at least with MS-DOS v7.10. =A0IIRC, 2.04 is<br=
>
> designed to work better in a Windows XP console ("dosbox") w=
indow,<br>
> not real-mode DOS.<br>
<br>
</div>2.04 (circa 2003) "mostly" works fine for everything I test=
ed. Sure,<br>
there are some rare bugs, but they were fixed in CVS (not that I<br>
really tried that). The only problem with 2.04 is that it wasn't<br>
as heavily tested in all environments as 2.03p2. Plus, there's been<br>
no release manager nor major interest since it was always "good<br>
enough" for the main developers. At least, that's what little I<br=
>
recall understanding about it. I don't have anything against<br>
2.03p2, but I'm not sure that's totally perfect either, for<br>
various minor reasons.<br>
<div class=3D"im"><br>
> Rugxulo, I know I need to get an email account and get on "DOS<br=
>
> ain't dead forums"...<br>
<br>
</div>No pressure! =A0:-) =A0I know you hate email, but perhaps GNU PG woul=
d<br>
help??<br>
<div class=3D"im"><br>
> But, until then, could you do me another<br>
> favor and let Japheth know I posted a patch for HIMEMX to<br>
> comp.os.msdos.programmer? =A0It supports multiple 001 E820h memory<br>
> blocks above 1MB. =A0If you recall, you posted a message or two there<=
br>
> for me previously discussing the issue.<br>
<br>
</div>Sure, but keep in mind that Japheth long ago disclaimed any hold<br>
over HimemX, so he's not really a maintainer (anymore, if ever).<br>
IIRC, he even refused the simple "jmp $+2" 386 patch. =A0:-(<br>
<br>
Though worst case, I'll just try to mirror your patch to iBiblio.<br>
<div class=3D"im"><br>
> If you do, thanks and sorry for the trouble...<br>
<br>
</div>No trouble, but my usefulness is limited. But I've gone ahead and=
<br>
posted there, so we'll see what he says.<br>
</blockquote></div><br></div>
--bcaec5015cf73bf78a04e006ec8f--
- Raw text -