Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Fix build of lttng-libust
Date: Mon, 30 Oct 2017 20:40:54 +0100	[thread overview]
Message-ID: <20171030204054.723cdc99@windsurf> (raw)
In-Reply-To: <20171030163121.939-1-norbert.lange@andritz.com>

Hello,

On Mon, 30 Oct 2017 17:31:21 +0100, Norbert Lange wrote:
> The build of doc/examples/cmake-multiple-shared-libraries
> does fail as a dependend library is missing.
> This issue is not specific to builroot and should ideally
> be fixed upstream (Issue: https://bugs.lttng.org/issues/1132)
> 
> The fix is done without any indepth knowledge of the CMake
> mechanisms, but seems to work correctly
> 
> Signed-off-by: Norbert Lange <norbert.lange@andritz.com>

Which specific build problem are you fixing? Is this a problem that has
been found by http://autobuild.buildroot.org? If that's the case, we
like to include a reference to such an autobuilder failure in the
commit log.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-10-30 19:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-30 16:31 [Buildroot] [PATCH 1/1] Fix build of lttng-libust Norbert Lange
2017-10-30 19:40 ` Thomas Petazzoni [this message]
2017-10-31 10:20   ` Norbert Lange
2017-11-05 16:13     ` Arnout Vandecappelle
2017-11-05 16:31       ` Yann E. MORIN
2017-11-05 19:55         ` Philippe Proulx
2017-11-05 21:10           ` Yann E. MORIN
2017-11-05 21:20             ` Yann E. MORIN
2017-11-05 20:36       ` Norbert Lange
2017-11-05 22:02         ` Arnout Vandecappelle
2017-11-06 21:06           ` Philippe Proulx
2017-11-06 21:12             ` Thomas Petazzoni
2017-11-06 21:41               ` Philippe Proulx

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=20171030204054.723cdc99@windsurf \
    --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