We don't have latex2man in HOSTTOOLs so documentaion is never built but this
dependency does cause problems on older releases like morty, pre-HOSTTOOLS.
Document the configuration explicitly in master.
(From OE-Core rev: 95a5ab819df324e7ec8068bb3575e55cad022e3a)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This recipe explictly sets -DAO_USE_PTHREAD_DEFS on ARM, but with libunwind 1.2
this causes the linker to fail:
hidden symbol `__sync_synchronize' in libgcc.a(linux-atomic.o) is referenced by DSO
Removing these defines lets configure do the right thing and build libunwind.
(From OE-Core rev: f2efadab8b1ab1c50584a39908673e1a6717f753)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Switch to using tarballs as git is unreliable (not responding right now).
LICENSE file is gone; COPYING has an additional line on top with
copyright attribution, the license text that follows has not changed.
(From OE-Core rev: fd55e8a463f42e4012aeedacb2d168f41232bf25)
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This effectively reverts the commit
3dd233ac0c80393824100c54bb525236f8290fd2
gold now emits errors on copy relocs against
protected symbols what ld.bfd did in past, however
it seems its too conservative.
This does not fix the case for folks who
use gold as default linker, however it
does make bintuls 2.27 work with default
configuration of OE
(From OE-Core rev: 0092a076adb11cac411c86389af84bb96169730f)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
libunwind makery inserts -nostdlib during linking
which fails the build on musl when security flags are enabled
since it remove ssp from linking, so add them explicitly
to SECURITY_LDFLAGS
disable tests for musl targets, tests use obsolete
posix APIs e.g. getcontext
patchout x86_local_resume() on x86, gets a working
linunwind on x86, it seems that it wont work even
in glibc case but lets leave it as it is for glibc
and apply the patch only for musl
(From OE-Core rev: c8ac9d483f6e1cfca82dad8cf3e0745935e96214)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
gcc driver is fixed to pass correct options to linker to do secure plt
linking when enabled. however this option --secure-plt is not supported
by gold linker which is now passed by default from gcc driver. Hence
the build fails when using gold. Therefore when we use gold then we do
not use secure plt
(From OE-Core rev: 1fcb1b91fae0646baf243d686fc6a52b97a53005)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
- This recipe is useful for more than just pulseaudio, so move it to
recipes-support.
- Rename to the correct upstream name, which corresponds to the library name.
Keep a PROVIDES of libatomics-ops for compatibility.
(From OE-Core rev: 5014de67fa6da1672626e3ec92fc51430fca3262)
(From OE-Core rev: 5a14d4f981c2c12c274fade518d23706dca5889b)
Signed-off-by: Christopher Larson <kergoth@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
- Depend on libatomics-ops unconditionally for all archs, as it's used by more
than just arm, and currently the configure script auto-detects and enables
its use based on the existence of its header, resulting in non-deterministic
builds.
- Drop the ldflags bits which link against libatomic_ops, because libunwind
doesn't actually link against it, nor does it need to, as it currently uses
all inline functions from the header file.
(From OE-Core rev: 83bb89502e2f05b8b78b14532ad96abc400ab264)
(From OE-Core rev: e43a47eb695050d04809ff54af14066acba6ec27)
Signed-off-by: Christopher Larson <kergoth@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The gold doesn't work for mips or mips64:
configure:3867: checking whether the C compiler works
configure:3889: mips-poky-linux-gcc -meb -mabi=32 -mhard-float -march=mips32r2 --sysroot=/buildarea/lyang1/test_uni/tmp/sysroots/qemumips -O2 -pipe -g -feliminate-unused-debug-types -Wl,-O1 -Wl,--as-needed -fuse-ld=gold conftest.c >&5
collect2: fatal error: cannot find 'ld'
(From OE-Core rev: 3c6746748a845b5156f81fe7a01caa58ee29e938)
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
At least the following boards have build errors without using gold:
qemux86, qemux86-64, qemuarm, qemuaarch64, qemuppc.
The error is:
ld: copy reloc against protected `_Uaarch64_local_addr_space' is invalid
ld: failed to set dynamic section sizes: Bad value
ld: copy reloc against protected `_Uaarch64_local_addr_space' is invalid
ld: failed to set dynamic section sizes: Bad value
| collect2: error: ld returned 1 exit status
So use gold for all archs to fix the problem.
(From OE-Core rev: 3dd233ac0c80393824100c54bb525236f8290fd2)
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Referred to RP's fix for x86 and x86-64:
34d517a5626ce2465f776367349bd9e66bf8ed1f
libunwind: Build with gold to avoid build failures
Fixed:
aarch64-poky-linux/4.9.2/ld: copy reloc against protected `_Uaarch64_local_addr_space' is invalid
aarch64-poky-linux/4.9.2/ld: failed to set dynamic section sizes: Bad value
aarch64-poky-linux/4.9.2/ld: copy reloc against protected `_Uaarch64_local_addr_space' is invalid
aarch64-poky-linux/4.9.2/ld: failed to set dynamic section sizes: Bad value
| collect2: error: ld returned 1 exit status
(From OE-Core rev: 31d84f67f74b31b479409cfa446b14ac67bb3707)
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The library fails to build with binutils 2.25 and standard ld. This
issue is fixed in gcc 5 with no plans to backport to gcc 4. Easiest
workaround for now is to use gold as the linker for the library
since gold does not have the issue. The bug is x86 only.
(From OE-Core rev: 34d517a5626ce2465f776367349bd9e66bf8ed1f)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
