Interesting idea: we could probably replace the fortran.spkg by a
gcc.spkg and have it compile gcc, gfortran on systems where this is
needed. The size of the gcc spkg would roughly be the same as the
current fortran spkg.
On bsd, I compiled gfortran-4.4.6 from source, compiled the Sage LAPACK
wit
On Thu, Jan 26, 2012 at 1:28 PM, Jeroen Demeyer wrote:
> On 2012-01-26 21:52, Jeroen Demeyer wrote:
>> I might look into this. I will try a proof-of-concept test on bsd.
> Proof-of-concept successful on bsd. Compiled gcc-4.4.6 and compiled
> PARI with it, PARI passes all tests.
>
> I'd like to t
On 2012-01-26 21:52, Jeroen Demeyer wrote:
> I might look into this. I will try a proof-of-concept test on bsd.
Proof-of-concept successful on bsd. Compiled gcc-4.4.6 and compiled
PARI with it, PARI passes all tests.
I'd like to try an OS X 10.7 machine if anybody can give me access to
such a ma
On 2012-01-26 21:52, Christopher Swenson wrote:
> 5) why don't you choose clang + llvm?
Because that's what Apple did and it's clearly not working.
--
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...@googl
Ah, my bad. I misinterpreted the original intent as "requiring" GCC as part
of building Sage from source.
Carry on.
:)
--Christopher
On Thu, Jan 26, 2012 at 15:57, William Stein wrote:
> On Thu, Jan 26, 2012 at 12:52 PM, Christopher Swenson
> wrote:
> > -1 for distributing our own version o
On Thu, Jan 26, 2012 at 12:52 PM, Christopher Swenson
wrote:
> -1 for distributing our own version of gcc.
>
> As someone who has been peripherally involved with this sort of thing at
> Google, here are some downsides:
>
> 1) several hours of extra compiling and testing (a full boostrap build of
>
-1 for distributing our own version of gcc.
As someone who has been peripherally involved with this sort of thing at
Google, here are some downsides:
1) several hours of extra compiling and testing (a full boostrap build of
GCC can be very painful, and running every test can take a very long time
I might look into this. I will try a proof-of-concept test on bsd.
--
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
Hi,
Earlier today I was arguing that we need to support Xcode 4.x, etc.,
in the context of the PARI bugs.
I'm sitting here with a grad student with a solid Mac running OS X
10.6.8, and trying to get XCode 3.x on it is HELL.
None of our Apple ID's work for the Developer network, etc. We can't
fin
