It is now possible to use ssl support via dev-libs/libretls library.
-fno-stack-protector flag was removed from configure script in upstream
in version 2.4.0.0.
Upstream-commit: 540c946d8632 ("Don't put -fno-stack-protector in default CFLAGS")
Signed-off-by: Petr Vaněk <arkamar@atlas.cz>
Signed-off-by: Sam James <sam@gentoo.org>
-fno-stack-protector flag was removed from configure script in upstream
in version 2.3.4.0.
Upstream-commit: 5b063a4db3e6 ("Don't put -fno-stack-protector in default CFLAGS")
Signed-off-by: Petr Vaněk <arkamar@atlas.cz>
Signed-off-by: Sam James <sam@gentoo.org>
Bug #782409 affects only 2.2.0.1 and 2.3.0.0 versions because they are
not compatible with dev-libs/skalibs-2.7.0.0 and newer, where
skalibs/mininetstring.h was removed.
Closes: https://bugs.gentoo.org/782409
Signed-off-by: Petr Vaněk <arkamar@atlas.cz>
Signed-off-by: Sam James <sam@gentoo.org>
-fno-stack-protector flag was removed from configure script in upstream
in version 1.0.6.0.
Upstream-commit: 5cda6f5fdc8f ("Don't put -fno-stack-protector in default CFLAGS")
Signed-off-by: Petr Vaněk <arkamar@atlas.cz>
Signed-off-by: Sam James <sam@gentoo.org>
-fno-stack-protector flag was removed from configure script in upstream
in version 2.5.1.4.
Upstream-commit: c934e0b32812 ("Don't put -fno-stack-protector in default CFLAGS")
Signed-off-by: Petr Vaněk <arkamar@atlas.cz>
Signed-off-by: Sam James <sam@gentoo.org>
-fno-stack-protector flag was removed from configure script in upstream
in version 2.2.3.1.
Upstream-commit: 57f70ba69ee2 ("Don't put -fno-stack-protector in default CFLAGS")
Signed-off-by: Petr Vaněk <arkamar@atlas.cz>
Signed-off-by: Sam James <sam@gentoo.org>
-fno-stack-protector flag was removed from configure script in upstream
in version 0.5.2.1.
Upstream-commit: a592de252872 ("Don't put -fno-stack-protector in default CFLAGS")
Signed-off-by: Petr Vaněk <arkamar@atlas.cz>
Signed-off-by: Sam James <sam@gentoo.org>
-fno-stack-protector flag was removed from configure script in upstream
in version 2.10.0.0.
Upstream-commit: 21ae83d8e28c ("Don't put -fno-stack-protector in default CFLAGS")
Signed-off-by: Petr Vaněk <arkamar@atlas.cz>
Signed-off-by: Sam James <sam@gentoo.org>
-fno-stack-protector flag was removed from configure script in upstream
in version 2.7.0.0.
Upstream-commit: 3c3e63f2a72b ("Don't put -fno-stack-protector in default CFLAGS")
Signed-off-by: Petr Vaněk <arkamar@atlas.cz>
Signed-off-by: Sam James <sam@gentoo.org>
-fno-stack-protector flag was removed from configure script in upstream
in version 2.10.0.0.
Upstream-commit: e5c83dd7b233 (" Remove -fno-stack-protector from default CFLAGS")
Signed-off-by: Petr Vaněk <arkamar@atlas.cz>
Signed-off-by: Sam James <sam@gentoo.org>
This package uses JNA's Pointer.SIZE API, which has been removed since
JNA 5.0.0. A replacement of the API is Native.POINTER_SIZE, which is
present in both JNA 4.x and 5.x.
Since JNA 5.0.0, the default JNI library loading mechanism has been
changed, which would cause this package to crash upon launch, unless
system property 'jna.nosys' is set to 'false', which restores the 4.x
library loading behavior compatible with this package.
Closes: https://bugs.gentoo.org/830847
Signed-off-by: Yuan Liao <liaoyuan@gmail.com>
Closes: https://github.com/gentoo/gentoo/pull/23933
Signed-off-by: Sam James <sam@gentoo.org>
This adds a patch from the zlib-devel ML to fix a minor
build inconsistency leading to GNU tools usage in LLVM
configured builds.
The reason we're adding it directly here is zlib upstream
takes forever to release new versions and there's not much
activity for some time (last release was in Jan 2017).
Closes: https://bugs.gentoo.org/831628
Signed-off-by: Adrian Ratiu <adrian.ratiu@collabora.com>
Closes: https://github.com/gentoo/gentoo/pull/23888
Signed-off-by: Sam James <sam@gentoo.org>
In the install phase, there are certain libraries which are re-linked
using "/usr/lib64". This creates a problem when cross-compilation is
done.
Snippet from logs:
libtool: relink: aarch64-cros-linux-gnu-clang -shared -fPIC -DPIC
.libs/liburcu_la-urcu.o .libs/liburcu_la-urcu-pointer.o
.libs/liburcu_la-compat_arch.o .libs/liburcu_la-compat_futex.o
-L/build/lakitu-arm64/tmp/portage/dev-libs/userspace-rcu-0.13.0/image/usr/lib64
-L/usr/lib64 -lurcu-common -pthread -Os -march=armv8-a+crc
-mtune=cortex-a57 -g -Wl,-O2 -Wl,--as-needed -Wl,--gc-sections
-Wl,--icf=all -pthread -Wl,-soname -Wl,liburcu.so.8 -o
.libs/liburcu.so.8.0.0
Doing `eautoreconf` in `src_prepare` fixes the problem.
Signed-off-by: Vaibhav Rustagi <vaibhavrustagi@google.com>
Closes: https://github.com/gentoo/gentoo/pull/23973
Signed-off-by: Sam James <sam@gentoo.org>