Opened 11 years ago
Closed 11 years ago
#40641 closed defect (invalid)
metis build fails
Reported by: | lord@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.2.0 |
Keywords: | Cc: | ryandesign (Ryan Carsten Schmidt) | |
Port: | metis |
Description
rosody /Users/lord/tmp# port install octave ---> Computing dependencies for octave ---> Dependencies to be installed: metis qhull qrupdate texinfo ---> Fetching archive for metis ---> Attempting to fetch metis-5.1.0_0.darwin_12.x86_64.tbz2 from http://packages.macports.org/metis ---> Attempting to fetch metis-5.1.0_0.darwin_12.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/metis ---> Attempting to fetch metis-5.1.0_0.darwin_12.x86_64.tbz2 from http://lil.fr.packages.macports.org/metis ---> Fetching distfiles for metis ---> Verifying checksums for metis ---> Extracting metis ---> Applying patches to metis ---> Configuring metis Error: org.macports.configure for port metis returned: configure failure: command execution failed Error: Failed to install metis Please see the log file for port metis for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_metis/metis/main.log Error: The following dependencies were not installed: metis qhull qrupdate texinfo To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port octave failed
Log file attacged
Attachments (3)
Change History (20)
Changed 11 years ago by lord@…
comment:1 Changed 11 years ago by lord@…
comment:2 Changed 11 years ago by lord@…
This also seems to be relevant: #40250.
Please advise on workaround for this problem.
comment:3 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
Hmm, the log says:
:info:configure CMake Error at /opt/local/share/cmake-2.8/Modules/Platform/Darwin.cmake:190 (message): :info:configure CMAKE_OSX_DEPLOYMENT_TARGET is '10.8' but CMAKE_OSX_SYSROOT: :info:configure :info:configure "" :info:configure :info:configure is not set to a MacOSX SDK with a recognized version. Either set :info:configure CMAKE_OSX_SYSROOT to a valid SDK or set CMAKE_OSX_DEPLOYMENT_TARGET to :info:configure empty.
I don't get this error on my system, OS X 10.8.5, with Xcode 5. What version of Xcode do you have? Are your ports up to date -- have you run "sudo port selfupdate" lately?
comment:4 Changed 11 years ago by lord@…
I am running XCode Version 5.0 (5A1413). And yes, I did selfupdate several times today.
comment:5 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
Priority: | High → Normal |
---|
I'm not sure where cmake records information about what went wrong. Could you attach the file CMakeCache.txt that's in the directory that will be opened in the Finder by running this command in the Terminal:
open $(port work metis)/*/build/*
Maybe it will shed some light.
Changed 11 years ago by lord@…
Attachment: | CMakeCache.txt added |
---|
comment:6 Changed 11 years ago by lord@…
Please find attached.
FYI - this is a fresh install of macports. I removed my old macports install and installed from scrarch yesterday.
comment:7 Changed 11 years ago by lord@…
If there is any other information I could provide to help to diagnose this? I need octave for work and I hate to switching away from ports to homebrew as some people suggest :(
comment:8 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | ryandesign@… added |
---|---|
Port: | metis added |
There are quite a lot of settings in my CMakeCache.txt that aren't in yours and I'm not sure why. Are you running the same version of cmake as me? I have cmake 2.8.11.2.
comment:9 Changed 11 years ago by lord@…
I have cmake version 2.8.11.2.
prosody /Users/lord/src/spiral> port info cmake Warning: xcodebuild exists but failed to execute cmake @2.8.11.2 (devel) Variants: gui, universal Description: An extensible, open-source system that manages the build process in an operating system and compiler independent manner. Unlike many cross-platform systems, CMake is designed to be used in conjunction with the native build environment. Homepage: http://www.cmake.org/ Library Dependencies: libidn, openssl Platforms: darwin, freebsd License: BSD Maintainers: css@macports.org
comment:10 Changed 11 years ago by lord@…
I attempted to re-install cmake building it from source code and surprisingly it does not compile! port install -v -s cmake fails. See attached log. Looks like something is broken but I could not figure out why. I have fresh XCode 5 and ports install. Compiler seem to be working...
Changed 11 years ago by lord@…
comment:11 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
What does "xcodebuild -version
" say? Are your command line tools up to date for your version of Xcode?
comment:12 Changed 11 years ago by lord@…
I have command line tools installed.
prosody /Users/lord# xcodebuild -version Xcode 5.0 Build version 5A1413
I noticed that xcode-select works only from root: As root:
prosody /Users/lord# xcode-select -print-path /Applications/Xcode.app/Contents/Developer
As myself:
prosody /Users/lord> 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.
So if part of a build is executed as non-root it might cause problems? However I run port command as root.
comment:13 Changed 11 years ago by lord@…
Non-root xcode-select problem is solved. Apparently it is not enough to do xcode-selct from command line. One needs to go to XCode preferences, "Locations" tab and select command line tools there. This solves the permission issue:
prosody /Users/lord> xcode-select -print-path /Applications/Xcode.app/Contents/Developer
Checking if this solves the compilation problem....
comment:14 follow-up: 15 Changed 11 years ago by lord@…
I confirm that this solved the issue and now metis compiles OK. Apparently this is a major gotcha with upgrade to XCode 5 and I suggest updating installation instructions web site to reflect this by adding the following text:
After installing command line tools, go to XCode preferences, "Locations" tab and select latest command line tools version there.
comment:15 Changed 11 years ago by larryv (Lawrence Velázquez)
Replying to lord@…:
Apparently this is a major gotcha with upgrade to XCode 5
Is it? I did not have to make this change when updating from Xcode 4.x to 5.
comment:16 Changed 11 years ago by lord@…
Well, all I can say it happened to me and I found the solution mentioned somewhere on the stackoveflow. Even if it affects small percent of users perhaps it worth mentioning to save them hours of headache...
comment:17 Changed 11 years ago by seanfarley (Sean Farley)
Resolution: | → invalid |
---|---|
Status: | new → closed |
Could be related to [110134]