Re: [sage-devel] Re: build failure of 4.3.5 on OS X 10.6.3

2010-04-05 Thread Dr. David Kirkby
William Stein wrote: On Sat, Apr 3, 2010 at 7:56 AM, mhampton > wrote: Ok, moving /usr/local/ "fixed" the problem. I wish I knew what I did that caused it though. I've been building Sage since version 1.4 on there without problems. It's sort of tota

Re: [sage-devel] Re: build failure of 4.3.5 on OS X 10.6.3

2010-04-04 Thread Dr. David Kirkby
William Stein wrote: On Sat, Apr 3, 2010 at 12:22 AM, Dima Pasechnik wrote: On Apr 3, 12:31 am, mhampton wrote: I'll try downloading it a second time, although I don't think its corrupted because I copied that tar file to 3 other computers and all their installs went fine. I don't think I'v

Re: [sage-devel] Re: build failure of 4.3.5 on OS X 10.6.3

2010-04-03 Thread William Stein
On Sat, Apr 3, 2010 at 7:56 AM, mhampton wrote: > Ok, moving /usr/local/ "fixed" the problem. I wish I knew what I did > that caused it though. I've been building Sage since version 1.4 on > there without problems. > It's sort of totally obvious to point this out, but perhaps you installed som

[sage-devel] Re: build failure of 4.3.5 on OS X 10.6.3

2010-04-03 Thread mhampton
Ok, moving /usr/local/ "fixed" the problem. I wish I knew what I did that caused it though. I've been building Sage since version 1.4 on there without problems. Thanks for the help, Marshall On Apr 3, 3:13 am, William Stein wrote: > On Sat, Apr 3, 2010 at 12:22 AM, Dima Pasechnik wrote: > > >

Re: [sage-devel] Re: build failure of 4.3.5 on OS X 10.6.3

2010-04-03 Thread William Stein
On Sat, Apr 3, 2010 at 12:22 AM, Dima Pasechnik wrote: > > > On Apr 3, 12:31 am, mhampton wrote: >> I'll try downloading it a second time, although I don't think its >> corrupted because I copied that tar file to 3 other computers and all >> their installs went fine. >> >> I don't think I've ever

[sage-devel] Re: build failure of 4.3.5 on OS X 10.6.3

2010-04-03 Thread Dima Pasechnik
On Apr 3, 12:31 am, mhampton wrote: > I'll try downloading it a second time, although I don't think its > corrupted because I copied that tar file to 3 other computers and all > their installs went fine. > > I don't think I've ever used Fink or Macports on the computer causing > problems.  I'm n

Re: [sage-devel] Re: build failure of 4.3.5 on OS X 10.6.3

2010-04-02 Thread Dr. David Kirkby
mhampton wrote: I'll try downloading it a second time, although I don't think its corrupted because I copied that tar file to 3 other computers and all their installs went fine. I don't think I've ever used Fink or Macports on the computer causing problems. I'm not sure how to "move /usr/local

[sage-devel] Re: build failure of 4.3.5 on OS X 10.6.3

2010-04-02 Thread mhampton
I'll try downloading it a second time, although I don't think its corrupted because I copied that tar file to 3 other computers and all their installs went fine. I don't think I've ever used Fink or Macports on the computer causing problems. I'm not sure how to "move /usr/local out of the way" in

[sage-devel] Re: build failure of 4.3.5 on OS X 10.6.3

2010-04-02 Thread John H Palmieri
On Apr 2, 9:19 am, William Stein wrote: > On Fri, Apr 2, 2010 at 9:16 AM, mhampton wrote: > > > Can anyone help with this?  I upgraded to 10.6.3, started over, and > > things crash in the same place as before - towards the end of building > > freetype.  Any ideas?? > > I can report that to help w

Re: [sage-devel] Re: build failure of 4.3.5 on OS X 10.6.3

2010-04-02 Thread William Stein
On Fri, Apr 2, 2010 at 9:16 AM, mhampton wrote: > > Can anyone help with this?  I upgraded to 10.6.3, started over, and > things crash in the same place as before - towards the end of building > freetype.  Any ideas?? I can report that to help with this I upgraded to 10.6.3 (on bsd.math), then di

[sage-devel] Re: build failure of 4.3.5 on OS X 10.6.3

2010-04-02 Thread mhampton
Can anyone help with this? I upgraded to 10.6.3, started over, and things crash in the same place as before - towards the end of building freetype. Any ideas?? -Marshall On Mar 31, 6:08 am, mhampton wrote: > I had no problem on linux or a mac running 10.5.  But on my 10.6.2 I > get this: > >