Hi Ali,
My builds are also OK (Ubuntu and W7).
I would double-check the sha1sum of your libelf package and make sure it matches util/crossgcc/sum/libelf-0.8.13.tar.gz.cksum. To be honest, though, I suspect it may be correct since you've probably tried multiple times.
The other thought that comes to mind is there was a patch that went in near the end of March that added the capability of using multithreaded decompressors. You might try modifying the flags in crossgcc/buildgcc. This also seems unlikely, as it looks like "tar zxf tarballs/libelf-0.8.13.tar.gz" is used. I'm with Zoran; see if you can decompress manually. It looks like he suggested a different option style, too.
When was the last time you built the tools successfully?
Thanks, Marshall
On Mon, Aug 15, 2016 at 12:47 AM, Ali H. Fardan raiz@firemail.cc wrote:
Here is what you asked for,
Raiz
Tar version: tar (GNU tar) 1.29 Shell (/bin/sh): GNU bash, version 4.3.46(1)-release (x86_64-unknown-linux-gnu) Distro: Manjaro-OpenRC (rolling) (Linux manjaro 4.4.16-1-MANJARO #1 SMP PREEMPT Wed Jul 27 21:09:47 UTC 2016 x86_64 GNU/Linux)
- for P in '$PACKAGES'
- unpack_and_patch LIBELF
- package=LIBELF
++ eval echo '$LIBELF_ARCHIVE' +++ echo http://www.mr511.de/software/libelf-0.8.13.tar.gz
++ eval echo '$LIBELF_DIR' +++ echo libelf-0.8.13
- dir=libelf-0.8.13
- test -d libelf-0.8.13
++ basename http://www.mr511.de/software/libelf-0.8.13.tar.gz
- printf ' * libelf-0.8.13.tar.gz\n'
- libelf-0.8.13.tar.gz
- FLAGS=zxf
++ echo http://www.mr511.de/software/libelf-0.8.13.tar.gz ++ sed 's,.*.,,'
- suffix=gz
- '[' gz = gz ']'
- '[' -n '' ']'
- '[' gz = gz ']'
- FLAGS=zxf
++ basename http://www.mr511.de/software/libelf-0.8.13.tar.gz
- tar zxf tarballs/libelf-0.8.13.tar.gz
gzip: stdin: not in gzip format tar: Child returned status 1 tar: Error is not recoverable: exiting now
- for patch in 'patches/${dir}_*.patch'
- test -r 'patches/libelf-0.8.13_*.patch'
- continue
- touch libelf-0.8.13/.unpack_success
touch: cannot touch 'libelf-0.8.13/.unpack_success': No such file or directory
- exit 1
downloading it manually and putting it in the tarballs folder.
If that's not what's happening, it's probably something in your environment:
- What shell is being used? ls -al /bin/sh; /bin/sh --version
- What version of tar is getting run? tar --version
- If you're running a less widely used OS or Distro, what are you running?
Try running the buildgcc command directly with -x enabled and see what's actually getting run for the tar command: /bin/sh -x util/crossgcc/buildgcc
Martin
-- coreboot mailing list: coreboot@coreboot.org https://www.coreboot.org/mailman/listinfo/coreboot