From: jeremie.galarneau@gmail.com (Jérémie Galarneau)
Subject: [lttng-dev] lttng-tools backport request: Fix: error.h -> common/error.h
Date: Thu, 6 Oct 2016 08:34:58 -0400 [thread overview]
Message-ID: <CA+jJMxtxjCwmjHHnFxWnoJawG8t+cmQtm+HVQvfWt9sG=hsWQw@mail.gmail.com> (raw)
In-Reply-To: <90905ba7-d102-c9f3-6fb3-67eb630b6558@mentor.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1164 bytes --]
I have merged the patch in 2.8.
Thanks for reporting!
Jérémie
On Oct 3, 2016 4:43 PM, "Nathan Lynch" <Nathan_Lynch at mentor.com> wrote:
> On 10/03/2016 10:36 AM, Nathan Lynch wrote:
> > Can this be backported to the stable-2.8 branch?
> >
> > commit 6712db617fe9
> > Author: Michael Jeanson <mjeanson at efficios.com>
> > Date: Wed Jun 15 17:18:03 2016 -0400
> >
> > Fix: error.h -> common/error.h
> >
> > OE is carrying this patch for its lttng-tools 2.8 package in order to
> > build against musl libc:
> >
> > http://lists.openembedded.org/pipermail/openembedded-core/
> 2016-September/126851.html
> >
> > I haven't personally verified the problem or the patch, but it seems
> > like an obvious, low-risk fix?
>
> I've now verified that the patch is necessary for cross-compiling with a
> musl toolchain.
>
> _______________________________________________
> lttng-dev mailing list
> lttng-dev at lists.lttng.org
> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.lttng.org/pipermail/lttng-dev/attachments/20161006/15337957/attachment.html>
prev parent reply other threads:[~2016-10-06 12:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-03 15:36 Nathan Lynch
2016-10-03 20:42 ` Nathan Lynch
2016-10-06 12:34 ` Jérémie Galarneau [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='CA+jJMxtxjCwmjHHnFxWnoJawG8t+cmQtm+HVQvfWt9sG=hsWQw@mail.gmail.com' \
--to=jeremie.galarneau@gmail.com \
/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