A couple of queries about Xcode

: currently installed version of Xcode, 8.3.2, is not supported by MacPorts. For your currently installed system, only the following versions of Xcode are supported: 8.3.1 8.3 8.2.1 8.2 8.1 8.0 The file guide.macports.org says in a Note in Section 2.1: Always make sure to install the latest

Re: command line tools for Xcode 8.1?

> On Oct 28, 2016, at 3:34 PM, Murray Eisenberg <murrayeisenb...@gmail.com> > wrote: > > Under OS X 10.11.6, I just updated Xcode to version 8.1 via App Store. > > Release notes for Xcode 8.1 say: > > Known Issues > • There are no Command Line

Re: command line tools for Xcode 8.1?

On Fri, Oct 28, 2016 at 3:34 PM, Murray Eisenberg <murrayeisenb...@gmail.com > wrote: > Known Issues > >- There are no Command Line Tools (OS X 10.11) for Xcode 8.1. Xcode >8.1 contains SDKs that are incompatible with earlier toolchains. Developers >who want to ma

command line tools for Xcode 8.1?

Under OS X 10.11.6, I just updated Xcode to version 8.1 via App Store. Release notes for Xcode 8.1 say: Known Issues There are no Command Line Tools (OS X 10.11) for Xcode 8.1. Xcode 8.1 contains SDKs that are incompatible with earlier toolchains. Developers who want to make use of the Xcode 8

Xcode 8.1 - how's it been doing building ports?

Before I update my Xcode from 8.0 to 8.1 (on a couple of El Capitan systems), I'd like to check if there is any experience among those here whether the ports they build, do about the same, worse, better? I'm in a risk-minimizing mode at the moment, so I thought I'd ask before just updating

Re: Xcode installed before macports?

On Jan 19, 2016, at 11:45 PM, Bachsau wrote: > Ryan Schmidt wrote on 20.01.2016 04:11: >> Xcode 4.0, 4.1 and 4.2 for Snow Leopard are not recommended because they are >> not free so MacPorts is tested much less well on those versions and you are >> likely to run into mor

Re: Xcode installed before macports?

On Wed, Jan 20, 2016 at 12:45 AM, Bachsau <w...@bachsau.name> wrote: > Ryan Schmidt wrote on 20.01.2016 04:11: > >> Xcode 4.0, 4.1 and 4.2 for Snow Leopard are not recommended because they >> are not free so MacPorts is tested much less well on those versions and

Xcode installed before macports?

Must the latest Xcode be installed before macports? I installed Xcode 3.2 in Snow Leopard, then macports before I discovered there was an Xcode 4.2 available for Snow Leopard. Do I now need to remove macports and reinstall it to make use of Xcode 4.2? Thanks. Best regards, Tim

Re: Xcode installed before macports?

Timothy W. Grove wrote on 19.01.2016 23:21: Must the latest Xcode be installed before macports? I installed Xcode 3.2 in Snow Leopard, then macports before I discovered there was an Xcode 4.2 available for Snow Leopard. Do I now need to remove macports and reinstall it to make use of Xcode 4.2

Re: Xcode installed before macports?

On Jan 19, 2016, at 16:21, Timothy W. Grove wrote: > > Must the latest Xcode be installed before macports? I installed Xcode 3.2 in > Snow Leopard, then macports before I discovered there was an Xcode 4.2 > available for Snow Leopard. > > Do I now need to remove macp

Re: Xcode installed before macports?

Ryan Schmidt wrote on 20.01.2016 04:11: Xcode 4.0, 4.1 and 4.2 for Snow Leopard are not recommended because they are not free so MacPorts is tested much less well on those versions and you are likely to run into more problems when using them. However, it is still VERY unlikely he will run

Re: xrg build fails after OS X upgrade to 10.11.2 (15C50) and Xcode Version 7.2

> On Dec 10, 2015, at 8:31 AM, Rainer Müller <rai...@macports.org> wrote: > > On 2015-12-10 03:21, Manfred Antar wrote: >> It’s something with Xcode 7.2 >> Im sure this will be coming up again > > Yes, I got a similar report against MacVim: > https://trac.mac

Re: xrg build fails after OS X upgrade to 10.11.2 (15C50) and Xcode Version 7.2

On 2015-12-10 03:21, Manfred Antar wrote: > It’s something with Xcode 7.2 > Im sure this will be coming up again Yes, I got a similar report against MacVim: https://trac.macports.org/ticket/49950 It seems like Xcode 7.2 expects more restrictive permissions on this path, but it does not

xrg build fails after OS X upgrade to 10.11.2 (15C50) and Xcode Version 7.2

rsion 15.2.0: Fri Nov 13 19:56:56 PST 2015; root:xnu-3248.20.55~2/RELEASE_X86_64 x86_64 Not sure what the problem is. I uninstalled Xcode and did a fresh install , same results. It built fine on 11.10 Thanks ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users

Re: xrg build fails after OS X upgrade to 10.11.2 (15C50) and Xcode Version 7.2

On Dec 9, 2015, at 13:49, Manfred Antar wrote: > > When trying to build xrg on OS X 10.11.2 I get this: > > (/)747}port -v build xrg > ---> Building xrg > Build settings from command line: >ARCHS = x86_64 >CLANG_CXX_LIBRARY = libc++ >GCC_VERSION =

Re: xrg build fails after OS X upgrade to 10.11.2 (15C50) and Xcode Version 7.2

odebuild[8831:128591] Failed to locate a valid >> instance of CoreSimulatorService in the bootstrap. Adding it now. >> > > Sounds like a problem described on the ElCapitanProblems or ProblemHotlist > wiki pages. Open Xcode.app once, then close it. I already tried th

Re: xrg build fails after OS X upgrade to 10.11.2 (15C50) and Xcode Version 7.2

now. >>> >>> Sounds like a problem described on the ElCapitanProblems or ProblemHotlist >>> wiki pages. Open Xcode.app once, then close it. >> >> I already tried that a couple of times. I even deleted Xcode.app and >> downloaded new install. &g

Re: xrg build fails after OS X upgrade to 10.11.2 (15C50) and Xcode Version 7.2

Xcode.app once, then close it. > > I already tried that a couple of times. I even deleted Xcode.app and > downloaded new install. > Opened that up and closed it. Still the same.Not sure if it is Xcode or OS X > 10.11.2 or both that caused this. Sorry, I misremembered and gave you the s

Re: xrg build fails after OS X upgrade to 10.11.2 (15C50) and Xcode Version 7.2

Open Xcode.app once, then close it. >>> >>> I already tried that a couple of times. I even deleted Xcode.app and >>> downloaded new install. >>> Opened that up and closed it. Still the same.Not sure if it is Xcode or OS >>> X 10.11.2 or both that caused this

Re: Should I try to upgrade to XCode 4.2 4c199 - Mac OS X 10.6.8

> Am 04.10.2015 um 09:38 schrieb Ryan Schmidt <ryandes...@macports.org>: > > >> On Oct 4, 2015, at 2:36 AM, Dominik Reichardt wrote: >> >>> Am 04.10.2015 um 09:26 schrieb Ryan Schmidt: >>> >>> On OS X 10.6.8, Xcode 3.2.6 is the recomm

Re: Should I try to upgrade to XCode 4.2 4c199 - Mac OS X 10.6.8

ed to reinstall it. I think this issues is being tracked: > > Ticket #48938 (new defect) > ffmpeg build failure on 10.6 > Opened 13 days ago > Last modified 4 days ago On OS X 10.6.8, Xcode 3.2.6 is the recommended version. Xcode 4 for Snow Leopard was never available for free; yo

Re: Should I try to upgrade to XCode 4.2 4c199 - Mac OS X 10.6.8

On Oct 4, 2015, at 2:36 AM, Dominik Reichardt wrote: > Am 04.10.2015 um 09:26 schrieb Ryan Schmidt: > >> On OS X 10.6.8, Xcode 3.2.6 is the recommended version. Xcode 4 for Snow >> Leopard was never available for free; you had to have a paid developer >>

Re: Should I try to upgrade to XCode 4.2 4c199 - Mac OS X 10.6.8

ings I use have always worked. >> >> I recently got myself into a pickle (difficult situation) with ffmpeg and >> tried to reinstall it. I think this issues is being tracked: >> >> Ticket #48938 (new defect) >> ffmpeg build failure on 10.6 >> Opened 13 days ag

Should I try to upgrade to XCode 4.2 4c199 - Mac OS X 10.6.8

Newbie here. I have used mac ports for many years and never had a reason to write to the list. The few things I use have always worked. I recently got myself into a pickle (difficult situation) with ffmpeg and tried to reinstall it. I think this issues is being tracked: Ticket #48938 (new

Housekeeping script to reclaim disk space by removing old Xcode caches

I recently discovered that several gigabytes of disk space were being used by caches specific to Xcode versions I no longer had installed. I wrote a script to clean them up. You can get a copy by running: svn export https://svn.macports.org/repository/macports/users/ryandesign/scripts

Re: Housekeeping script to reclaim disk space by removing old Xcode caches

Seems I compile less than you ;) Phobos ~ > sudo ./housekeeping-xcode Password: ---> Deleting 2.7M of caches for Xcode 6.1.1-6A2008a which is no longer installed ---> Deleting 1.1M of caches for Xcode 6.2-6C131e which is no longer installed ---> Deleting 2.4M of caches for Xco

Re: Xcode 7.0?

> On Sep 18, 2015, at 08:15, Dave Horsfall <d...@horsfall.org> wrote: > > On Fri, 18 Sep 2015, Ryan Schmidt wrote: > >> No need for you to test anything. As I said before, OS X 10.11 requires >> Xcode 7. But this thread was started by someone on OS X 10.10, and

Re: Xcode 7.0?

On Sep 18, 2015, at 2:53 AM, Dave Horsfall wrote: > Looks like my MacBook (10.10.5) just helped itself to Xcode 7. Should I > be worried about any, err, issues? I recall a note about that... Because Xcode 7 only contains the OS X 10.11 SDK, you may have problems building some ports o

Re: Xcode 7.0?

On Fri, Sep 18, 2015 at 04:54:37AM -0500, Ryan Schmidt wrote: > > On Sep 18, 2015, at 2:53 AM, Dave Horsfall wrote: > > > Looks like my MacBook (10.10.5) just helped itself to Xcode 7. Should I > > be worried about any, err, issues? I recall a note about that... > > Be

Re: Xcode 7.0?

rks out I would be happy to try things for people. No need for you to test anything. As I said before, OS X 10.11 requires Xcode 7. But this thread was started by someone on OS X 10.10, and I explained in my previous post why Xcode 7 on OS X 10.10 might be problematic, in ways that Xcode 7 on O

Re: Xcode 7.0?

On Sep 18, 2015, at 7:09 AM, Richard Cobbe wrote: > On Fri, Sep 18, 2015 at 04:54:37AM -0500, Ryan Schmidt wrote: >> >> On Sep 18, 2015, at 2:53 AM, Dave Horsfall wrote: >> >>> Looks like my MacBook (10.10.5) just helped itself to Xcode 7. Should I >>>

Re: Xcode 7.0?

On Fri, 18 Sep 2015, Ryan Schmidt wrote: > No need for you to test anything. As I said before, OS X 10.11 requires > Xcode 7. But this thread was started by someone on OS X 10.10, and I > explained in my previous post why Xcode 7 on OS X 10.10 might be > problematic, in ways that X

Re: Xcode major version upgrades, migration?

On Thu, Sep 17, 2015 at 2:13 PM, Bradley Giesbrecht <pixi...@macports.org> wrote: > The migration guide [1] says the migration is not if you are only > upgrading Xcode. Does this hold for Xcode major version upgrades? Yes; while it may provide new compilers, the runtime part

Xcode major version upgrades, migration?

The migration guide [1] says the migration is not if you are only upgrading Xcode. Does this hold for Xcode major version upgrades? [1] http://trac.macports.org/wiki/Migration Regards, Bradley Giesbrecht (pixilla) ___ macports-users mailing list

Re: Xcode major version upgrades, migration?

> The migration guide [1] says the migration is not if you are only upgrading > Xcode. Does this hold for Xcode major version upgrades? > > Yes; while it may provide new compilers, the runtime part of libraries such > as libSystem, libc++, etc. come with the OS and are upgraded with the

Re: macports thinks xcode is not installed...?

Hi, I had the same warning over the weekend with my OSX 10.11 VM. I had Xcode 7 beta 4 installed from https://developer.apple.com/xcode/downloads/ and I also installed the Xcode 7 beta 4 command line tools from ‘additional tools’ link at the bottom of the above link. Interesting

Re: macports thinks xcode is not installed...?

On 03.08.2015 04:01 AM, Carlo Tambuatco wrote: I recently upgraded my harddrive to a hybrid SSD and had to reinstall OS X Yosemite then restore everything from Time Machine backup. I then re installed XCode albeit a newer version, this time I went with the XCode 7 beta 4 release

Re: macports thinks xcode is not installed...?

On Aug 2, 2015, at 10:50 PM, Mihai Moldovan wrote: On 03.08.2015 04:01 AM, Carlo Tambuatco wrote: I recently upgraded my harddrive to a hybrid SSD and had to reinstall OS X Yosemite then restore everything from Time Machine backup. I then re installed XCode albeit a newer version

Re: macports thinks xcode is not installed...?

installed XCode albeit a newer version, this time I went with the XCode 7 beta 4 release. The problem is that you are using an unreleased, testing Xcode version. While we don't support beta or pre-release versions of Xcode or OS X, merely using them is not necessarily a problem

Re: macports thinks xcode is not installed...?

) are prohibited - even for the root user. This is the first I'd heard of it. I like it. Thanks for letting us know. That may sound cool for us (and the unsuspecting user, that cannot mess up the system easily anymore), but it will inevitably break legacy behavior, like Xcode installing

macports thinks xcode is not installed...?

I recently upgraded my harddrive to a hybrid SSD and had to reinstall OS X Yosemite then restore everything from Time Machine backup. I then re installed XCode albeit a newer version, this time I went with the XCode 7 beta 4 release. It seems to automatically install the xcode command line tools

Re: How to fix faulty symlink in XCode 3.2.6, issue 14018?

On Jun 19, 2015, at 10:24 PM, semaphor...@yahoo.com wrote: I am trying to solve the issue described there http://bugs.python.org/issue14018, which prevents me from installing gqrx. The problem is I don't understand how the solution should be implemented. It states: The Xcode installer

Re: How to fix faulty symlink in XCode 3.2.6, issue 14018?

installing gqrx. The problem is I don't understand how the solution should be implemented. It states: The Xcode installer creates faulty symlinks to /Library within /Developer/SDKs. I assume /Library is the wrong target. But the example shows: $ cd /Developer/SDKs/MacOSX10.6.sdk/Library

Re: How to fix faulty symlink in XCode 3.2.6, issue 14018?

On Jun 20, 2015, at 7:34 AM, semaphor...@yahoo.com wrote: Thanks for your quick answer, but it doesn't seem to work, still. What error message are you seeing? ___ macports-users mailing list macports-users@lists.macosforge.org

Re: How to fix faulty symlink in XCode 3.2.6, issue 14018?

:info:configure is not set up correctly on this system. This is known to occur when :info:configure installing Xcode 3.2.6: :info:configure :info:configurehttp://bugs.python.org/issue14018 :info:configure :info:configure The problem may cause build errors that report missing

Re: How to fix faulty symlink in XCode 3.2.6, issue 14018?

In article 28ecc888-1cf6-4306-bfce-b4713369e...@yahoo.com, semaphor...@yahoo.com wrote: Ned: what are you referring to here? But yeah, the problem in issue14018 does not apply to any MacPorts python port and shouldn't be an issue for any other port unless there is a bug in the port.

Re: How to fix faulty symlink in XCode 3.2.6, issue 14018?

. [...] I just installed a fresh copy of Xcode 3.2.6 on Snow Leopard, and can confirm there is a problem with the Mac OS X 10.6 SDK's Frameworks, which is that /Developer/SDKs/MacOSX10.6.sdk/Library/Frameworks is a directory, and it contains a symlink Frameworks pointing to /Library/Frameworks

Re: How to fix faulty symlink in XCode 3.2.6, issue 14018?

): :info:configure The SDK Library/Frameworks path :info:configure :info:configure//Library/Frameworks :info:configure :info:configure is not set up correctly on this system. This is known to occur when :info:configure installing Xcode 3.2.6: :info:configure :info:configurehttp

Re: How to fix faulty symlink in XCode 3.2.6, issue 14018?

:info:configure//Library/Frameworks :info:configure :info:configure is not set up correctly on this system. This is known to occur when :info:configure installing Xcode 3.2.6: :info:configure :info:configurehttp://bugs.python.org/issue14018 :info:configure :info:configure

How to fix faulty symlink in XCode 3.2.6, issue 14018?

Hello there, I am trying to solve the issue described there http://bugs.python.org/issue14018, which prevents me from installing gqrx. The problem is I don't understand how the solution should be implemented. It states: The Xcode installer creates faulty symlinks to /Library within

Re: [Newbie Alert] Did i screw up my XCode?

-MBP:~ Ton$ sudo xcode-select --install Password: xcode-select: error: command line tools are already installed, use Software Update to install updates Does the directory /usr/include exist and contain header files? If so, then I don't know, and I would need to see the particular software

Re: [Newbie Alert] Did i screw up my XCode?

On Tue, Apr 14, 2015 at 9:39 AM, Ton Machielsen t...@machielsen.net wrote: Yep. Directory is there and contains header files. I am trying to compile linrad (http://www.sm5bsz.com/linuxdsp/linrad.htm). It fails on the ./configure step For what it's worth, the configure succeeds here (10.9).

Re: [Newbie Alert] Did i screw up my XCode?

You are my hero!!! I never looked at the version i am trying to compile. I was just ASSUMING that it was the latest/correct one…. (ASSUME makes and ASS out of ME). I am back in business!! Thanks, Brandon! I’ve been stuck for days on this. I just never looked at the obvious. :-( On Tue, Apr 14,

Re: [Newbie Alert] Did i screw up my XCode?

On Apr 13, 2015, at 7:54 AM, Ton Machielsen wrote: TM-MBP:~ Ton$ sudo xcode-select --install Password: xcode-select: error: command line tools are already installed, use Software Update to install updates Does the directory /usr/include exist and contain header files? If so, then I don't

[Newbie Alert] Did i screw up my XCode?

Hi all! New MacPorts user here. So this is what i have done so far: Installed Xcode Installed MacPorts All working fine Replaced MacPorts with Homebrew because i needed something that was in Homebrew but not in MacPorts. Now i cannot remember what. Removed Homebrew. Removed and reinstalled

Re: [Newbie Alert] Did i screw up my XCode?

On Apr 13, 2015, at 7:48 AM, Ton Machielsen wrote: TM-MBP:~ Ton$ /usr/bin/gcc -v Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/usr/include/c++/4.2.1 Apple LLVM version 6.1.0 (clang-602.0.49) (based on LLVM 3.6.0svn) Target:

Re: [Newbie Alert] Did i screw up my XCode?

On Apr 13, 2015, at 7:18 AM, Ton Machielsen wrote: New MacPorts user here. So this is what i have done so far: Installed Xcode Installed MacPorts All working fine Replaced MacPorts with Homebrew because i needed something that was in Homebrew but not in MacPorts. Now i cannot remember

Re: [Newbie Alert] Did i screw up my XCode?

at 2:45 PM, Ryan Schmidt ryandes...@macports.org wrote: On Apr 13, 2015, at 7:18 AM, Ton Machielsen wrote: New MacPorts user here. So this is what i have done so far: Installed Xcode Installed MacPorts All working fine Replaced MacPorts with Homebrew because i needed something

Re: [Newbie Alert] Did i screw up my XCode?

On Apr 13, 2015, at 7:18 AM, Ton Machielsen wrote: The gcc compiler is installed but does not work. The reason is probably missing header files. In addition to Xcode, have you installed the Xcode command line tools (which among other things installs the contents of /usr/include, which

Re: [Newbie Alert] Did i screw up my XCode?

TM-MBP:~ Ton$ sudo xcode-select --install Password: xcode-select: error: command line tools are already installed, use Software Update to install updates On Mon, Apr 13, 2015 at 2:48 PM, Ryan Schmidt ryandes...@macports.org wrote: On Apr 13, 2015, at 7:48 AM, Ton Machielsen wrote: TM-MBP

Re: Using Xcode toolchain internals (Was: apple clang vs macports clang performance)

On Wednesday January 28 2015 18:27:35 Lawrence Velázquez wrote: The libraries in XcodeDefault.xctoolchain aren't even versioned. There's no need for that since only a single version is present at any given time. I never meant to argue that using a shared library inside Xcode would be a good

Using Xcode toolchain internals (Was: apple clang vs macports clang performance)

of support and stability. The vendor can change a private ABI/API whenever it feels like, so it's a poor idea to rely on it. The libraries in XcodeDefault.xctoolchain aren't even versioned. Neither the Xcode SDKs nor the CLT contain those libraries, so I expect Eh? The CLT have libclang in /usr

Re: Which Xcode?

Xcode doesn't really do anything that you couldn't do with clang, llvm, gnu make and your choice of text editor. The best I've ever been able to say about Xcode is that I found it barely tolerable, now I regard using it as just like pounding nails with my fists. This is not at all to say I don't

Re: Which Xcode?

I wonder to what extent Xcode 3.2.6 can be configured to use new clang and the latest SDKs. That's an IDE concept I still prefer: individual editor windows, a separate project window etc. I really don't get that fashion of monolithic interfaces that block everything behind them and make

Re: Which Xcode?

Apple has not documented any way to plug in compilers other than those that come with Xcode. That doesn't mean that one cannot do so, just that Apple won't tell you how. However - while it would be some work - you could write an external compiler that plugs into CodeWarrior. That would just

Re: Which Xcode?

in compilers other than those that come with Xcode. That doesn't mean that one cannot do so, just that Apple won't tell you how. However - while it would be some work - you could write an external compiler that plugs into CodeWarrior. That would just be a wrapper around the clang command-line tool

Which Xcode?

I had to do a clean install of the OS (Mavericks) and now ready to re-install macports. Should I install xcode 6.1 or stick with 5? (I've heard that 6 is buggy). Mark ___ macports-users mailing list macports-users@lists.macosforge.org https

Re: Which Xcode?

On Sat, Nov 22, 2014 at 5:28 PM, Mark Brethen mark.bret...@gmail.com wrote: I had to do a clean install of the OS (Mavericks) and now ready to re-install macports. Should I install xcode 6.1 or stick with 5? (I've heard that 6 is buggy). 5 won't have Mavericks support (and it probably won't

Re: Which Xcode?

I install xcode 6.1 or stick with 5? (I've heard that 6 is buggy). 5 won't have Mavericks support (and it probably won't even install). 6.0 doesn't either, IIRC. -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com

Re: Which Xcode?

On Nov 22, 2014, at 11:28 AM, Mark Brethen wrote: I had to do a clean install of the OS (Mavericks) and now ready to re-install macports. Should I install xcode 6.1 or stick with 5? (I've heard that 6 is buggy). The latest generally available stable version supported on your operating

Re: Which Xcode?

If you have concerns about problems in Xcode 6.1, could you be more specific? I suppose he may be referring to the reviews on the Store (I checked several national stores, the reviews all agree that this version is buggy and crashy) ___ macports-users

Re: upgrading XCode on 10.9

MacPorts tends to work fine without Xcode unless a package needs xcodebuild. On Nov 20, 2014, at 10:41, René J.V. Bertin rjvber...@gmail.com wrote: MacPorts should do fine with the commandline tools, no? (xcode-select -p /Library/Developer/CommandLineTools

Re: upgrading XCode on 10.9

On Nov 20, 2014, at 10:44 AM, Jeremy Lavergne jer...@lavergne.gotdns.org wrote: MacPorts tends to work fine without Xcode unless a package needs xcodebuild. On Nov 20, 2014, at 10:41, René J.V. Bertin rjvber...@gmail.com wrote: MacPorts should do fine with the commandline tools

Re: upgrading XCode on 10.9

Hi, Tends to work, yes. We don't support that configuration, so just hope you don't run into any problems with it. another data point might be interesting here. During the upgrade to Yosemite I rebuilt all of my ports without Xcode and the 10.10 SDK in trace mode. All of my 500+ ports either

upgrading XCode on 10.9

Hi, I've seen lots of talk about XCode 6 lately. When I had my 10.9.4 VM running the last few days, I did get an update for the dev. command line tools (to 5.1 IIRC), but no sign of an update to the IDE. Would that require upgrading to 10.9.5 first? Cheers, René

Re: upgrading XCode on 10.9

In article 1977346.HivKc7Tkja@portia.local, I've seen lots of talk about XCode 6 lately. When I had my 10.9.4 VM running the last few days, I did get an update for the dev. command line tools (to 5.1 IIRC), but no sign of an update to the IDE. Would that require upgrading to 10.9.5 first

Re: upgrading XCode on 10.9

On Sunday November 16 2014 16:07:21 Ned Deily wrote: The Xcode entry in the Mac App store claims that 10.9.4 or later is required for the current Xcode 6.1. You may need to login in the App Store app to buy it (for free) if you haven't already or to ensure your account is registered

Xcode 6.1 stealth update

It appears that the version of Xcode 6.1 that is available on the Mac App Store (CFBundleVersion 6604, ProductBuildVersion 6A1052d) is slightly newer than the version of Xcode 6.1 that was available previously on the Apple Developer web site (CFBundleVersion 6602, ProductBuildVersion 6A1052d

Of 10.10 and Xcode etc

Short version: updated to MacPorts 2.3.2 for the same reason that Everest was climbed, but forewarned by the iOS 8 debacle I held off with Yosemite for a while because it needed Xcode 6.1. Well, it just made itself at home; I've yet to venture into ports-land... -- Dave Horsfall (VK2KFU) http

Xcode 6.1 now available in the App Store

Xcode 6.1 seem to be available in the App Store now. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Yosemite, XCode 6.1?

: 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 compile with the released version of XCode

Re: Yosemite, XCode 6.1?

On Oct 19, 2014, at 12:50 AM, Ned Deily n...@acm.org 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

Re: Yosemite, XCode 6.1?

On 19 .10 .2014, at 16.41, James Rome jamesr...@gmail.com wrote: xcode6.1 is released on the Apple Developer's site: https://developer.apple.com/downloads/index.action# https://developer.apple.com/downloads/index.action# For me, it’s ”Available shortly” there… ! ! Jyrki

Re: Yosemite, XCode 6.1?

is a component of XCOde 6.1. I had the same message. Although I already had XCode 6.0.1 from the Mac App Store, from which I had already chosen to install CLI tools, I tried xcode-select --install anyway, as MacPorts suggested to me. It triggered some OS X software install window, and then it started

Re: Yosemite, XCode 6.1?

processes for some ports really do depend on using an SDK and/or xcodebuild, which is why MacPorts requires that you install both Xcode and the Command Line Tools. Back in the day before the CLTs were broken out as a convenient separate item, it really didn't matter as you always had to install

XCode Command line tools not detected?

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?

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, XCode 6.1?

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?

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

Re: Yosemite, XCode 6.1?

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

Re: Yosemite, XCode 6.1?

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

Re: XCode Command line tools not detected?

are missing message comes up, but ports still build, doesn't this indicate a problem in the detection process? I had the previous Xcode (6.0.1) and tools installed on the MBPro before upgrading to Yosemite. It might be that Macports used the old tools to build with, but detected that the new tool

Re: Yosemite, XCode 6.1?

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, XCode 6.1?

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?

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

All ok with Xcode 6.0.1 and Command Line Tools 6.0?

Hi everyone, I noticed Apple recently made available, for OS X 10.9, XCode 6.0.1 and Command Line Tools 6.0. I would like to install both on one of our Macs with MacPorts 2.2.1 installed. Are there any known issues? Thanks, -T.M. ___ macports-users

Re: All ok with Xcode 6.0.1 and Command Line Tools 6.0?

On Fri, Sep 26, 2014 at 2:49 AM, Tabitha McNerney tabith...@gmail.com wrote: I noticed Apple recently made available, for OS X 10.9, XCode 6.0.1 and Command Line Tools 6.0. I would like to install both on one of our Macs with MacPorts 2.2.1 installed. Are there any known issues? It's been

Re: All ok with Xcode 6.0.1 and Command Line Tools 6.0?

I'm pretty sure Octave has issues with the new Clang/LLVM in Xcode 6. We're working on it during the coming days to verify and hopefully fix. - MLD On Fri, Sep 26, 2014 at 2:49 AM, Tabitha McNerney tabith...@gmail.com wrote: I noticed Apple recently made available, for OS X 10.9, XCode 6.0.1

Re: All ok with Xcode 6.0.1 and Command Line Tools 6.0?

On Sep 26, 2014, at 1:49 AM, Tabitha McNerney wrote: I noticed Apple recently made available, for OS X 10.9, XCode 6.0.1 and Command Line Tools 6.0. I would like to install both on one of our Macs with MacPorts 2.2.1 installed. Are there any known issues? I've been running the Xcode 6

Re: All ok with Xcode 6.0.1 and Command Line Tools 6.0?

I couldn't get CMake (3.0.2) to install today (10.10 preview 3, Xcode 6.0.1). It's kinda critical for other ports I maintain, so I'll be poking on it in the coming week. - MLD ___ macports-users mailing list macports-users@lists.macosforge.org https

  1   2   3   4   5   6   7   >