From: Fabrice Fontaine <fontaine.fabrice@gmail.com>
To: buildroot@buildroot.org
Cc: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Subject: [Buildroot] [PATCH 1/1] package/libglvnd: needs __sync_*_4 intrinsics
Date: Thu, 13 Jan 2022 08:58:47 +0100 [thread overview]
Message-ID: <20220113075847.3267080-1-fontaine.fabrice@gmail.com> (raw)
Fix the following build failure raised since the addition of the package
in commit 0378e2e5d9ce9d5676975dfbff501360094fdc1a:
/tmp/instance-1/output-1/host/opt/ext-toolchain/bin/../lib/gcc/sparc-buildroot-linux-uclibc/10.3.0/../../../../sparc-buildroot-linux-uclibc/bin/ld: src/EGL/libEGL.so.1.1.0.p/libegl.c.o: in function `AtomicIncrement':
libegl.c:(.text+0x614): undefined reference to `__sync_add_and_fetch_4'
Fixes:
- http://autobuild.buildroot.org/results/a204953020a714057ec6690e63a3ad8ac621acd5
Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
---
package/libglvnd/Config.in | 2 ++
1 file changed, 2 insertions(+)
diff --git a/package/libglvnd/Config.in b/package/libglvnd/Config.in
index 2d99be8632..cd19fde582 100644
--- a/package/libglvnd/Config.in
+++ b/package/libglvnd/Config.in
@@ -1,5 +1,6 @@
config BR2_PACKAGE_LIBGLVND
bool "libglvnd"
+ depends on BR2_TOOLCHAIN_HAS_SYNC_4 # __sync_*_4 intrisics
depends on !BR2_STATIC_LIBS # dlfcn.h
help
The GL Vendor-Neutral Dispatch library
@@ -45,4 +46,5 @@ config BR2_PACKAGE_PROVIDES_LIBGLES
endif
comment "libglvnd needs a toolchain w/ dynamic library"
+ depends on BR2_TOOLCHAIN_HAS_SYNC_4
depends on BR2_STATIC_LIBS
--
2.34.1
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2022-01-13 8:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 7:58 Fabrice Fontaine [this message]
2022-01-13 17:52 ` [Buildroot] [PATCH 1/1] package/libglvnd: needs __sync_*_4 intrinsics Yann E. MORIN
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220113075847.3267080-1-fontaine.fabrice@gmail.com \
--to=fontaine.fabrice@gmail.com \
--cc=buildroot@buildroot.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.