On Oct 18, 2014, at 11:50 PM, Ned Deily wrote:
> In article ,
> 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
>
> The reason, I think, is that Xcode 6.0.
In article ,
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
The reason, I think, is that Xcode 6.0.x was released to support iOS 8
when iOS 8 was released s
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/
>
> it always says
>
> /private/opt/local/ is not provided by a MacPorts port, e.g.
MacPorts should be in /opt/local, not /private/opt/local.
Is
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 wa
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 devel
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
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 ar
I just did a selfupdate to 2.3.2, and when I try to run
sudo port provides /private/opt/local/
it always says
/private/opt/local/ is not provided by a MacPorts port, e.g.
--
[15:24] nightowl:~ % port provides /opt/local/sbin/sasldblistusers2
/private/opt/local/sbin/sasldblistusers2 is not prov
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
__
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 wrote:
>
> I'm rebuilding my ports after installing Yosemite, and I'm stuck at cmake
>
On Sat, Oct 18, 2014 at 5:20 PM, Gregory Shenaut
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 the ports won't co
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 no
That worked. Thanks for the quick response.
Jay
On Oct 18, 2014, at 2:50 PM, Jeremy Lavergne 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 of what was installed.
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 foll
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 the
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
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
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.
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 far
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 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 to. You need to wai
20 matches
Mail list logo
