FC 6: gunzip: stdin: invalid compressed data--format violated
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
FC 6: gunzip: stdin: invalid compressed data--format violated
Hello, I've installed Fedora Core 6, and am a new user. I want to program my AX4510 development board for our senior project, but I'm unable to install the toolchain. The toolchain was copied from a CD to my HD /home/Justin/CD/uClinux/Toolchain.I did this:
sh arm-elf-tools-20030314.sh
and got this:
'tail: cannot open `+43' for reading: No such file or directory'
following ipodlinux.org/Toolchain I changed line 39 to:
I don’t know about your tool chain problem, but gunzip is telling you that the stuff you pulled off the end of the ${SCRIPT} file was not compressed information.
Perhaps, instead of tail -n+${SKIP} ${SCRIPT} | gunzip | tar xvf - you should use tail -n +${SKIP} ${SCRIPT} | gunzip | tar xvf -
Or, if what was implied by the first error you reported is correct, tail -n +43 ${SCRIPT} | gunzip | tar xvf - to just skip the first 43 lines of $SCRIPT.
Just to see what’s going on, I downloaded the tool chain to /tmp and did this:
Sorry, ark is the KDE archive GUI. Just a moment, let me check GNOME.
O.K., under GNOME, go to Accessories->Archive Manager and open the tar file.
Or just use the tar command to unpack the file. See man tar for details, but (as you saw) the command used in the file is tar xvf, so, as root, entering # tar xvf /usr/tmp/arm-elf-tools-20030314.tar should do the trick.
Last edited by PTrenholme; 03-13-2007 at 11:19 AM.
Thankyou PTrenholme, I recopied the arm-elf-tools-20030314.sh from the Embest CD to /usr/tmp, and followed your instructions.
It worked perfectly, and I "verbosely extracted" the file. Thankyou PTrenholme, this forum is awesome.
For anyone interested this was for an AX4510 Evaluation board, my OS is Fedora Core 6, and I was trying to install a toolchain (User Guide page 16) called arm-elf-tools-20030314.sh
I'm having the same issues above, except PTrenholme's resolution isn't working for either arm-elf-tools-20040427.sh or arm-elf-tools-20030314.sh.
This is on a fresh Fedora 2.6.18-1.2789.fc6 install.
Here is what I'm seeing when trying to both run the scripts and run PTrenholme's steps:
******************
[root@alex_fedora PACT]# sh arm-elf-tools-20040427.sh
./usr/local/arm-elf/
./usr/local/arm-elf/bin/
./usr/local/arm-elf/bin/nm
gunzip: stdin: invalid compressed data--format violated
tar: Read 6144 bytes from -
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
***************************
[root@alex_fedora PACT]# sh arm-elf-tools-20030314.sh
incomplete literal tree
gzip: stdin: invalid compressed data--format violated
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
****************************
I'm at a real loss. Been searching all day long for some answers with no luck. I have a deadline approaching and this is a serious hold up.
I'm a bit of a Linux novice, so if anyone can shed some light, I'd be very appreciative!
Well, the error message seems to be telling you that your sh file is too short. Have you tried downloading it again? Can you verify the file byte count?
Perhaps there's another download site you could try.
Well, the error message seems to be telling you that your sh file is too short. Have you tried downloading it again? Can you verify the file byte count?
Perhaps there's another download site you could try.
I've tried downloading it from at least 3 sources with the same results. I've been right clicking->save as. Is this the correct method?
OK, I downloaded another copy from uclinux and I got 18406845 bytes (more than you report) with a sha1sum of e837e617e1fa983c885161554428e1cbaa237014. What download method are you using? you could try an FTP from ftp://166.111.68.183/pub/linux/ since, sometimes, an FTP download works better.
OK, I downloaded another copy from uclinux and I got 18406845 bytes (more than you report) with a sha1sum of e837e617e1fa983c885161554428e1cbaa237014. What download method are you using? you could try an FTP from ftp://166.111.68.183/pub/linux/ since, sometimes, an FTP download works better.
My earlier stated size was for the arm-elf-tools-20040427.sh. I get the same file size and sha1sum for a just downloaded arm-elf-tools-20030314.sh
Where would I find the arm-elf-tools file in the ftp directory you provided? I couldn't find it.
OK, I downloaded arm-elf-tool-20040427.sh from the Samsung site and got 17589174 bytes (sill different from your report) with a sha1sum of 85ca541c8ef916a0ffddd895962980a8de524af7
OK, at this point you've got the tar file extracted, so just do (as "root") a tar xvf arm-elf-tools.tar and you should be "home free." (You can delete the toc file, that was just to confirm that the tar file was good.)
The problem with the script is that it is using a nonstandard tail format. According to the Posix standard (I think, but have not verified) tail -n +43 - is required whilst the script uses tail +43 -, omitting the required -n argument.
If you want the script to work, you'd need to change the tail +${SKIP} ${SCRIPT} | gunzip | tar xvf - to read tail -n +${SKIP} ${SCRIPT} | gunzip | tar xvf -. (And you could omit the | gunzip too) since (as you saw when you did the tar "list" command to generate the toc file, tar (on your system, at least) automatically unzipped the extracted file.)
Last edited by PTrenholme; 03-23-2007 at 08:23 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.