On Fri, Aug 10, 2012 at 08:22:02AM -0700, Jeremy Huddleston Sequoia wrote:
>
> On Aug 10, 2012, at 06:32, Jack Howarth <howa...@bromo.med.uc.edu> wrote:
>
> > On Thu, Aug 09, 2012 at 06:15:46PM -0700, Jeremy Huddleston Sequoia wrote:
> >>
> >> On Aug 9, 2012, at 18:06, Jack Howarth <howa...@bromo.med.uc.edu> wrote:
> >>
> >>> On Thu, Aug 09, 2012 at 05:53:51PM -0700, Jeremy Huddleston Sequoia wrote:
> >>>>
> >>>> On Aug 9, 2012, at 17:08, Jack Howarth <howa...@bromo.med.uc.edu> wrote:
> >>>>
> >>>>> Did anyone else notice that the initial release of Xcode 4.4 on Lion
> >>>>> seemed to install an
> >>>>> older version of the Command Line Tools on Lion than on Mountain Lion?
> >>>>
> >>>> Yes, that was discussed on this mailing list. It should be fixed now
> >>>> (you should see an "install" or "update" button in XCode for command
> >>>> line tools to install the correct versions). The issue only affected
> >>>> the tools installed from within XCode on Lion after upgrading from XCode
> >>>> 4.3. You still had the option of installing the correct package from
> >>>> http://connect.apple.com
> >>>
> >>> Hmm, I am pretty sure that I manually downloaded the original Xcode 4.4
> >>> Command Line Tools for Lion and installed that over
> >>> the copy that Xcode 4.4's Preference panel installed which still left me
> >>> with the stale compilers and devtools.
> >>
> >> Well that seems contrary to what everyone in the macports-users thread
> >> mentioned, but at least it seems to be working for you now =)
> >
> > Jeremy,
> > Curiously, the Command Line Tools from August 2012 for Lion are slightly
> > newer than those from
> > the August 2012 release for Mountain Lion. On Lion, Xcode 4.4.1 installs...
>
> Ok, well then that answers that ... "something" got fixed for clang =) If
> you're curious, you can check the ChangeLogs once they're posted to
> http://opensource.apple.com (and poke me when you notice that happen, so I
> can update the cctools and ld64 ports).
>
> Thanks,
> Jeremy
>
Jeremy,
It seems that Apple was may have simply botched the initial August 2012
Command Line Tools update
for Mountain Lion. A new Command Line Tools update (without a matching
Xcode.app update) appeared today
in Xcode and after installation now shows...
h% clang -v
Apple clang version 4.0 (tags/Apple/clang-421.0.60) (based on LLVM 3.1svn)
Target: x86_64-apple-darwin12.0.0
Thread model: posix
which finally syncs the Command Line Tools for Lion and Mountain Lion on Xcode
4.4.x.
Jack
> >
> > % clang -v
> > Apple clang version 4.0 (tags/Apple/clang-421.0.60) (based on LLVM 3.1svn)
> > Target: x86_64-apple-darwin11.4.2
> > Thread model: posix
> > % ld -v
> > @(#)PROGRAM:ld PROJECT:ld64-133.3
> > configured to support archs: armv6 armv7 i386 x86_64
> > LTO support using: LLVM version 3.1svn, from Apple Clang 4.0 (build
> > 421.0.60)
> >
> > whereas on Mountain Lion, Xcode 4.4.1 installs...
> >
> > % clang -v
> > Apple clang version 4.0 (tags/Apple/clang-421.0.57) (based on LLVM 3.1svn)
> > Target: x86_64-apple-darwin12.0.0
> > Thread model: posix
> > % ld -v
> > @(#)PROGRAM:ld PROJECT:ld64-133.3
> > configured to support archs: armv6 armv7 i386 x86_64
> > LTO support using: LLVM version 3.1svn, from Apple Clang 4.0 (build
> > 421.0.57)
> >
> > Odd. Anyway, that argues that the Command Line Tools now shipping for Xcode
> > 4.4.1
> > on Lion aren't the same ones that shipped with the Xcode 4.4 release on
> > Lion.
> > Jack
> >
> >>
> >> --Jeremy
> >>
> >>
_______________________________________________
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-dev
