rvaug...@gmail.com wrote:
I was able to make sage-4.3.3 just fine on a machine running 32-bit
Scientific Linux 5.4.
But on a machine running 64-bit Scientific Linux, the make failed.
Details in /usr/share/sage-4.3.3/spkg/build/prereq-0.7/config.log:
configure:2974: gcc conftest.c >&5
/tmp/ccdsUkwr.s: Assembler messages:
/tmp/ccdsUkwr.s:8: Error: suffix or operands invalid for `push'
/tmp/ccdsUkwr.s:9: Error: suffix or operands invalid for `push'
/tmp/ccdsUkwr.s:11: Error: suffix or operands invalid for `push'
/tmp/ccdsUkwr.s:13: Error: suffix or operands invalid for `pop'
/tmp/ccdsUkwr.s:14: Error: suffix or operands invalid for `pop'
configure:2978: $? = 1
configure:3016: result:
configure: failed program was:
| /* confdefs.h. */
| #define PACKAGE_NAME "Sage"
| #define PACKAGE_TARNAME "sage"
| #define PACKAGE_VERSION "x.y.z"
| #define PACKAGE_STRING "Sage x.y.z"
| #define PACKAGE_BUGREPORT "sage-de...@googlegroups.com"
| #define PACKAGE "sage"
| #define VERSION "x.y.z"
| /* end confdefs.h. */
|
| int
| main ()
| {
|
| ;
| return 0;
| }
configure:3022: error: in `/usr/share/sage-4.3.3/spkg/build/
prereq-0.7':
configure:3025: error: C compiler cannot create executables
See `config.log' for more details.
When I Googled the error message, I saw this:
x86-64 has a different assembly langauge and a different ABI.
"On x86-64 your program should be written more like
xorl %%edi, %%edi
call f1
movl %0, %%edi
movl %%eax, %%esi
call f2
with clobbers where appropriate. "
Is this the case?
Will SAGE-4.3.3 not make successfully on a 64-bit machine due to
different assembly langauge/different ABI
The 'prereq' script which gives the error is basically just trying to compile a
program with
int main()
{
return 0
}
No specific options are used to force a 32 or 64-bit compile.
This indicates a pretty fundamental gcc installation issue to me.
Can you create a 'hello world' C program and get that to execute?
It looks to me like you are trying to build Sage as root, given the path. It's
generally bad practice to use the root account for anything that can be done
without being root. Everyone types the wrong command some times. The
implications for doing this as root as more severe. I'd personally suggest you
don't build as root, though that is unlikely to be the cause of the problem.
To me, the gcc installation looks broken, which is why I suggest you create a
hello world.
Dave
--
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to
sage-support+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/sage-support
URL: http://www.sagemath.org
To unsubscribe from this group, send email to sage-support+unsubscribegooglegroups.com or
reply to this email with the words "REMOVE ME" as the subject.
