From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] ola: Add patch to fix linking issue
Date: Mon, 10 Aug 2015 14:44:03 +0200 [thread overview]
Message-ID: <20150810144403.08c28fb4@free-electrons.com> (raw)
In-Reply-To: <CAFXXi0mu73=5UC6=n60uNZd=eUb16ns6vtxMH756MGuTDRhvFg@mail.gmail.com>
Dear Simon Marchi,
On Sun, 9 Aug 2015 23:11:03 -0400, Simon Marchi wrote:
> On 8 August 2015 at 06:44, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
> > Could you report the problem to the upstream ola project and see what
> > they say? Also, they have a 0.9.7 release, maybe you want to try it?
>
> I discussed it a bit on their IRC channel, it seems like the right fix
> will be to move the implementations to the .cpp files.
>
> I filed a bug: https://github.com/OpenLightingProject/ola/issues/880
Shouldn't we simply remove -fvisibility-inlines-hidden ?
> The 0.9.7 release does not change anything about that problem, but we
> could still bump the version. I am preparing a patch to cleanup the
> plugin management of the package, if it hasn't been bump by the time I
> send my patch, I'll do it then.
Sure, but that's going to be material for after 2015.08. What I was
looking for right now for 2015.08 is a fix for the build issue.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-08-10 12:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 4:19 [Buildroot] [PATCH] ola: Add patch to fix linking issue Simon Marchi
2015-08-05 7:58 ` Nicolas Cavallari
2015-08-05 14:54 ` Simon Marchi
2015-08-08 10:44 ` Thomas Petazzoni
2015-08-10 3:11 ` Simon Marchi
2015-08-10 12:44 ` Thomas Petazzoni [this message]
2015-08-10 17:45 ` Simon Marchi
2015-08-10 19:09 ` 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=20150810144403.08c28fb4@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