Mail Archives: djgpp/1998/08/31/03:44:38
On Sun, 30 Aug 1998, Ralph Proctor wrote:
> This is to both Andris and Martin------
>
> At 02:28 PM 8/30/98 GMT, you wrote:
> >Andris Pavenis (pavenis AT lanet DOT lv) wrote:
> >: One hint for poeple who sets TMPDIR to ramdrive. Try to unpack
> >: large enough .tar.gz or .tgz archive with GNU tar, for example:
> >:
> >: tar xzvf egcs-19980824.tar.gz
> >:
> >: and You'll see that simple setting TMPDIR to ramdrive breaks GNU
> >: tar. A simplest solution is adding additional lines
> >
> >I haven't noticed this.
>
> I have not either.
>
> >Isn't this what happens if your drive fills up? Wouln't this happen if
> >your TMPDIR only can hold less than necessary regardless whether it's
> >on a RAMDISK or not?
> >
> >I think the answer is yes to those two quetsions.
> >
> >
> >Homlboe, Symphony No. 6,
> >
> > MartinS
> Andris--
>
> I have detarred and uncompressed a lot of stuff with my configuration and
> have had no problem once I got the right sequence. What I mean is my only
> problem has been with me and not with the temporary directory setup. So, at
> least for now, I have to agree with Martin that the temp directory seems to
> be no problem with tar at least with what I have done.
>
How big archives did You uncompress?
I had ramdrive with size 4Mb, but size of development snapshot of
egcs-1.1 is more than 11Mb in archived form and I was unable to unpack it
when TMPDIR were set to ramdrive. There were no problem to unpack
libg++ sources where archive size were about 750K.
TAR works ok with small .tar.gz archives when ramdrive with such size
is being used. The problem is only with big archives.
Therefore I suggested to modify DJGPP.ENV to tell TAR not to use ramdrive.
However I'm afraid there are problems also with BASH when using pipes:
some_cmd1 | some_cmd2
perhaps will fail if output of some_cmd1 will not fit in drive specified
with $TMPDIR.
Andris
- Raw text -