[MacPorts] #41070: cmake: Wrong CMAKE_SYSTEM_HOST_PROCESSOR setting

MacPorts noreply at macports.org
Wed Oct 30 20:03:32 PDT 2013


#41070: cmake: Wrong CMAKE_SYSTEM_HOST_PROCESSOR setting
----------------------+--------------------
  Reporter:  hjj@…    |      Owner:  css@…
      Type:  defect   |     Status:  closed
  Priority:  Normal   |  Milestone:
 Component:  ports    |    Version:  2.2.0
Resolution:  invalid  |   Keywords:
      Port:  cmake    |
----------------------+--------------------
Changes (by larryv@…):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 Replying to [ticket:41070 hjj@…]:
 > A colleague in USA suggests that we switch to homebrew to solve the
 > problem of getting cmake to do the correct thing on both linux and
 > darwin systems without dirty tricks, as testing for darwin and ports
 > and then change explicitly to x86_64. I hope that I instead can
 > persuade you to fix the problem.

 No. The problem is that you are using `CMAKE_HOST_SYSTEM_PROCESSOR`
 incorrectly.

 If you are not cross-compiling, `CMAKE_HOST_SYSTEM_PROCESSOR`
 [http://www.cmake.org/cmake/help/v2.8.12/cmake.html#variable:CMAKE_HOST_SYSTEM_PROCESSOR
 is equivalent] to `CMAKE_SYSTEM_PROCESSOR`, which is
 [http://www.cmake.org/cmake/help/v2.8.12/cmake.html#variable:CMAKE_SYSTEM_PROCESSOR
 defined to be] the output of `uname -p` on *nix systems, not `uname -m`.
 On my 10.8.5 machine:
 {{{
 % /usr/bin/uname -p
 i386
 }}}

 If `CMAKE_HOST_SYSTEM_PROCESSOR` does not provide the information you
 require, then you need to find another way of obtaining that information.

-- 
Ticket URL: <https://trac.macports.org/ticket/41070#comment:2>
MacPorts <http://www.macports.org/>
Ports system for OS X


More information about the macports-tickets mailing list