From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2017-02-20
Date: Thu, 23 Feb 2017 09:17:59 +0100 [thread overview]
Message-ID: <20170223091759.3b1cd434@free-electrons.com> (raw)
In-Reply-To: <20170222213900.4ba95a1f@gmx.net>
Hello,
On Wed, 22 Feb 2017 21:39:00 +0100, Peter Seiderer wrote:
> On Tue, 21 Feb 2017 08:29:02 +0100 (CET), Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:
>
> > sparc | libv4l-1.12.2 | NOK | http://autobuild.buildroot.net/results/3f13042565df20087e007949f653942c0462e334
>
>
> From build-end.log:
>
> CXXLD qv4l2
>
> qv4l2-qv4l2.o: In function `QtPrivate::RefCount::deref()':
> qv4l2.cpp:(.text._ZN9QtPrivate8RefCount5derefEv[_ZN9QtPrivate8RefCount5derefEv]+0x24): undefined reference to `__sync_fetch_and_add_4'
> qv4l2-qv4l2.o: In function `QString::QString(QString const&)':
> qv4l2.cpp:(.text._ZN7QStringC2ERKS_[_ZN7QStringC5ERKS_]+0x54): undefined reference to `__sync_fetch_and_add_4'
> qv4l2-vbi-tab.o: In function `QtPrivate::RefCount::ref()':
> vbi-tab.cpp:(.text._ZN9QtPrivate8RefCount3refEv[_ZN9QtPrivate8RefCount3refEv]+0x24): undefined reference to `__sync_fetch_and_add_4'
This normally indicates that a dependency on BR2_TOOLCHAIN_HAS_SYNC_4
is missing.
> This can be fixed by adding the following two lines to package/libv4l/libv4l.mk:
>
> LIBV4L_CONF_ENV += CXXFLAGS="$(TARGET_CXXFLAGS) -std=gnu++0x"
> LIBV4L_CONF_ENV += LDFLAGS="$(TARGET_LDFLAGS) -latomic"
Hum, so using gnu++0x forces to use __atomic built-ins instead of
__sync built-ins ?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-02-23 8:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 7:29 [Buildroot] [autobuild.buildroot.net] Build results for 2017-02-20 Thomas Petazzoni
2017-02-21 21:42 ` Peter Seiderer
2017-02-21 21:48 ` Thomas Petazzoni
2017-02-21 21:51 ` Romain Naour
2017-02-21 22:01 ` Peter Seiderer
2017-02-21 22:12 ` Thomas Petazzoni
2017-02-22 20:39 ` Peter Seiderer
2017-02-23 8:17 ` Thomas Petazzoni [this message]
2017-02-23 16:57 ` Peter Seiderer
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=20170223091759.3b1cd434@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox