From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] package/libv4l: link with libatomic when needed
Date: Wed, 30 Oct 2019 11:30:40 +0100 [thread overview]
Message-ID: <20191030113040.474a31f9@windsurf> (raw)
In-Reply-To: <20191030065303.22948-2-bernd.kuhls@t-online.de>
On Wed, 30 Oct 2019 07:53:03 +0100
Bernd Kuhls <bernd.kuhls@t-online.de> wrote:
> On some architectures, atomic operations are provided by the libatomic
> library from gcc. Linking with libatomic is therefore necessary,
> otherwise the build fails with:
>
> /home/buildroot/autobuild/run/instance-1/output-1/host/opt/ext-toolchain/bin/../lib/gcc/sparc-buildroot-linux-uclibc/7.4.0/../../../../sparc-buildroot-linux-uclibc/bin/ld:
> qv4l2-qv4l2.o: undefined reference to symbol '__atomic_fetch_add_4@@LIBATOMIC_1.0'
>
> This is often for example the case on sparcv8 32 bit.
>
> Fixes:
> http://autobuild.buildroot.net/results/089/08952dbf89bf3c49da7697943441cee411940420/
The LIBV4L_AUTORECONF = YES that was kept in
d0f3c9de49bfe3f8ac6e75a706540eefcc1afc07 was intended to fix this
libatomic linking issue, so I'm a bit confused.
Could you discuss this with Peter Seiderer (in Cc) ?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-10-30 10:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-30 6:53 [Buildroot] [PATCH 1/2] package/libv4l: fix musl build Bernd Kuhls
2019-10-30 6:53 ` [Buildroot] [PATCH 2/2] package/libv4l: link with libatomic when needed Bernd Kuhls
2019-10-30 10:30 ` Thomas Petazzoni [this message]
2019-10-30 22:26 ` Peter Seiderer
2019-11-20 14:46 ` Thomas Preston
2019-11-20 19:44 ` Peter Seiderer
2019-11-21 11:33 ` Thomas Preston
2019-11-21 16:46 ` Thomas Preston
2019-12-08 13:35 ` [Buildroot] [PATCH 1/2] package/libv4l: fix musl build Thomas Petazzoni
2019-12-22 19:35 ` Peter Korsgaard
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=20191030113040.474a31f9@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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.