Alexey Brodkin 9cf2457878 libaio: link against libgcc and libc to avoid unresolved symbols ... For some weird reason, the libaio build system passes -nostdlib -nostartfiles, which causes libgcc to not be linked in, even if it's needed. Due to this, on some architectures, with specific optimization features, the build fails with unresolved symbols, as gcc emits code that uses functions implemented in libgcc. The fix proposed by Debian developers is to simply drop -nostdlib -nostartfiles. Fixes build failures of blktrace, lvm2 and the like users of libaio. A couple of examples below: blktrace: http://autobuild.buildroot.net/results/5528ab59f1939a7eff7e85318f3b36283019cc50/ lvm2: http://autobuild.buildroot.net/results/a5dfc87f94b97135e5cc84f6a876114891ed9dd9/ And since we solve the problem in libaio sources there's no need to mess with compilation flags in Buildroot, thus partially revert commit ce6536ae50 ("libaio: work-around for PowerPC issue"). Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>		2018-10-08 21:29:35 +02:00
..
0001-src-Makefile-add-ENABLE_SHARED-boolean-to-allow-stat.patch
0002-Makefile-add-missing-DESTDIR-variable-use.patch
0003-Link-against-libgcc-to-avoid-unresolved-symbols.patch	libaio: link against libgcc and libc to avoid unresolved symbols	2018-10-08 21:29:35 +02:00
Config.in
libaio.hash
libaio.mk	libaio: link against libgcc and libc to avoid unresolved symbols	2018-10-08 21:29:35 +02:00