Mail Archives: djgpp/1997/05/18/11:05:51
On Fri, 16 May 1997, Robert S. Peterson wrote:
> way. Caused some files with repetitive long names to be over
> written and lost (ie cpp.info-1 became cpp.inf and was
> overwritten by cpp.info-2, cpp.info-3, etc). Looking in FAQ
> 22.14 "Long Filenames Don't Work" it talks about Win95, but not
> for DOS/DJGPP. How do I make sure that LFNs remain and are not
> truncated? Do the LFNs actually exist even though I can't see
> them (with DIR)?
You can't have LFN on DOS/Windows 3.x, but you need not worry: DOS
transparently truncates the long filenames to 8+3 limits, so when a
program (e.g., Make) needs to find a file with a long filename, it
will happily settle for its truncated form.
> Also FAQ says to use DJTAR to open ".tar.gz" archives,
You need indeed to use DJTAR, the FAQ mentions it for a good reason:
I'm not aware of any other free program that can unzip and untar
.tar.gz files in one pass, and will never allow several files to
overwrite one another due to clashes of filenames (it will prompt you
to supply different names).
> but what to do when the download renames the file (ie
> to gcc-2_7_.gz)?
Well, DJTAR doesn't care about the filename, why should you? Just say
like so:
djtar -x gcc-2_7_.gz
(or rename it to gcc-272.tgz, if you care about the name). There's
nothing magic in the name of the file.
> I have found another program UNTAR.EXE but it
> also seems to truncate and hung on my machine (I think?) What's
> a newbie to do?
A newbie should follow instructions religiously. If the FAQ says
``use DJTAR'', use DJTAR, not Winzip, not UNTAR.
> 3) Maybe this is all the long way around because I haven't even
> started to configure, patch, or compile. Does HP48xGCC.exe exist
> for DJGPP or can the Win95 version be converted?
I don't know if there is a DJGPP port (anybody?). As for converting
the Windows 95 version, that depends on the toolchain (compiler, Make,
etc.) with which it was compiled. I'd guess they used Cygnus Win32
tools, which means you probably can't convert it easily.
> 4) I did try to compile DJGPP gcc-272s.zip (not realizing I
> needed the Gnu source) and I hit some errors: [Error 1] and
> [Error -1]. Where can I find a listing of error descriptions?
> (for future use- no doubt)
These are probably error messages from Make (you should generally tell
this explicitly, so I won't need to guess). If so, then Error -1
usually means that Make didn't find a program it needed to run. You
should examine the last line printed by Make before this message and
figure out which program is that. Most probably, you didn't install
some optional tool (like rm or mv) which the build process needs.
Error 1 means that a program that Make runs returned exit code of 1.
This is in general bad news (programs return non-zero code when
something's wrong), so Make usually stops when it gets such code,
unless the Makefile tells it to ignore the error (in which case it
will say "Error 1 (ignored)").
Did you run the CONFIGURE.BAT batch file there before running Make?
If not, it won't work.
> 5) Is there a general prescription for how to adapt Gnu
> programs to DJGPP?
No, and it's far from being a newbie stuff. I won't even know where
to begin explaining this to somebody who doesn't know *a lot* about
Unix tools and how GNU packages are configured and built. You need to
know about Make, Unix-style shell and GNU configure scripts, for
starters. You also need to know about frequently-used Unix tools such
as `mv', `rm', `sed', `grep' and a few others. If you really need to
do this, I would suggest downloading one of the GNU packages uploaded
lately to DJGPP archives (in the v2gnu directory), such as `enscript'
(ens150s.zip), Fileutils (fil316s.zip) or Groff (gro110s.zip), read
the DJGPP-specific README file there and study the batch files that
configure and build these packages. You will also need to install
quite a few of additional tools (the READMEs list them).
Another way to accomplish your goal would be to begin with the DJGPP
GCC sources (gcc2721s.zip). This should be simpler for building GCC
as is, but I'm afraid you might run into trouble when you try to add
files from the original GCC source distribution, which you need to
build a cross-compiler, because some files you add might have
filenaming problems and belong to the parts of the GCC Makefiles and
configure scripts that weren't converted to something that can run on
MS-DOS.
> go32-v2:
> DPMI memory available: 527 Kb
Too low amount of memory. If that was from DOS box, fire up PIF
Editor, open the file DOSPRMPT.PIF and change the EMS and XMS values
to -1 (see the DJGPP FAQ for more about this).
If this is from plain DOS (no Windows), read section 3.9 of the FAQ
for advice on how to configure your system for DJGPP.
Either way, you need to have at least 2MB of free DPMI memory before
you can run complicated Makefiles safely; otherwise it will run *very*
slowly and some of them will just plain crash.
- Raw text -