From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/boost: boost-filesystem needs wchar
Date: Thu, 23 Jul 2015 08:08:37 +0200 [thread overview]
Message-ID: <1437631717.6881.4.camel@embedded.rocks> (raw)
In-Reply-To: <20150722085507.4f78d81f@free-electrons.com>
Dear Thomas,
On Mi, 2015-07-22 at 08:55 +0200, Thomas Petazzoni wrote:
> Dear J?rg Krause,
>
> On Fri, 17 Jul 2015 16:15:16 +0200, J?rg Krause wrote:
> > Also add reverse dependency for cc-tool.
> >
> > Fixes:
> > http://autobuild.buildroot.net/results/2c7/2c7783b7f3cc28d54d15a7f0
> > 17442c48244ffd8e/
> > http://autobuild.buildroot.net/results/2c7/2c7783b7f3cc28d54d15a7f0
> > 17442c48244ffd8e/
> > http://autobuild.buildroot.net/results/0dd/0dd3ef96bbd034a41d908cda
> > a6552b27fda78132/
> > http://autobuild.buildroot.net/results/34b/34b55b2cd83fd5d87af4a9c1
> > 5d05094b16ef3960/
> >
> > and many more
> >
> > Signed-off-by: J?rg Krause <joerg.krause@embedded.rocks>
>
> Apparently, this isn't sufficient to fix all problems:
>
> http://autobuild.buildroot.net/results/49f/49f5c0521fc90fbd4673ad23
> 3ff679be007d2953/build-end.log
>
>
> Maybe we should make the entire boost package depends on wchar and be
> done with it?
I will check a build with all boost modules enabled. If there are too
many depending on wchar, let's say more then four or five, we can do it
this way.
Best regards
J?rg Krause
next prev parent reply other threads:[~2015-07-23 6:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-17 14:15 [Buildroot] [PATCH 1/1] package/boost: boost-filesystem needs wchar Jörg Krause
2015-07-18 12:13 ` Thomas Petazzoni
2015-07-22 6:55 ` Thomas Petazzoni
2015-07-23 6:08 ` Jörg Krause [this message]
2015-07-23 7:18 ` Jörg Krause
2015-07-23 7:31 ` 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=1437631717.6881.4.camel@embedded.rocks \
--to=joerg.krause@embedded.rocks \
--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