This is now trac #11280 On May 2, 11:23 am, Dima Pasechnik <dimp...@gmail.com> wrote: > On May 2, 9:03 am, amaseam <amas...@gmail.com> wrote: > > > > > > > 2011/4/30 Dima Pasechnik <dimp...@gmail.com>: > > > > On Apr 30, 12:54 pm, William Stein <wst...@gmail.com> wrote: > > >> On Wed, Apr 27, 2011 at 8:28 PM, Dima Pasechnik <dimp...@gmail.com> > > >> wrote: > > >> > Hi, > > > >> > I tried XCode 4 and came to conclusion that it is buggy as hell > > >> > - I can't build working Sage (due to startup-time segfaults, as > > >> > described here), > > >> > I can't even build a working copy of MPIR, etc etc... > > > >> > Even worse is behaviour with its clang compilers (they can't even > > >> > compile several parts of Sage) > > > >> Wow, that's incredible! > > > >> We should: > > > >> (1) add a remark right in the prereq spkg that checks that xcode 4 > > >> (4.0.1, to be precise) > > >> isn't being used (unless SAGE_PORT or something is set) > > > > In fact, I don't know how to check this easily: it ships the same > > > build of gcc as XCode 3 (3.2.6, to be precise) > > > (gcc version 4.2.1 (Apple Inc. build 5666) (dot 3)) > > > and there is no ready way to check the version of the whole setup. > > > The difference sits in libraries. > > > $ xcodebuild -version > > Xcode 3.1.4 > > Component versions: DevToolsCore-1204.0; DevToolsSupport-1186.0 > > BuildVersion: 9M2809 > > excellent! That's certainly can be used.
-- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
