Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] dependencies/cmake: blacklist cmake 3.7
Date: Mon, 27 Feb 2017 18:12:24 +0100	[thread overview]
Message-ID: <1488215544.31837.9.camel@embedded.rocks> (raw)
In-Reply-To: <1488148967-8055-1-git-send-email-yann.morin.1998@free.fr>

Hi all,

On Sun, 2017-02-26 at 23:42 +0100, Yann E. MORIN wrote:
> cmake-3.7 has a bug in how it handles rpath, linking with libraries
> from
> the host.
> 
> Until we completely understand the issue, just blacklist cmake-3.7.
> 
> The issue has been reported upstream:
> ????http://public.kitware.com/pipermail/cmake/2017-February/064970.ht
> ml

Brad King from Kitware replied today [1]. In short, Brad does not think
there anything wrong about handling the rpath and supposes to load a
custom platform cmake file instead of the Linux one.

[1] http://public.kitware.com/pipermail/cmake/2017-February/065063.html

J?rg

  parent reply	other threads:[~2017-02-27 17:12 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-26 22:42 [Buildroot] [PATCH] dependencies/cmake: blacklist cmake 3.7 Yann E. MORIN
2017-02-27  4:43 ` Baruch Siach
2017-02-27 15:51   ` Yann E. MORIN
2017-02-27 17:12 ` Jörg Krause [this message]
2017-02-27 17:25   ` Yann E. MORIN
2017-02-27 17:31     ` Baruch Siach
2017-02-27 17:41       ` Yann E. MORIN
2017-02-27 18:30     ` Yann E. MORIN
2017-02-27 18:35       ` Ben Boeckel
2017-02-27 20:59         ` Yann E. MORIN
2017-02-27 21:13           ` Jörg Krause
2017-02-27 20:53       ` Yann E. MORIN
2017-02-27 21:02         ` Jörg Krause
2017-02-27 20:04     ` Jörg Krause
2017-02-27 20:08       ` Ben Boeckel
2017-02-27 20:24         ` Jörg Krause
2017-02-27 20:40           ` Ben Boeckel
2017-02-27 20:56         ` Jörg Krause
2017-02-28  8:51 ` Peter Korsgaard
2017-02-28 16:16   ` Yann E. MORIN
2017-02-28 16:38     ` Peter Korsgaard

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=1488215544.31837.9.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