This fixes the issue that arch specific headers will not appear in the flist
file when cross-compiling, and thus being missing in the resulting binary
package.
Resulting binaries like libstdc++.so will end up having an rpath with an
absolute path to the build sandbox set in the elf headers.
This issue was discovered when trying to run a cross-compiled lftp which
was cross-compiled against musl libc and segfaulted when being executed.
Removing the explicit rpath seems to solve the runtime issue because lftp
is not segfaulting anymore and works as expected.
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.
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.
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.
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.
Christian Wiese