summaryrefslogtreecommitdiff
path: root/dev-python/bitarray
diff options
context:
space:
mode:
authorDongsu Park <dpark@linux.microsoft.com>2022-06-14 12:48:58 +0200
committerSam James <sam@gentoo.org>2022-06-15 23:05:18 +0100
commit4302d08ccac50d123e66d3524f01243bcddf9601 (patch)
tree7a1339125bb66e31266c12b1d6b6f80a9fedd79d /dev-python/bitarray
parente6dda8fd393edeaff05dddcd34020a13a6c833ba (diff)
downloadgentoo-4302d08ccac50d123e66d3524f01243bcddf9601.tar.gz
gentoo-4302d08ccac50d123e66d3524f01243bcddf9601.tar.bz2
gentoo-4302d08ccac50d123e66d3524f01243bcddf9601.zip
sys-devel/gdb: fix cross build issues with configuring gmp libs
As gdb 11 or newer requires gmp libs as dependency, a cross build of gdb 11.2 started to fail when its configure scripts try to detect if gmp exists. The failure occurs mainly because the build still passes '-L/usr/lib64` to LDFLAGS. Let's say, for example, host toolchains outside of sysroot have amd64 libs, while the target inside of sysroot should have arm64 libs. However, configure scripts of gdb 11.2 still try to find its libs outside of sysroot, /usr/lib64, although it should find its libs inside of sysroot, e.g. /build/arm64/usr/lib64. To fix the cross build issues, pass --with-sysroot as well as --libdir, correctly with ${ESYSROOT}. As a side note, for some reason, upstream gdb configure scripts are not able to correctly make use of its gmp-specific options like --with-gmp or --with-gmp-lib. Passing those options does not bring anything. Also configure must have both --with-sysroot and --libdir, to make the build work. Signed-off-by: Dongsu Park <dpark@linux.microsoft.com> Closes: https://github.com/gentoo/gentoo/pull/25896 Signed-off-by: Sam James <sam@gentoo.org>
Diffstat (limited to 'dev-python/bitarray')
0 files changed, 0 insertions, 0 deletions