--- Comment #5 from htl10 at users dot sourceforge dot net 2008-08-26
18:19 ---
(In reply to comment #4)
> From that link:
> GNU tar version 1.14 (or later)
> Necessary (only on some platforms) to untar the source code. Many systems' tar
> programs will also work, only try GNU tar if yo
--- Comment #4 from pinskia at gcc dot gnu dot org 2008-08-26 18:10 ---
> Can somebody update the platform-specific notes please:
> http://gcc.gnu.org/install/specific.html ?
> Still, the POSIX tar vs GNU tar issue could be spelt out a bit :-(.
> (spent a few days on this...)
It is sp
--- Comment #3 from htl10 at users dot sourceforge dot net 2008-08-26
18:06 ---
Yes, mid-air collision - I realised the problem as soon as I looked at my own
bug report and looked at the directory again.
Still, the POSIX tar vs GNU tar issue could be spelt out a bit :-(.
(spent a few
--- Comment #2 from htl10 at users dot sourceforge dot net 2008-08-26
18:04 ---
Oh dear, sorry about the noise - Looking at my own error message about the
missing files and where they are, I found that it is the vendor tar which is
broken - it truncates file path names to 100 characters
--- Comment #1 from pinskia at gcc dot gnu dot org 2008-08-26 17:45 ---
>Some of the headers are not created?
What tar did you use? Because the filename for this file goes past the limit
of a POSIX tar, GNU tar is required to untar the GCC now.
--
pinskia at gcc dot gnu dot org cha
