So I am also unsure of what exactly your scenario is (what the
reproduction steps are).
Without any environment variables, cross compiling isn't used, so this
bug isn't hit. It's only when you set environment variables to use
cross compilers that you might hit this scenario. But if you look at,
** Changed in: cmake (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to cmake in Ubuntu.
https://bugs.launchpad.net/bugs/1472314
Title:
Fix subsequent cmake runs when using multi-arch
To manage
Ping?
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to cmake in Ubuntu.
https://bugs.launchpad.net/bugs/1472314
Title:
Fix subsequent cmake runs when using multi-arch
To manage notifications about this bug go to:
** Tags added: patch
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to cmake in Ubuntu.
https://bugs.launchpad.net/bugs/1472314
Title:
Fix subsequent cmake runs when using multi-arch
To manage notifications about this bug go to:
** Patch added: cmake.patch
https://bugs.launchpad.net/ubuntu/+source/cmake/+bug/1472314/+attachment/4425866/+files/cmake.patch
** Description changed:
Running cmake a second time on a project when using multi-arch seems to
be broken without this patch in Ubuntu.
+
+ NB: This is a patch
How to reproduce this? and what do you mean by running a second time?
Cause, mutliarch file only kicks in when environmental variables are set
correctly pointing at cross-arch build/host combination and otherwise
does nothing and defaults to a normal native compilation.
Imho this patch should
log that reproduces the error:
mkdir build; cd build; cmake ..; cmake ..
The second time that it's configured cmake doesn't need to detect the
platform anymore so CMakeDetermineSystem.cmake isn't called anymore as
it calls the Platform file directly.
** Attachment added: cmake-ubuntu-error