On Fri, Feb 17, 2012 at 11:00:34AM -0500, Alexander Hansen wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 2/17/12 10:04 AM, Jack Howarth wrote:
> > It might be a reasonable idea to add a few lines of code to fink
> > that checks for an unset developer directory path. I believe all
> > recent Xcode releases have been setting this path so only Xcode
> > 4.3 would result in 'xcodebuild -version' producing the error...
> >
> > Error: No developer directory found at /Developer. Run
> > /usr/bin/xcode-select to update the developer directory path.
> >
> > We could either have fink error out with a message that the user
> > needs to execute...
> >
> > sudo xcode-select -switch /Applications/Xcode.app
> >
> > or assume that the user must be on Xcode 4.3 or later and execute
> > that command for them. Since I have observed that the /usr/bin/c++
> > symlink can be left set to llvm-g++-4.2 when the developer
> > directory path is unset, I worry what other obscure issues could
> > exist as well in that case. Jack
> >
>
> For what it's worth, "xcodebuild -version" is only used in the
> bootstrap script, and there only to check whether Xcode's version is
> within the allowable limits for the OS version. Everywhere else in
> fink VirtPackage.pm is used, and that has been updated for fink-0.32.3 .
>
> I wouldn't think that /usr/bin/c++ still pointing to llvm-g++-4.2
> should really matter, since we've gone to all of the trouble to
> circumvent it with the path-prefix-clang wrappers. "c++" is still
> "clang++" by default for Fink builds on 10.7.
I've only tested it once, but I am pretty sure when I did the Xcode 4.3
installation over Xcode 4.2.1 followed by the Command Line Tools
installation (but not setting the developer directory path with
xcode-select), that the files sizes in /usr/bin and
/Applications/Xcode.app/Contents/Developer/usr/bin
differed. I think it is worthwhile to make sure the user is really
running the Xcode version that they think they are.
>
> If anything, I'd worry more about packages that _don't_ work with
> clang that suddenly find themselves trying to build with it, due to a
> maintainer using e.g. SetCC: /usr/bin/gcc
My understanding from the Apple developers is that /usr/bin/gcc and /usr/bin/g++
will always be kept pointing at llvm-gcc-4.2 and llvm-g++-4.2 (at least while
they exist in Xcode).
Jack
>
> - --
> Alexander Hansen, Ph.D.
> Fink User Liaison
> http://finkakh.wordpress.com/
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (Darwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAk8+eaIACgkQB8UpO3rKjQ/mGQCfSK1gLI92bynl0OCO5pu5TV7T
> X4cAn3HsD+SbGCFaKNqiNg+6U/lSjYlV
> =/AnR
> -----END PGP SIGNATURE-----
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel
