Mail Archives: djgpp/1996/07/15/12:44:03
Reply to message 8680180 from MSCHULTER AT MAC on 07/11/96 3:08PM
I'm glad you like it! The rest of us do as well. :)
>As far as the "57K for hello, world" issue, I assumed correctly that a
>sophisticated 32-bit compiler using DPMI might require a bit of overhead.
>It might be good just to let a beginner know that this is a normal result.
>I understand that the next FAQ will do this.
Yes, in fact it does. I don't know if it's propagated to SimTel yet, but
the new FAQ (version 2.01) is downloadable right now from DJ's web site.
The question was being asked so often in fact, that I think Eli and DJ
must have gotten nauseous just thinking about it (I know I did.) :)
>A couple of small glitches. Using pkunzip -d, I got an overwrite query
>because both djcrx200.zip and gcc272b.zip unzip identical versions of libgcc.a
>to identical paths. Here pkunzip -d -o -n, as recommended in djtut2_1.zip,
>avoided the problem.
Erm... I believe that the readme.1st file instructs you to use '-o' when you
unzip. The reason for duplication is because some packages are
optional, and thus may need to have the same things in them.
BTW, from other conversations on the newsgroup, I have been led to
believe that you djcrx200.zip is ONLY needed when you are building
a Unix-to-DOS cross-compiler. You should not install it if you are running
DJGPP _from_ DOS.
>Also, I was unable to find any documentation on the tests included in
>djtst200.zip, although this could be my oversight. Running either batch
>file in \djgpp\tests results in "Bad command or file name." I notice that
>mkexe.bat includes a command path ending with posix\bin\stubify -- and
>neither DOS nor I can find such a path (nor does it seem to be in the
>manifest for djtst200). Here a small bit of documentation for a rank newcomer
>might be helpful.
Hmm - not all of the test files are debugged, and you are right that there is
no
documentation whatsoever. They ought to be pretty self-explanatory, though!
A question - did you download mak373b.zip? This contains the GNU Make
utility, which can be used to compile the test programs. Ideally, you should
only need to go into any of the test directories and type 'make <program>.exe'
to automatically compile the sample prog you want.
John
- Raw text -