Applying libc-compat.h related patches to the kernel itself breaks the build.
It doesn't really make much sense to do that anyway because it is highly
unlikely that there will be any musl dpecific patch for the kernel itself.

This reverts commit d0201f400f.

In the parse-config-9 we map the linux-header and linux package to the same
directory which is 'linux' thus the patches in the linux-header subdir were
not applied.

Detected when cross-compiling

Origin: https://github.com/sabotage-linux/kernel-headers/blob/master/generic/include/linux/libc-compat.h

When cross-compiling following error appears at linking time, which strangely
doesn't when building "natively" within a chrooted environment.
------------------------------------------------------------------------------
/bin/ld: ssmtp.o: undefined reference to symbol 'X509_free'
/bin/ld: note: 'X509_free' is defined in DSO /usr/lib/libcrypto.so.1.0.0 so try adding it to the linker command line
/usr/lib/libcrypto.so.1.0.0: could not read symbols: Invalid operation
collect2: error: ld returned 1 exit status
------------------------------------------------------------------------------

Note:

Because the original procps project is pretty unmaintained a fork called
procps-ng was initiated by Debian, Redhat and Suse.
This update is replacing the sources with those provided by the procps-ng
project.

The vserver patch changes the type of the 'i_flags' field within 'struct inode'
from 'unsigned int' to 'unsigned short'.

This mimics the standard behavior of OpenSDE for normal package builds,
where .patch files found in the $confdir are unconditionally applied,
whereas .diff files are commonly added to the patch file list based on
some conditions defined in the package conf.

patch origin: sabotage linux

https://raw.githubusercontent.com/sabotage-linux/sabotage/8054eda9e3b5e58309e36d8d2223aba00a9480e6/KEEP/pciutils-pread.patch

7 years is enough for every version! :D

Note:

Currently this is a copy of the glibc config.cache because this was formerly
injected from the frameworks for all builds!

TODO: All the entries need to be checked on a native build!

When using this workaround the kernel is hanging at "Unpacking initramfs...".

Actually reverting 8a5fecedc6.