Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build fails because Linux Headers cannot be fetched #128

Open
hertrste opened this issue Jul 27, 2021 · 4 comments
Open

Build fails because Linux Headers cannot be fetched #128

hertrste opened this issue Jul 27, 2021 · 4 comments

Comments

@hertrste
Copy link

The make build currently fails because the LINUX_HEADERS_SITE = http://ftp.barfooze.de/pub/sabotage/tarballs/ to download the linux headers tarball is not reachable.

See following log:

Connecting to ftp.barfooze.de (ftp.barfooze.de)|5.9.157.210|:80... failed: Connection timed out.
Retrying.
--2021-07-27 07:38:19--  (try:18)  http://ftp.barfooze.de/pub/sabotage/tarballs//linux-headers-4.19.88.tar.xz
Connecting to ftp.barfooze.de (ftp.barfooze.de)|5.9.157.210|:80... failed: Connection timed out.
Retrying.
--2021-07-27 07:40:38--  (try:19)  http://ftp.barfooze.de/pub/sabotage/tarballs//linux-headers-4.19.88.tar.xz
@mathieu-aubin
Copy link

mathieu-aubin commented Jul 27, 2021

Works from here, is it still current? Try mirrors listed on https://github.com/sabotage-linux/kernel-headers

@hertrste
Copy link
Author

Yes, the servers are back up.

I found an old issue suggesting to use the full kernel tarball instead of downloading only the headers. This would allow to have kernel.org as a server instead of http://ftp.barfooze.de which might increase reliability of the whole build process.

If this option isn't feasible due to reasons consider this issue resolved.

rofl0r added a commit to rofl0r/musl-cross-make that referenced this issue Jul 27, 2021
unlike kernel.org, the site hosting linux-header tarball doesn't have
100% uptime.

fixes richfelker#128
@rofl0r
Copy link
Contributor

rofl0r commented Jul 27, 2021

using the full kernel tarball has the following disadvantages:

  • 100MB+ download (which is an issue if your behind old-school dsl or mobile plan) and extraction (time-consuming and space-wasting)
  • upstream kernel tarball isn't patched for use with musl, so there are a number of cases where kernel and musl header definitions clash

to address this, i added a commit mentioning a mirror URL to my pr #126

@richfelker
Copy link
Owner

It's intended that the upstream headers be usable with the patches applied by mcm (if any). If there are problems with that, they should be both reported upstream (kernel) and patched (in mcm patch set) for existing supported versions.

Personally I prefer using the headers only package, but as there have been multiple problems users have hit, I'm kinda leaning towards making upstream kernel package the default again. Or maybe even turning off kernel headers by default, but that might upset users who expect busybox to compile out of the box.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants