Re: untarring gcc-2.95.2-2 (howto use md5 ?)

[Charles Wilson <cwilson at ece dot gatech dot edu>]

Mark -
  this error is because /libiberty (the directory) is created as a link
to ../../libiberty or something like that. Remove the libiberty link,
and 'mkdir libiberty' instead. Then, 'tar xvzf gcc-2.95.2-2/libiberty/*'

  This isn't technically a packaging error, because the src tarball is
built to be unpackaged as part of a larger 'src' directory including
binutils and cygwin/winsup, which all use a shared libiberty directory.

Chris, should a note to this effect go in the FAQ into a gcc-2.95.2
CYGWIN-README?

--Chuck


Mark Van De Vyver wrote:
> 
> Hi,
> I've had trouble untarring gcc-2.95.2-2-src.tar.gz (13,077,613 bytes)
> the type of message I get is:
> tar: gcc-2.95.2-2/libiberty/xstrerror.c: Could not create file: No such file
> or directory
> 
> Things went fine for gcc-2.95.2 tho after applying Mumit's patch and the
> pgcc patch (without errors) the make failed (configure went ok) so I thought
> I'd try and build a vanilla gcc before asking what went wrong there...
> So pulled the latest sources down from aarnet.edu.au now tar zxf ... fails
> as a 'check' I tried opening up the gz file with winzip and sure enough it
> complained about the libiberty directory.
> 
> The only thing I can think of is that the mirror is bad? but I'm not sure
> how to use md5 to check (which I'm assuming is the purposes of the md5.sum
> files).  Is there any receipe for using md5?  Found nought in quick search
> of the User guide web pages or archives.
> 
> Note I've built the autoconf, perl and automake files (I think) without
> error
> 
> Any help appreciated
> 
> Mark Van De Vyver
> 
> http://www.bigfoot.com/~mvdv
> Mailto:mvdv@bigfoot.com
> 
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com