| Summary: | Linux-Headers extracting failure | ||
|---|---|---|---|
| Product: | buildroot | Reporter: | Melanie <melanie> |
| Component: | Other | Assignee: | unassigned |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | CC: | buildroot |
| Priority: | P5 | ||
| Version: | 2019.11.1 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Host: | Target: | ||
| Build: | |||
The extract command for e.g. RaspberryPi looks like the following: gzip -d -c <custom_path>/dl/linux/linux-64d0a9870ac14d5eb5253f67d984ae348eec1393.tar.gz | <custom_path>/host/bin/tar --strip-components=1 -C <custom_path>/build/linux-headers-custom -xf - Maybe try to re-name your tarball a little bit more meaningful.e.g. /home/user/pi/my/dl/linux/tarball.tar or (after compression) /home/user/pi/my/dl/linux/tarball.tar.gz We use the tarball filename extension to decide how to uncompress it, so if it doesn't have any extension, we don't know what to do with it. As Peter explained, it should have a .tar, .tar.gz, .tar.xz, tar.bz2, etc. extension depending on the compression scheme being used. |
Buildroot fails with the following error message: >>> linux-headers custom Extracting /home/user/pi/my/dl/linux/tarball | tar --strip-components=1 -C /home/user/pi/my/output/build/linux-headers-custom -xf - /bin/sh: /home/user/pi/my/dl/linux/tarball: Permission denied tar: This does not look like a tar archive tar: Exiting with failure status due to previous errors make[1]: *** [package/pkg-generic.mk:172: /home/user/pi/my/output/build/linux-headers-custom/.stamp_extracted] Error 2 make: *** [Makefile:84: _all] Error 2 The failure is caused by this command-line: /home/user/pi/my/dl/linux/tarball | tar --strip-components=1 -C /home/user/pi/my/output/build/linux-headers-custom -xf - To fix this issue, the following command works for me: tar --strip-components=1 -C /home/user/pi/my/output/build/linux-headers-custom -xf /home/user/pi/my/dl/linux/tarball