Upgrading XCode to version 2.5 (gcc build 5370, slightly newer than
William's) solved the problem; nothing more was necessary.

Thanks very much to everyone who responded!

Steve

On Dec 16, 2007 2:37 PM, mabshoff
<[EMAIL PROTECTED]> wrote:

>
> On Dec 16, 6:21 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
>
> > On Dec 16, 2007 9:17 AM, Stephen Forrest <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> > > I just downloaded the 2.9 source tarball and attempted a build.  It died 
> > > on
> > > building lapack.  It looks like the test* files in
> > > spkg/build/lapack-20071123/src/INSTALL are for a different architecture.
> >
> > > I'm running OSX 10.4 Intel; 2 GHz Intel Core Duo and 1 GB of RAM.
> >
> > > Steve
> >
> > > ****************************************************
> > > GCC Version
> > > gcc -v
> > > Using built-in specs.
> > > Target: i686-apple-darwin8
> > > Configured with: /private/var/tmp/gcc/gcc- 5250.obj~20/src/configure
> > > --disable-checking -enable-werror --prefix=/usr --mandir=/share/man
> > > --enable-languages=c,objc,c++,obj-c++
> > > --program-transform-name=/^[cg][^.-]*$/s/$/-4.0/
> > > --with-gxx-include-dir=/include/c++/4.0.0 --build=powerpc-apple-darwin8
> > > --with-arch=pentium-m --with-tune=prescott --program-prefix=
> > > --host=i686-apple-darwin8 --target=i686-apple-darwin8
> > > Thread model: posix
> > > gcc version 4.0.1 (Apple Computer, Inc. build 5250)
> >
>
> Hi Steve,
>
>
> > I'm not sure if this is related to the problem you just reported,
> > but you should upgrade to a newer version of XCode.
> > E.g., on my intel osx10 10.4 test machine I have build 5367:
> >
>
> I suspect the same issue, since we recently updated the binary g95 for
> OSX 10.5.
>
> Slightly surreal, but the first hit on Google for "libf95.a is out of
> date" is:
>
> http://www.mail-archive.com/[email protected]/msg04632.html
>
> Analog to the above mail do a
>
> touch  spkg/installed/lapack-20071123.spkg
>
> since we don't really need Lapack on OSX. We started building it also
> on OSX in anticipation of building ATLAS there, too. I suspect that
> you will run into trouble "down the road" with numpy, scipy and cvxopt
> if you don't fix the problem via William's suggested fix.
>
> A last resort is to install gfortran and do SAGE_FORTRAN=`which
> gfortran` before forcing a rebuild of the sage fortran.spkg via
>
> ./sage -f spkg/standard/fortran-20071120.p1.spkg
>
> Let us know if you run into any more trouble. If the above solves your
> problem we should update the readme to reflect the requirement for a
> specific XCode release.
>
>
> > $ gcc -v
> > gcc version 4.0.1 (Apple Computer, Inc. build 5367)
> >
> > William
>
> Cheers,
>
> Michael
>
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~----------~----~----~----~------~----~------~--~---

Reply via email to