Hello,
Linux 7.1+ has removed support for amateur radio protocols, including ROSE, as per this upstream commit. As a result, the <linux/rose.h> header, which is required by net-tools's rose.c, no longer exists when the Linux API headers are updated to version 7.1. And thus net-tools fails to compile successfully.
Because config.in defaults ROSE support to enabled, it has to be manually disabled in order for the build to succeed, by a command such as the following:
sed -e 's/HAVE_AFROSE y/HAVE_AFROSE n/' -e 's/HAVE_HWROSE y/HAVE_HWROSE n/' -i config.in
I am writing this issue just to let you know about this in case you weren't aware (plus to help anyone it may concern who encounters this build failure - I doubt most of the mainstream distributions will encounter it anytime soon, because they usually don't upgrade their kernel API headers to the latest versions even if they update the kernel itself).
It may be worth documenting the upstream removal at minimum, if (justifiably) not fully defaulting the feature to disabled in config.in, assuming there is no way to re-implement support for the protocol manually (which, if the kernel itself no longer supports it, I'd guess is unlikely to be possible).
Regards.
Hello,
Linux 7.1+ has removed support for amateur radio protocols, including ROSE, as per this upstream commit. As a result, the
<linux/rose.h>header, which is required by net-tools'srose.c, no longer exists when the Linux API headers are updated to version 7.1. And thus net-tools fails to compile successfully.Because
config.indefaults ROSE support to enabled, it has to be manually disabled in order for the build to succeed, by a command such as the following:I am writing this issue just to let you know about this in case you weren't aware (plus to help anyone it may concern who encounters this build failure - I doubt most of the mainstream distributions will encounter it anytime soon, because they usually don't upgrade their kernel API headers to the latest versions even if they update the kernel itself).
It may be worth documenting the upstream removal at minimum, if (justifiably) not fully defaulting the feature to disabled in
config.in, assuming there is no way to re-implement support for the protocol manually (which, if the kernel itself no longer supports it, I'd guess is unlikely to be possible).Regards.