From: DATACOM - Edson Siqueira <edson.siqueira@datacom.ind.br>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] boost: add option to build boost_coroutine
Date: Tue, 03 Nov 2015 16:14:20 -0200 [thread overview]
Message-ID: <5638F97C.7060300@datacom.ind.br> (raw)
In-Reply-To: <20151103183541.000defd6@free-electrons.com>
Hello Thomas Petazzoni,
At the time of commit 611dfe6cb55ed72d7df3b7c102f4a723248a4037, this library
was new to boost and being built regardless of the config. The fix was to
always remove it from compilation to avoid problems with some compilers.
Now, with a proper option, it should be possible to enable it only when
the compiler supports the compilation of this library.
I've tested this patch using a ppc32 toolchain to build the library.
Thanks,
On 03-11-2015 15:35, Thomas Petazzoni wrote:
> Dear Edson Siqueira,
>
> On Tue, 3 Nov 2015 14:59:38 -0200, Edson Siqueira wrote:
>> It was disabled by default by commit 611dfe6cb55ed72d7df3b7c102f4a723248a4037
>> due to the upgrade to boost 1.54.0.
>>
>> Signed-off-by: Edson Siqueira <edson.siqueira@datacom.ind.br>
> Thanks for your contribution. However, you don't explain why you think
> that the problems that lead to commit
> 611dfe6cb55ed72d7df3b7c102f4a723248a4037 have now been fixed. Can you
> give more details ? Have you tested the configurations pointed by the
> 611dfe6cb55ed72d7df3b7c102f4a723248a4037 commit log and verified that
> they now build fine with the coroutine module enabled ?
>
> Thanks,
>
> Thomas
--
Edson Siqueira
DATACOM
Projetista de Software Embarcado - P&D
Rua da Gl?ria, 251 - 8 ? andar - Centro C?vico - Curitiba, PR
Fone: +55 41 3089-3670
edson.siqueira at datacom.ind.br
www.datacom.ind.br
next prev parent reply other threads:[~2015-11-03 18:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 16:59 [Buildroot] [PATCH 1/1] boost: add option to build boost_coroutine Edson Siqueira
2015-11-03 17:35 ` Thomas Petazzoni
2015-11-03 18:14 ` DATACOM - Edson Siqueira [this message]
2015-11-03 20:17 ` 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=5638F97C.7060300@datacom.ind.br \
--to=edson.siqueira@datacom.ind.br \
--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