From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] tinycbor: new package
Date: Sat, 30 Jul 2016 16:43:01 +0200 [thread overview]
Message-ID: <20160730164301.329de917@free-electrons.com> (raw)
In-Reply-To: <1469435859-25918-1-git-send-email-fabrice.fontaine@orange.com>
Hello,
On Mon, 25 Jul 2016 10:37:39 +0200, Fabrice Fontaine wrote:
> Concise Binary Object Representation (CBOR) Library
>
> Signed-off-by: Fabrice Fontaine <fabrice.fontaine@orange.com>
> ---
> package/Config.in | 1 +
> package/tinycbor/Config.in | 20 ++++++++++++++++++++
> package/tinycbor/tinycbor.hash | 2 ++
> package/tinycbor/tinycbor.mk | 38 ++++++++++++++++++++++++++++++++++++++
> 4 files changed, 61 insertions(+)
> create mode 100644 package/tinycbor/Config.in
> create mode 100644 package/tinycbor/tinycbor.hash
> create mode 100644 package/tinycbor/tinycbor.mk
This package is causing two types of build failures:
* On Blackfin only:
http://autobuild.buildroot.net/?reason=tinycbor-v0.3.1&arch=bfin
The Blackfin external toolchain uses gcc 4.3, which is pretty old.
The error occurs on unnamed unions, maybe there's a problem with
that. But
https://gcc.gnu.org/onlinedocs/gcc-4.3.2/gcc/Unnamed-Fields.html
seems to indicate it was already supported in gcc 4.3. More
investigation is needed.
* On other architectures, a problem occurs when
output/target/usr/lib/libtinycbor.a is created as a directory, for
some reason:
http://autobuild.buildroot.net/results/760/7605c301f460398c2435f6b73d6d07c7d1022e8c/build-end.log
Could you look into those issues?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-07-30 14:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 8:37 [Buildroot] [PATCH 1/1] tinycbor: new package Fabrice Fontaine
2016-07-25 21:35 ` Thomas Petazzoni
2016-07-30 14:43 ` Thomas Petazzoni [this message]
2016-07-30 19:52 ` Thomas Petazzoni
2016-07-30 20:03 ` Fabrice Fontaine
2016-07-30 21:24 ` Thomas Petazzoni
2016-07-31 6:56 ` Fabrice Fontaine
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=20160730164301.329de917@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