folks,

anyone knows that what does that happenned ?
I wanna install arm-elf-tools-20030314.sh for skyeye to test my virtual arm board. i googled for some time,and i saw that some guy had the similar problem with me ,his error is '+368",but mine is '+43',and i typed the command he offered,nothing changed,anything worked the same as before.

my system :
ubuntu 8.04L

linux kernel 2.6.24-19-generic

errors:
tail : cannot open `+43' for reading : No such file or directory

gzip:stdin: not in gizp format
tar: This does not look like a tar archive
tar: Error exit delayed from previous errors


anyone could help me ?
thank you advanced!

Please post the exact commands giving error, so we can see what's going wrong.

You are attempting to install 'arm-elf-tools-20030314.sh', which is a shell script (based by it's suffix), so it's rather the installer tool, and not the tool itself.

The error feedback is propably accurate when stating that some tarball file is not the expected gzip format. Some web services do a lot of magic to hide the real tarballs and prevent other sites of pointing to those packages directly - it is possible that you downloaded an HTML file (containing some redirection info to the real tarball) instead of the needed package. If you open such a fake tarball and it starts with an html tag, then you know what the problem is.

The point is: make sure that your downloaded files are really what they are supposed to be.

linux

well,command ? both
$ sudo sh arm-elf-tool-20030314.sh

and
$ su && sh arm-elf-tool-20030314.sh

even
$./arm-elf-tool-20030314.sh

does not work,the same error like above....

well,yes,I am sure that what i download is a tarball,and that is really a bothersome error.and i think the error comes to me is not the tar or gzip like the errors,but the errors of "tail: could not ...." . for that the first step is like "tail" or any others i do not know .

what if the error really is "tail..." ,what could i do ?

hehe! thank you , your advice did bring me help.....

Shouldn't command be Also,are you in the right directory?

This error comes out when you use the obsolete option for tail
the latest POSIX standard interprets it as the name of a file. In this case you have to use the correct option
However, since you're running a binary file, it is not possible to edit it to change commands. But you can change the POSIX standard to match the one assumed by the installer. Just set the environment variable _POSIX2_VERSION as in
and the trick is done.

colucix:
thank you so much,your are right.
problem solved with this "export _POSIX2_VERSION=199209"
hehe~~

and also thank "alan_ri",thanks for your help..
and thank "gergely89" once again! thanks for you tring to help me....

thank all of you once again.

Hi there everyone

I have exactly the same problem. I'm trying to install the m68k-elf-gcc compiler and linker tools for Motorola Coldfire microprocessors. I always get that error (cannot open <<+43>>). I've tried to set the environment variable _POSIX2_VERSION to 199209, but it still doesn't work. I paste the errors I got:

ismael@ismael-desktop:~$ echo $_POSIX2_VERSION

ismael@ismael-desktop:~$ sudo sh m68k-elf-tools-20030314.sh
[sudo] password for ismael:
tail: no se puede abrir «+43» para lectura: No existe el fichero ó directorio

gzip: stdin: not in gzip format
tar: Esto no parece un archivo tar
tar: Salida con error demorada desde errores anteriores
ismael@ismael-desktop:~$ export _POSIX2_VERSION=199209
ismael@ismael-desktop:~$ sudo sh m68k-elf-tools-20030314.sh
tail: no se puede abrir «+43» para lectura: No existe el fichero ó directorio

gzip: stdin: not in gzip format
tar: Esto no parece un archivo tar
tar: Salida con error demorada desde errores anteriores


I'm sorry for the messages being in spanish. Anyway, I believe the problems a clear. What I try to do here is the following:
1. See if the _POSIX2_VERSION variable is previously already defined in my system. As you see, it is not.
2. I try to execute the file (with sudo for being root, as I use Ubuntu). In this situation, I got the error.
3. I change the variable to 199209, as recommended.
4. Now, with the new created environment variable and its value, I try the same and I got exactly the same error.

By the way: I run Ubuntu on a VMWare virtual machine. I don't believe that should be a problem, anyway.

Any suggestion?

Thank you in advance.