From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v7 1/1] libcpprestsdk: new package
Date: Sun, 31 Dec 2017 17:23:25 +0100 [thread overview]
Message-ID: <20171231172325.6a0ef08f@windsurf> (raw)
In-Reply-To: <20171230231328.3299abdc@windsurf>
Hello,
On Sat, 30 Dec 2017 23:13:28 +0100, Thomas Petazzoni wrote:
> Interestingly, it is the same error I had when building opentracing-cpp
> with the same toolchain. Building with the Linaro ARM toolchain works
> fine however.
>
> Could you test this package with ./utils/test-pkg before submitting the
> next version ?
Since Jan Heylen had the same problem on opentracing-cpp, he
investigated it. It turns out that you need to make your package
"depends on !BR2_TOOLCHAIN_HAS_GCC_BUG_64735" to avoid a gcc bug.
Could you resubmit with this change ?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2017-12-31 16:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-30 19:16 [Buildroot] [PATCH v7 1/1] libcpprestsdk: new package Adam Duskett
2017-12-30 22:13 ` Thomas Petazzoni
2017-12-31 1:03 ` Adam Duskett
2017-12-31 16:23 ` 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=20171231172325.6a0ef08f@windsurf \
--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