Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-05-10
Date: Tue, 13 May 2014 23:51:26 +0200	[thread overview]
Message-ID: <20140513235126.212289d9@free-electrons.com> (raw)
In-Reply-To: <20140511094535.GF4096@tarshish>

Dear Baruch Siach,

On Sun, 11 May 2014 12:45:35 +0300, Baruch Siach wrote:

> On Sun, May 11, 2014 at 08:30:09AM +0200, Thomas Petazzoni wrote:
> >        arm |                   ltrace-0.7.3 | NOK | http://autobuild.buildroot.net/results/eefa8efbe6e6a6b203c02c2977d29be9c77846cb/
> 
> Build log says:
> 
> checking for backtrace in -lunwind... no
> configure: error: Couldn't find or use libunwind.
> 
> But I can't reproduce it here. Thomas, can you look into config.log?

To reproduce the problem, you needed to have: libatomic_ops, libunwind,
and ltrace selected, and an architecture like ARMv4 or ARMv5. The
problem is that on ARMv4 and ARMv5, libatomic_ops doesn't provide real
atomic operations. But libunwind did not use the libatomic_ops stuff
properly, and therefore libatomic_ops was not providing emulated atomic
operations for those architectures. Later on, when ltrace tried to link
against libunwind, there were unresolved symbols due to this problem.

I've sent a patch to the Buildroot mailing list to fix this. You're
Cc'ed on the patch.

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      reply	other threads:[~2014-05-13 21:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-11  6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-05-10 Thomas Petazzoni
2014-05-11  9:45 ` Baruch Siach
2014-05-13 21:51   ` Thomas Petazzoni [this message]

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=20140513235126.212289d9@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