Looks to me that the command line tools were installed -- are not the compilers part of command line tools? Maybe they're not in the expected place in Yosemite?

Last login: Thu Jan 22 23:41:26 on ttys001
jeromes-Mac-mini:~ jeromeschatten$ gcc --version
Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.10.sdk/usr/include/c++/4.2.1
Apple LLVM version 6.0 (clang-600.0.56) (based on LLVM 3.5svn)
Target: x86_64-apple-darwin14.0.0
Thread model: posix
jeromes-Mac-mini:~ jeromeschatten$

j.

On 2015-01-22 11:23 PM, Ryan Schmidt wrote:
On Jan 23, 2015, at 12:31 AM, jerome schatten wrote:

*S*ystem: MacMini -- late 2014 - Yosemite 10.10.1; Xcode installed.

I've installed macports 2.3.3 with no problems; I've installed port hypermail 
with no 'apparent' problem. I've followed the MacPorts Guide every step of the 
way.

My first question is this: The install of the hypermail port gives:

jeromes-Mac-mini:bin jeromeschatten$ sudo port install hypermail

Warning: The Xcode Command Line Tools don't appear to be installed; most ports 
will likely fail to build.
Warning: Install them by running `xcode-select --install'.
--->  Fetching archive for hypermail
--->  Attempting to fetch hypermail-2.3.0_1.darwin_14.x86_64.tbz2 from 
http://packages.macports.org/hypermail
--->  Attempting to fetch hypermail-2.3.0_1.darwin_14.x86_64.tbz2.rmd160 from 
http://packages.macports.org/hypermail
--->  Installing hypermail @2.3.0_1
--->  Activating hypermail @2.3.0_1
--->  Cleaning hypermail
--->  Updating database of binaries
--->  Scanning binaries for linking errors
--->  No broken files found.


But Xcode IS installed and the tools work as I've used them elsewhere. Is this 
a or is this not a problem?
Yes, MacPorts requires the Xcode command line tools, and Xcode. These are two 
separate installations, as of OS X 10.7 Lion.


If it's not a problem, then at this point, I should be able to launch the 
hypermail binary with a './hypermail' and it should run. But it doesn't. The 
cursor simply moves to the next line and it sits there. No error messages, 
nothing.

I looked at the hypermail and xcode process with top and it reports:
PID   COMMAND      %CPU      TIME     #TH  #WQ  #PORT MEM    PURG CMPR PGRP
[...]
1435  hypermail           0.0       00:00.00    1    0    15 604K   0B     0B   
1435

1404  Xcode                0.0       00:02.26    8    1    249 66M    72K   0B  
 1404

So, it doesn't look like hypermail is doing much and Xcode is indeed there.
Xcode does not need to be running to use MacPorts, it just needs to be 
installed, as do the separate Xcode command line tools.

You didn't get an error while installing hypermail, so I would not suspect 
absence of the Xcode command line tools to have been a problem in this 
particular case. But you should install them to prevent future problems with 
other ports.




_______________________________________________
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Reply via email to