On Dec 1, 2:10 pm, François Bissey f.r.bis...@massey.ac.nz wrote:
On Wed, 02 Dec 2009 04:17:50 strogdon wrote:
Hey Francois. I too thought that perhaps the spkg supplied flags would
override any changes with custom flags. However the custom flags seem
to be appended to the spkg provided
On Dec 2, 2:28 pm, François Bissey f.r.bis...@massey.ac.nz wrote:
On Thu, 03 Dec 2009 08:03:44 strogdon wrote: So, it would appear that it is
not the CFLAGS but whether CFLAGS has
been set to something. The no-strict-aliasing is suspiciously missing.
The documentation I have on gcc 4.3.4
? Gentoo custom flags for
32 bit architectures do not seem to have this build problem. On an
amd64 laptop I have, the CFLAGS setting
CFLAGS=-march=k8 -O2 -pipe
also results in a sage that fails.
Steve
On Nov 5, 2:32 pm, strogdon strog...@d.umn.edu wrote:
I'm building sage 4.2 on an amd64 machine
On my Gentoo box I unpacked the subject tarball, changed to the sage
directory and did a make with the results:
gcc version 4.1.2 (Gentoo 4.1.2 p1.0.2)
RHOMES= []
DEBUG= True
Setting RHOMES
]
dortmund.de wrote:
On Apr 23, 4:52 pm, strogdon [EMAIL PROTECTED] wrote:
Hi,
On my Gentoo box I unpacked the subject tarball, changed to the sage
directory and did a make with the results:
gcc version 4.1.2 (Gentoo 4.1.2 p1.0.2
