Re: mysql5 port upgrade failed

2014-10-18 Thread Christopher Jones
Thanks, but now it fails on upgrading make, I am using mysql56, because I am too using mysql56-server for Egroupware and cacti. I am thinking of complete removing macports and install all application fresh and see if they are failing, the main applications are apache2, cyrus-imapd,

Re: mysql5 port upgrade failed

2014-10-18 Thread Horst Simon
On 18 Oct 2014, at 4:28 pm, Ryan Schmidt ryandes...@macports.org wrote:On Oct 18, 2014, at 12:04 AM, Horst Simon wrote:Thanks, but now it fails on upgrading make, I am using mysql56, because I am too using mysql56-server for Egroupware and cacti. I am thinking of complete removing macports and

Re: mysql5 port upgrade failed

2014-10-18 Thread Christopher Jones
Hi, So yes, its cmake not make you are having problems with, and from the log you can see its exactly the problem I was referring to. You need to wait for the release of Xcode 6.1, or install the preview if its still available… Chris On 18 Oct 2014, at 7:20am, Horst Simon

Re: mysql5 port upgrade failed

2014-10-18 Thread Horst Simon
Thanks, this is a test system and I can wait until XCode 6.1 Sent from my iPhone On 18 Oct 2014, at 17:47, Christopher Jones jon...@hep.phy.cam.ac.uk wrote: Hi, So yes, its cmake not make you are having problems with, and from the log you can see its exactly the problem I was referring

XCode Command line tools not detected?

2014-10-18 Thread David Nicholls
I think Macports does not detect newer installs of Xcode tools. Here's the story Having just upgraded from Mavericks to Yosemite, I installed Xcode 6.1, including the extras it asked for when run for the first time. Xcode 6.1 (plus extras) includes the command line tools inside the app, so

Re: XCode Command line tools not detected?

2014-10-18 Thread Ryan Schmidt
Both Xcode and the Xcode command line tools are and have always been required for MacPorts. The pre-built installers for MacPorts 2.3.2, for all OS X version from Yosemite back to Tiger, were uploaded yesterday and are linked from the MacPorts web site.

Yosemite upgrade

2014-10-18 Thread Comer Duncan
Yesterday I installed Yosemite but have not yet done either selfupdate or upgrade outdated. Before I do that I am wondering whether there are any recommendations as to whether it is too early to upgrade since perhaps macports code developers need some time to get essentials ready for such? I sort

Re: Yosemite upgrade

2014-10-18 Thread Jeremy Lavergne
If you've already installed Yosemite, then your existing MacPorts will likely not function. Simply re-install MacPorts to get it running again. Once running, you can do selfupdate and make the usual list of requested packages in a file and uninstall/reinstall everything. Another option is using

Re: Yosemite upgrade

2014-10-18 Thread Fisher, Jay L.
One warning. I just installed Yosemite, then tried to follow the macports instructions on migrating. As part of the instructions on the page, it says to save your installed ports and then uninstall the ports. However, after upgrading, my port command doesn’t work - it only complains that

Re: Yosemite upgrade

2014-10-18 Thread Jeremy Lavergne
You only need to reinstall the macports binary. The reinstalled MacPorts can read the existing software list, there is no reason to panic about it losing track of what was installed. On Oct 18, 2014, at 3:47 PM, Fisher, Jay L. wrote: One warning. I just installed Yosemite, then tried to

Re: Yosemite upgrade

2014-10-18 Thread Fisher, Jay L.
That worked. Thanks for the quick response. Jay On Oct 18, 2014, at 2:50 PM, Jeremy Lavergne jer...@lavergne.gotdns.org wrote: You only need to reinstall the macports binary. The reinstalled MacPorts can read the existing software list, there is no reason to panic about it losing track

Yosemite, XCode 6.1?

2014-10-18 Thread Gregory Shenaut
I'm rebuilding my ports after installing Yosemite, and I'm stuck at cmake like several other people. I currently have XCode 6.0.1. However, I'm also seeing this unusual (to me) message: “Warning: All compilers are either blacklisted or unavailable; defaulting to first fallback option”. And I

Re: Yosemite, XCode 6.1?

2014-10-18 Thread Brandon Allbery
On Sat, Oct 18, 2014 at 5:20 PM, Gregory Shenaut gkshen...@ucdavis.edu wrote: And I note that in the cmake log, it appears to require the MacOSX10.10.sdk, which is a component of XCOde 6.1. I could download a pre-release version of XCode 6.1 from the Apple site, but it seems odd to me that

Re: Yosemite, XCode 6.1?

2014-10-18 Thread Chris Jones
Its quite simple, you need the OSX 10.10 SDK, which is only available in Xcode 6.1, which for whatever reason is not released yet. You need to wait for it On 18 Oct 2014, at 10:20 pm, Gregory Shenaut gkshen...@ucdavis.edu wrote: I'm rebuilding my ports after installing Yosemite, and

Re: Yosemite, XCode 6.1?

2014-10-18 Thread René J . V . Bertin
On Saturday October 18 2014 22:25:09 Chris Jones wrote: Its quite simple, you need the OSX 10.10 SDK, which is only available in Xcode 6.1, which for whatever reason is not released yet. You need to wait for it Quite simple indeed ... early adopters' blues. R

MacPorts 2.3.2 and port provides

2014-10-18 Thread Greg Earle
I just did a selfupdate to 2.3.2, and when I try to run sudo port provides /private/opt/local/some/path it always says /private/opt/local/some/path is not provided by a MacPorts port, e.g. -- [15:24] nightowl:~ % port provides /opt/local/sbin/sasldblistusers2

Re: XCode Command line tools not detected?

2014-10-18 Thread David Nicholls
Yes, of course. My question was how Macports detects whether the tools are installed, and whether it detects them if the tools are part of the Xcode.app (if they are). If the tools are not installed, then some ports won't build. If all ports build, the tools are installed. If the tools

Re: Yosemite, XCode 6.1?

2014-10-18 Thread Ryan Schmidt
On Oct 18, 2014, at 4:20 PM, Gregory Shenaut wrote: However, I'm also seeing this unusual (to me) message: “Warning: All compilers are either blacklisted or unavailable; defaulting to first fallback option”. This message is not related to the cmake build failure. Some ports blacklist

Re: Yosemite upgrade

2014-10-18 Thread Ryan Schmidt
On Oct 18, 2014, at 2:07 PM, Comer Duncan wrote: Yesterday I installed Yosemite but have not yet done either selfupdate or upgrade outdated. Before I do that I am wondering whether there are any recommendations as to whether it is too early to upgrade since perhaps macports code

Re: Yosemite upgrade

2014-10-18 Thread Ryan Schmidt
Remember to Reply All when you reply. On Oct 18, 2014, at 7:13 PM, Carlo Tambuatco wrote: Yeah, just upgraded my ports yesterday after upgrading to Yosemite, and cmake along with other ports such as pypy etc fail to upgrade properly. I am using the Xcode 6.0 toolchain, so do I need to wait

Re: MacPorts 2.3.2 and port provides

2014-10-18 Thread Ryan Schmidt
On Oct 18, 2014, at 5:40 PM, Greg Earle wrote: I just did a selfupdate to 2.3.2, and when I try to run sudo port provides /private/opt/local/some/path it always says /private/opt/local/some/path is not provided by a MacPorts port, e.g. MacPorts should be in /opt/local, not

Re: Yosemite, XCode 6.1?

2014-10-18 Thread Ned Deily
In article f763bd5f-40f8-4b30-9a3a-2d7628a09...@hep.phy.cam.ac.uk, Chris Jones jon...@hep.phy.cam.ac.uk wrote: Its quite simple, you need the OSX 10.10 SDK, which is only available in Xcode 6.1, which for whatever reason is not released yet. You need to wait for it The reason, I think,

Re: Yosemite, XCode 6.1?

2014-10-18 Thread Ryan Schmidt
On Oct 18, 2014, at 11:50 PM, Ned Deily wrote: In article f763bd5f-40f8-4b30-9a3a-2d7628a09...@hep.phy.cam.ac.uk, Chris Jones jon...@hep.phy.cam.ac.uk wrote: Its quite simple, you need the OSX 10.10 SDK, which is only available in Xcode 6.1, which for whatever reason is not released yet. You