Mail Archives: djgpp/2011/11/29/03:15:33
Hi,
On Nov 28, 5:30 pm, Rugxulo <rugx DOT DOT DOT AT gmail DOT com> wrote:
>
> On Nov 28, 4:23 pm, tm <thomas DOT mer DOT DOT DOT AT gmx DOT at> wrote:
>
> > I installed DJGPP under Windows XP, to test it.
> > I use the original make.exe from DJGPP/bin to execute mk_djgpp.mak
> > (with C:\DJGPP\bin\make -f mk_djgpp.mak). When I use your patch I
> > get error messages.
And yet your makefile doesn't work for me (aunts' WinXP cpu). It still
seems to need backslash escapes for both single and double quotes as
well as editing to avoid "Ambiguous redirect error" for
GET_CC_VERSION.
Also, it's kinda weird. It uses about 350-420 MB of RAM for "hi
chk_all" due to GCC 4.6.2 being used (by the compiled compiler?). Also
trying to trim that via using -O1 didn't work too well (GCC
regression???), seemed to freeze the compiler at one point. But with -
O2 the tests do pass (compiled compiler), so I guess it really is a
rare CWSDPMI r7 quirk (under native FreeDOS on my own machine).
Presumably due to page tables being in low RAM with nowhere to swap
(or at least r7 refuses to swap here despite ample FAT32 space).
Actually, I tried GCC 4.1.2 (in FreeDOS) but got other weird errors
(division by zero), for some reason. Fun fun fun (confusing).
> > - Does the comment /* backslash (ASCII) */ make problems?
> > I added this comment to show the meaning of the value 92.
>
> It was being expanded into file names under Bash.
And yet it still seems to do it when not using Bash. I don't know why.
Perhaps your Make is old 3.79.1? I'm using /beta/mak381b.zip here.
Also I think you must have Fil41b, Txt20b, Shl2011b (aka, CoreUtils)
installed else it has some other error in the "make depend" stage,
didn't check too closely.
> > - As I already mentioned \' and \" do cause problems under XP.
>
> I don't know, it's easy to get confused, esp. because Make, Bash, and
> COMMAND.COM are all fighting over who controls stdout.
I honestly can't remember when / if COMMAND.COM is called for DOS
programs when on XP.
> To capture (almost) all output messages, I just now did this (under
> DOSEMU):
>
> redir -eo hi chk_all | tee blah.txt
So slow as it has to wait for finished output, ugh. I really wish
there was an easy way to enable compilation messages. Just sitting
there "in the dark" isn't very enlightening. (Besides, it scrolls past
the screen too fast, and "No swap space!" isn't redirectable anyways.)
> > Probably this was caused by the "No swap space!" error you
> > mentioned. To prove this you can call
>
> > hi comp chkbig
>
> > manually. The file tmp_chkbig.cerrs or tmp_chkbig.lerrs may
> > contain helpful information. Please tell me, when the Seed7
> > compiler (comp.sd7) itself crashes.
I'm not sure *.cerrs is being created. You may still have blindly
assumed "2>" works everywhere. But let me reiterate that "hi chkbig"
and "hi chkset" both work fine. Honestly, all this fuss may be (only)
over the compiled compiler, which I don't really "need", do I? An
interpreter is good enough. ;-)
> > I really want to improve "mk_djgpp.mak", such that it works for you.
> > But I think it should also work for DJGPP under Windows (that way I
> > can test it also). Please help me, to reach that goal.
Well, in theory, you could install FreeDOS 1.1 test #3 (from iBiblio)
in VirtualBox. However, I definitely am not expecting or even
requesting that. I know that's probably tedious.
P.S. Does your makefile depend on both "seed7/bin/hi" and "seed7/bin/
hi.exe" existing? They're the same exact file but wasting space with
duplication. Feel free to directly "-o hi.exe" (instead of "-o hi") to
avoid that.
- Raw text -