The problem is now fixed with the latest gcc/g++ in Ubuntu Karmic.
On Sep 10, 12:48 am, Dan Drake wrote:
> I installed an Ubuntu Karmic virtual machine to see how Sage compiles
> there...and right now, it doesn't.
>
> I've tried on a 64-bit and 32-bit VM, with between 768 and about 1250 MB
> of
A quick fix I used was to change OPTFLAGS=-O3 in PARI's get_cc script to
OPTFLAGS=-O1. I wrote down the specific steps here: <
http://thesweeheng.wordpress.com/2009/08/28/building-sage-4-1-1-on-fedora-11/>.
Hope that helps.
Swee Heng
On Thu, Sep 10, 2009 at 11:17 PM, William Stein wrote:
>
> On
William Stein wrote:
> On Thu, Sep 10, 2009 at 12:48 AM, Dan Drake wrote:
>> I installed an Ubuntu Karmic virtual machine to see how Sage compiles
>> there...and right now, it doesn't.
>>
>> I've tried on a 64-bit and 32-bit VM, with between 768 and about 1250 MB
>> of RAM allocated to the VM, an
On Thu, Sep 10, 2009 at 12:48 AM, Dan Drake wrote:
> I installed an Ubuntu Karmic virtual machine to see how Sage compiles
> there...and right now, it doesn't.
>
> I've tried on a 64-bit and 32-bit VM, with between 768 and about 1250 MB
> of RAM allocated to the VM, and it consistently fails whil
I tried the compilation on an Arch Linux VM with gcc 4.4.1 and it worked
fine. So this is something related to Ubuntu's and Fedora's gcc
packages.
Dan
--
--- Dan Drake
- http://mathsci.kaist.ac.kr/~drake
---
signature.asc
Description: Digital signature
Hi Dan,
On Thu, Sep 10, 2009 at 5:48 PM, Dan Drake wrote:
> Can anyone else confirm (or perhaps even fix) this?
Jaap Spies reported the same error when compiling Sage 4.1.2.alpha0 on
32-bit Fedora 11. See
http://groups.google.com/group/sage-devel/browse_thread/thread/2ea99a973a54581c/41944c
