#39086: cmake 2.8.10.2 with macosx_deployment_target 10.7 fails to configure ---------------------+------------------- Reporter: help@… | Owner: css@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: cmake | ---------------------+------------------- Changes (by macsforever2000@…): * owner: macports-tickets@… => css@… Comment: In the future, please Cc the port maintainer(s). -- Ticket URL: <https://trac.macports.org/ticket/39086#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X

#39086: cmake 2.8.10.2 with macosx_deployment_target 10.7 fails to configure ---------------------+------------------- Reporter: help@… | Owner: css@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: cmake | ---------------------+------------------- Comment (by ville.aakko@…): Hi, This is still an issue on Snow Leopard - CMAKE_OSX_SYSROOT is set wrongly exactly the same way (pointing to /Developer/SDKs/MacOSX10.8.sdk instead of /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.8.sdk/). I will try the approach above (I have no reason to believe it shouldn't work). However, I have no idea what is really going wrong, or where to look next. Also, this was originally Snow Leopard but I upgraded to Mountain Lion recently. After upgrade I upgraded XCode and MacPorts according to https://trac.macports.org/wiki/Migration {{{ $ sudo xcode-select --print-path /Applications/Xcode.app/Contents/Developer }}} So this is on Mountain Lion 10.8.4, XCode 4.6.3, and trying to install cmake 2.8.11.2. Hope this helps to find out what is going on (wrongly)! There are loads of other bugs on other ports (not to mention configure errors that are in no way related to MacPorts I found via google) where the SDKs is not found / looked for in the wrong path. I suspect this might not actually be a bug in MacPorts and/or cmake port, but maybe in OS X / XCode / or triggers only in certain situation (perhaps after some upgrade path(s)?). In bug #40237, reinstalling XCode repaired the issue for another user, but that didn't help in my case (I tried it already). There could still be some leftovers from XCode from OSX 10.6.X somewhere, however... -- Ticket URL: <https://trac.macports.org/ticket/39086#comment:3> MacPorts <http://www.macports.org/> Ports system for OS X

#39086: cmake 2.8.10.2 with macosx_deployment_target 10.7 fails to configure ---------------------+---------------------- Reporter: help@… | Owner: css@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: cmake | ---------------------+---------------------- Comment (by css@…): I just successfully built on Lion with `macosx_deployment_target` set to 10.7. Do you still get an error with the current version of the port? -- Ticket URL: <https://trac.macports.org/ticket/39086#comment:6> MacPorts <http://www.macports.org/> Ports system for OS X

#39086: cmake 2.8.10.2 with macosx_deployment_target 10.7 fails to configure ---------------------+---------------------- Reporter: help@… | Owner: css@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: cmake | ---------------------+---------------------- Comment (by ville.aakko@…): Hi, This is still an issue for me on Muontain Lion. I've just attached a log file from my system. Maybe someone can spot something in there. Now that I look at the original reporters log file, the output is slightly different, but the workaround still works. If you have no access to Mountain Lion, maybe you should upgrade. It's only 17,99€ ;-) -- Ticket URL: <https://trac.macports.org/ticket/39086#comment:8> MacPorts <http://www.macports.org/> Ports system for OS X

#39086: cmake 2.8.10.2 with macosx_deployment_target 10.7 fails to configure ---------------------+---------------------- Reporter: help@… | Owner: css@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: cmake | ---------------------+---------------------- Comment (by ville.aakko@…): Replying to [comment:9 css@…]:

Can you check:

* Do you have a `SDKROOT` environment variable?

No. Should I?

* What is the output from `xcode-select -print-path`?

If you read my previous comment, you'll notice it prints: {{{ $ sudo xcode-select --print-path /Applications/Xcode.app/Contents/Developer }}} Just a hunch, but I can't seem to be able to run xcode-select as non-root: {{{ xcode-select --print-path xcode-select: Error: Incorrect permissions for data file at '/usr/share /xcode-select/xcode_dir_link'. Run xcode-select -switch <xcode_folder_path> to reset the path to the Xcode folder. }}} Should I be able to? How are build systems (and, macports) supposed to find this directory without root priviledges? I have set MacPorts to run as a non-root (I have commented out macportsuser in macports.conf). Maybe this is causing problems... only a guess though. Can you (for who this is working correctly) run xcode-select --print-path as non-root? As what user have you set macports to run (as root or non-root)? -- Ticket URL: <https://trac.macports.org/ticket/39086#comment:10> MacPorts <http://www.macports.org/> Ports system for OS X

#39086: cmake 2.8.10.2 with macosx_deployment_target 10.7 fails to configure ---------------------+---------------------- Reporter: help@… | Owner: css@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: cmake | ---------------------+---------------------- Comment (by ville.aakko@…): Hi Larry, I have done that a bunch of times! {{{ $ sudo xcode-select --switch /Applications/Xcode.app Password: $ xcode-select -print-path xcode-select: Error: Incorrect permissions for data file at '/usr/share /xcode-select/xcode_dir_link'. Run xcode-select -switch <xcode_folder_path> to reset the path to the Xcode folder. $ sudo xcode-select -print-path /Applications/Xcode.app/Contents/Developer $ ls -l /usr/share/xcode-select/ ls: : Permission denied $ sudo ls -l /usr/share/xcode-select/ total 16 lrwx------ 1 root wheel 42 28 Syy 22:35 xcode_dir_link -> /Applications/Xcode.app/Contents/Developer -rw------- 1 root wheel 43 28 Syy 22:35 xcode_dir_path $ ls -ld /usr/share/xcode-select drwx------ 4 root wheel 136 28 Syy 22:35 /usr/share/xcode-select }}} I have tried manually changing permissions, so that /usr/share/xcode- select is readable and traversable by all, and xcode_dir_path is readable. The xcode_dir_link is a link, and it's permissions can't be changed (AFAICT). But /Applications/Xcode.app/Contents/Developer is readable by regular users. But, again, this might not be a bug in Macports (but instead in XCode / OS X / certain upgrade paths). Sorry if I have changed this bug report into a support forum / discussion =). But I hope it helps to determine if this is a bug in MacPorts or somewhere else (or an incompatibility with Mountain Lion / newest version of xcode / whatever...) Also, FWIW, after the first time commenting on this bug, my xcode has been upgraded to 5.0 (since it rolled out into App Store). -- Ticket URL: <https://trac.macports.org/ticket/39086#comment:12> MacPorts <http://www.macports.org/> Ports system for OS X

#39086: cmake 2.8.10.2 with macosx_deployment_target 10.7 fails to configure ----------------------+-------------------- Reporter: help@… | Owner: css@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: invalid | Keywords: Port: cmake | ----------------------+-------------------- Changes (by css@…): * status: assigned => closed * resolution: => invalid Comment: Replying to [comment:13 larryv@…]:

This is not a bug in MacPorts. At least, your problem isn’t. Please post about it to [[MailingLists|macports-users]], as it doesn’t seem to be related to this ticket.

So it sounds like this is due to some other kind of machine-specific environment error? If so then this ticket can be closed. -- Ticket URL: <https://trac.macports.org/ticket/39086#comment:14> MacPorts <http://www.macports.org/> Ports system for OS X