From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/5] core/pkg-cmake: provide our own platform description
Date: Tue, 28 Feb 2017 21:41:53 +0100 [thread overview]
Message-ID: <1488314513.5877.3.camel@embedded.rocks> (raw)
In-Reply-To: <f25e9ff7873418c0b323528d6a9c2482c752cd31.1488305206.git.yann.morin.1998@free.fr>
Hi Yann,
On Tue, 2017-02-28 at 19:07 +0100, Yann E. MORIN wrote:
> The handling of RPATH in cmake-3.7 has changed drastically, causing a
> slew of build failures dues to libraries from the host being pulled
> in:
>
> ? - domoticz : http://autobuild.buildroot.org/results/fd0/fd0ba54c7ab
> f973691b39a0ca1bb4e07d749593a/
> ? - freerdp??: http://autobuild.buildroot.org/results/5d4/5d429d0e288
> 754a541ee5d8be515454c5fccd28b/
> ? - libcec???: http://autobuild.buildroot.org/results/3f3/3f3593bab77
> 34dd274faf5b5690895e9424cbb89/
> ? - and so on...
>
> The bug was reported upstream [0], which dismissed it altogether [1]
> as
> being expected behaviour, quoting:
>
> ????I don't think there is anything wrong with that change on its
> own.
> ????It merely exposed some existing behavior in a new case.
>
> Instead, upstream suggested in that same message that a platform
> definition be used instead, quoting:
>
> ????If a toolchain file specifies CMAKE_SYSTEM_NAME such that a
> custom
> ????`Platform/MySystem.cmake` file is loaded then the latter can set
> ????them as needed for the target platform.
Upstream has opened an issue [1] about this and is already working on a
fix [2] for version 3.7 and 3.8. It fixes the behavior of how
FIND_LIBRARY_USE_LIB32_PATHS handle symlinks.?As 'lib32' is just just a
symlink to 'lib' in Buildroot, 'find_library()' will skip 'lib32' as a
runtime search path and as a consequence 'lib32' will not be used as
rpath anymore.
> So here we are doing so:
>
> ? - we add a new platfom definitions that inherits from the Linux
> one,
> ????then overrides the problematic settings;
>
> ? - we change our toolchain file to use that platform instead;
>
> ? - we tell cmake where to find additional modules, so that it can
> find
> ????our custom platform file.
As the issue might be fixed at some point, do we want to keep the
custom platform file?
> This has been tested to work in the following conditions:
>
> ?- pre-installed host cmake, versions 3.5.1 (Ubuntu 16.04) and 3.7.2
> ???(manually built)
>
> ? - internal cmake, versions 3.6.3 (the current version as of this
> ????patch) and 3.7.2 (with the followup patches).
>
> Thanks to J?rg, Ben and Baruch for the help investigating the issue.
> Special thanks to J?rg for handling the discussion with upstream and
> pointing to the relevant messages! :-)
You are welcome!
[1] https://gitlab.kitware.com/cmake/cmake/issues/16682
[2] https://gitlab.kitware.com/cmake/cmake/merge_requests/534
J?rg
next prev parent reply other threads:[~2017-02-28 20:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 18:07 [Buildroot] [PATCH 0/5] package/cmake: re-introduce cmake-3.7 Yann E. MORIN
2017-02-28 18:07 ` [Buildroot] [PATCH 1/5] core/pkg-cmake: provide our own platform description Yann E. MORIN
2017-02-28 18:26 ` Baruch Siach
2017-02-28 20:03 ` Yann E. MORIN
2017-02-28 20:41 ` Jörg Krause [this message]
2017-02-28 20:58 ` Yann E. MORIN
2017-02-28 22:15 ` Jörg Krause
2017-03-01 8:01 ` Arnout Vandecappelle
2017-03-01 7:58 ` Arnout Vandecappelle
2017-03-01 8:17 ` Thomas Petazzoni
2017-03-01 8:35 ` Arnout Vandecappelle
2017-03-01 18:43 ` Yann E. MORIN
2017-03-05 23:27 ` Arnout Vandecappelle
2017-03-06 17:00 ` Yann E. MORIN
2017-03-06 22:02 ` Arnout Vandecappelle
2017-03-02 12:29 ` Baruch Siach
2017-03-02 12:41 ` Thomas Petazzoni
2017-02-28 18:07 ` [Buildroot] [PATCH 2/5] cmake: bump version to 3.7.0 Yann E. MORIN
2017-02-28 18:07 ` [Buildroot] [PATCH 3/5] cmake: bump version to 3.7.1 Yann E. MORIN
2017-02-28 18:07 ` [Buildroot] [PATCH 4/5] cmake: adjust dependencies added for libuv Yann E. MORIN
2017-02-28 18:07 ` [Buildroot] [PATCH 5/5] cmake: bump version to 3.7.2 Yann E. MORIN
2017-03-01 7:49 ` [Buildroot] [PATCH 0/5] package/cmake: re-introduce cmake-3.7 Arnout Vandecappelle
2017-03-01 7:59 ` Thomas Petazzoni
2017-03-01 21:14 ` Thomas Petazzoni
2017-03-02 8:41 ` Thomas Petazzoni
2017-03-02 17:39 ` 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=1488314513.5877.3.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