Date: Wed, 13 Nov 2002 00:33:40 -0500 From: 2boxers <2boxers AT comcast DOT net> Subject: Re: linux-x-djgpp revised howto To: djgpp-workers AT delorie DOT com Message-id: <001101c28ad6$393711e0$021ca8c0@helm> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 X-Mailer: Microsoft Outlook Express 5.50.4807.1700 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal References: <019501c28abe$1f6139c0$021ca8c0 AT helm> <200211130256 DOT gAD2uZ104685 AT envy DOT delorie DOT com> Reply-To: djgpp-workers AT delorie DOT com corrections have been made. I have it up as a text file for the moment. http://users.erols.com/praccompsol/djgpp/linux-x-djgpp_REV-2.txt Please let me know what you think. > Er, the howtos are plain ASCII, not HTML... > And for some reason you are defaulting to a text size that is way > smaller than my default. Don't you trust me to pick my own font size? I didn't realize there was a font size specification. It is true ascii now. > DJGPP's mini-faq has nothing to do with the versions of software > installed on your Linux machine. removed > You shouldn't refer to one particular djgpp mirror. Go through > www.simtel.net and hunt down the file; point to the URL for the last > page before you pick a mirror site. Or (probably best) just say > "v2/djcrx203.zip from your local djgpp ftp site". fixed in the offline HTML version pending the discovery of your font size ;) > The environment variable setting instructions are specific to bash. > They won't work in sh or csh (just a note would be fine). sh/bash/ksh specific commands are now listed and so are csh specific commands > The canonical djgpp target name is i586-pc-msdosdjgpp, not i686. It's > probably not a problem any more, but at one point it was. We use i586 > in our docs, probably should continue that to be consistent. fixed > The symbolic links should probably be relative, not absolute, like > ln -s libstdc++.a $prefix/$target/lib/libstdcxx.a fixed > The /usr/bin/djgcc files should probably go by default in > /usr/local/bin fixed > You don't need to restub your binary to get it to run under DOS. Just > put cwsdpmi.exe somewhere in your PATH. The rest is automatic. Correct, it simply mentions that you can do this if you choose to.