From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] protobuf: apply patch to compile for PowerPC
Date: Wed, 10 Feb 2016 17:44:25 +0100 [thread overview]
Message-ID: <20160210174425.592ffaa5@free-electrons.com> (raw)
In-Reply-To: <2127002292.1917904.1455121926734.JavaMail.zimbra@datacom.ind.br>
Dear Carlos Santos,
On Wed, 10 Feb 2016 14:32:06 -0200 (BRST), Carlos Santos wrote:
> The problem is the same you found on mpd (commit 84533029c70a4dffb2cd2e4f05e3903fd1b8fcd9) in branch master. With the patch in configure.ac I get this:
>
> $ owerpc-e500v2-linux-gnuspe-ldd --root target/ target/usr/bin/protoc
> libprotobuf.so.9 => /usr/lib/libprotobuf.so.9 (0xdeadbeef)
> libatomic.so.1 => /lib/libatomic.so.1 (0xdeadbeef)
> libpthread.so.0 => /lib/libpthread.so.0 (0xdeadbeef)
> libc.so.6 => /lib/libc.so.6 (0xdeadbeef)
> ld.so.1 => /lib/ld.so.1 (0xdeadbeef)
> libz.so.1 => /usr/lib/libz.so.1 (0xdeadbeef)
> libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xdeadbeef)
> libm.so.6 => /lib/libm.so.6 (0xdeadbeef)
> libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xdeadbeef)
> libprotoc.so.9 => /usr/lib/libprotoc.so.9 (0xdeadbeef)
Yes, looks good.
> Without the patch protoc is not linked to libatomic.so.1.
Indeed.
And so, what's the problem ?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-02-10 16:44 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 13:08 [Buildroot] [PATCH 1/1] protobuf: apply patch to compile for PowerPC Carlos Santos
2016-02-04 23:06 ` Thomas Petazzoni
2016-02-05 11:04 ` Henrique Marks
2016-02-05 13:09 ` Thomas Petazzoni
2016-02-05 13:22 ` Henrique Marks
2016-02-05 13:37 ` Thomas Petazzoni
2016-02-07 21:19 ` Thomas Petazzoni
2016-02-10 15:25 ` Carlos Santos
2016-02-10 15:57 ` Thomas Petazzoni
2016-02-10 16:32 ` Carlos Santos
2016-02-10 16:44 ` Thomas Petazzoni [this message]
2016-02-10 16:50 ` Carlos Santos
2016-02-10 18:30 ` Carlos Santos
2016-02-10 20:13 ` Thomas Petazzoni
2016-02-11 15:14 ` Carlos Santos
2016-02-10 15:33 ` [Buildroot] [PATCH 1/1] protobuf: fix detection of __atomic_*() built-ins Carlos Santos
2016-02-10 15:50 ` Thomas Petazzoni
2016-02-10 18:42 ` Carlos Santos
2016-02-10 20:06 ` Arnout Vandecappelle
2016-02-10 20:00 ` Arnout Vandecappelle
2016-02-11 14:56 ` Carlos Santos
2016-02-11 15:23 ` Carlos Santos
2016-02-17 17:43 ` [Buildroot] [PATCH v2 0/1] " Carlos Santos
2016-02-17 17:43 ` [Buildroot] [PATCH v2 1/1] " Carlos Santos
2016-02-27 21:55 ` Arnout Vandecappelle
2016-03-20 22:43 ` Thomas Petazzoni
2016-02-17 18:33 ` [Buildroot] [PATCH v2 0/1] " Carlos Santos
2016-02-17 20:51 ` Thomas Petazzoni
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=20160210174425.592ffaa5@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