From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2017-02-22
Date: Thu, 23 Feb 2017 21:20:30 +0100 [thread overview]
Message-ID: <20170223212030.2a6a10af@free-electrons.com> (raw)
In-Reply-To: <20170223200631.GB3910@free.fr>
Hello,
On Thu, 23 Feb 2017 21:06:31 +0100, Yann E. MORIN wrote:
> And now I seem to remember that we already questioned that some time in
> the past...
Yes, I even asked on the pkg-config mailing list how we are supposed to
handle such a situation, and they didn't had a very clear answer.
But I guess we need to go ahead and tweak the DirectFB .pc files and
add -lstdc++ in Libs.private. It's the most logical thing to do IMO.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-02-23 20:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 7:28 [Buildroot] [autobuild.buildroot.net] Build results for 2017-02-22 Thomas Petazzoni
2017-02-23 17:16 ` Yann E. MORIN
2017-02-23 17:48 ` Thomas Petazzoni
2017-02-23 20:06 ` Yann E. MORIN
2017-02-23 20:20 ` Thomas Petazzoni [this message]
2017-02-23 20:28 ` Yann E. MORIN
2017-02-23 20:21 ` Yann E. MORIN
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=20170223212030.2a6a10af@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