From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/4] package/cmake: revert the bump to 3.7
Date: Sun, 26 Feb 2017 22:34:50 +0100 [thread overview]
Message-ID: <1488144890.10882.6.camel@embedded.rocks> (raw)
In-Reply-To: <20170226164509.GC4043@free.fr>
Hi Ben, hi Yann,
On Sun, 2017-02-26 at 17:45 +0100, Yann E. MORIN wrote:
> Ben, All,
>
> On 2017-02-26 16:32 +0000, Ben Boeckel spake thusly:
> > On Sat, 25 Feb, 2017 at 18:51:29 GMT, Yann E. MORIN wrote:
> > > cmake 3.7 causes serious regressions in some cmake-based
> > > packages,
> > > related to how RPATH is handled.
> > >
> > > See for example:
> > >
> > > ? - domoticz : http://autobuild.buildroot.org/results/fd0/fd0ba54
> > > c7abf973691b39a0ca1bb4e07d749593a/
> > > ? - freerdp??: http://autobuild.buildroot.org/results/5d4/5d429d0
> > > e288754a541ee5d8be515454c5fccd28b/
> > > ? - libcec???: http://autobuild.buildroot.org/results/3f3/3f3593b
> > > ab7734dd274faf5b5690895e9424cbb89/
> > >
> > > (and many others)
> > >
> > > All causes the link to be attemped against host libraries, which
> > > is
> > > definitely not appropriate...
> > >
> > > Properly fixing this so close to the release is problematic; we'd
> > > risk
> > > having to hunt down packages one by one.
> >
> > Could you please submit a report to CMake's issue tracker?
> > Regressions
> > are taken seriously and it'd be nice to have this fixed for 3.8.0
> > (which
> > is currently in its RC cycle).
> > ????https://gitlab.kitware.com/cmake/cmake/issues
>
> Yes, that would be awesome.
>
> However, I don't know how to caracterise the bug with a minimal
> reproducer.
> Nor am I able to explain exactly what happens in details...
>
> Maybe J?rg (which has already made an extensive analyis of the
> problem)
> or you (if you are knowledgeable about cmake) could do it? ;-)
In fact, I already submitted a report [1] to the CMake mailing list
some weeks ago. I was not sure, if this is a bug or a lack of
understanding at that moment.
Ray Donnelly replied in that thread he has a PR [2] in the loop "[..]
that asks the linker (via the compiler) what its implicit
search directories are instead.?It is the right way to do it IMHO, but
I need to find time to finish it unfortunately."
I did not checked the PR, yet.
[1] http://public.kitware.com/pipermail/cmake/2017-February/064970.html
[2] https://gitlab.kitware.com/mingwandroid/cmake/commit/b937ff949d8fda
ab7d8b812d503f67f8cef69532
J?rg
next prev parent reply other threads:[~2017-02-26 21:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-25 18:51 [Buildroot] [PATCH 0/4] package/cmake: revert the bump to 3.7 Yann E. MORIN
2017-02-25 18:51 ` [Buildroot] [PATCH 1/4] Revert "cmake: bump version to 3.7.2" Yann E. MORIN
2017-02-25 18:51 ` [Buildroot] [PATCH 2/4] Revert "cmake: adjust dependencies added for libuv" Yann E. MORIN
2017-02-25 18:51 ` [Buildroot] [PATCH 3/4] Revert "cmake: bump version to 3.7.1" Yann E. MORIN
2017-02-25 18:51 ` [Buildroot] [PATCH 4/4] Revert "cmake: bump version to 3.7.0" Yann E. MORIN
2017-02-25 20:44 ` [Buildroot] [PATCH 0/4] package/cmake: revert the bump to 3.7 Baruch Siach
2017-02-25 22:10 ` Yann E. MORIN
2017-02-26 4:23 ` Baruch Siach
2017-02-26 8:44 ` Jörg Krause
2017-02-26 8:59 ` Yann E. MORIN
2017-02-26 9:12 ` Jörg Krause
2017-02-26 16:32 ` Ben Boeckel
2017-02-26 16:45 ` Yann E. MORIN
2017-02-26 20:29 ` Ben Boeckel
2017-02-26 21:34 ` Jörg Krause [this message]
2017-02-26 21:41 ` Peter Korsgaard
2017-02-26 22:40 ` 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=1488144890.10882.6.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