Thanks for all responses
Complete config.log can be found here:
www.physics.rutgers.edu/~rvaughn/config.log
Appended is an excerpt.
Also, in compiling "Hello, world" (as both root and a normal user) I
receive:
[root]# g++ -Wall hello.cc -o hello
/tmp/ccDiEsut.s: Assembler messages:
/tmp/ccDiEsut.s:10: Error: suffix or operands invalid for `push'
/tmp/ccDiEsut.s:38: Error: suffix or operands invalid for `push'
/tmp/ccDiEsut.s:55: Error: suffix or operands invalid for `push'
/tmp/ccDiEsut.s:79: Error: suffix or operands invalid for `push'
/tmp/ccDiEsut.s:81: Error: suffix or operands invalid for `push'
/tmp/ccDiEsut.s:85: Error: suffix or operands invalid for `push'
/tmp/ccDiEsut.s:94: Error: suffix or operands invalid for `pop'
/tmp/ccDiEsut.s:95: Error: suffix or operands invalid for `pop'
where the contents of hello.cc is:
#include <iostream>
int
main ()
{
std::cout << "Hello, world!\n";
return 0;
}
The same "Hello world" program compiles and runs just fine on 32-bit
Scientific Linux 5.4.
I've read where it's said that x86-64 has a different assembly
language and a different ABI.
I would be very interested in hearing from someone who has
successfully made SAGE
on a 64-bit version of Linux.
-Richard Vaughn
================= excerpt from config.log:
============================
configure:2952: checking for C compiler default output file name
configure:2974: gcc conftest.c >&5
/tmp/ccPnMtbv.s: Assembler messages:
/tmp/ccPnMtbv.s:8: Error: suffix or operands invalid for `push'
/tmp/ccPnMtbv.s:9: Error: suffix or operands invalid for `push'
/tmp/ccPnMtbv.s:11: Error: suffix or operands invalid for `push'
/tmp/ccPnMtbv.s:13: Error: suffix or operands invalid for `pop'
/tmp/ccPnMtbv.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.4/spkg/build/
prereq-0.7':
configure:3025: error: C compiler cannot create executables
See `config.log' for more details.
==========================================================
On Mar 24, 8:04 am, "Dr. David Kirkby" <david.kir...@onetel.net>
wrote:
> rvaug...@gmail.com wrote:
> > Brand-new (3/20/10) 4.3.4 version of SAGE; ran make
> > on my Scientific Linux 32-bit Scientific Linux PC.
> > make took a long time, but succeeded.
>
> > Took the same brand-new (3/20/10) 4.3.4 version of SAGE, ran make
> > on my Scientific Linux 64-bit 5.4 server.
>
> > There, make fails. Excerpt from install.log:
> > -------------------------------------------------------------------------------------------------------------
> > checking for C compiler default output file name...
> > configure: error: in `/usr/share/sage-4.3.4/spkg/build/prereq-0.7':
>
> Just as a general point, it is inadvisable to use the root account for
> anything
> that does not require root privileges. The fact this is under /usr suggests
> you
> are doing that.
>
> See, for example:
>
> http://tldp.org/LDP/lame/LAME/linux-admin-made-easy/root-account.html
> where it says:
>
> ------------
> While "root", type commands carefully and double-check them before pressing
> return. Sign off from the "root" account as soon as you have accomplished the
> task you signed on for.
> ----------------
>
> There are loads of part of Sage which delete files. Consider the implications
> if
> there was a bug in one of them. By avoiding the root account, you reduce the
> chance of any damage occurring to the system.
>
> > configure: error: C compiler cannot create executables
> > See `config.log' for more details.
>
> It looks like your C compiler is broken in some way, as all that line of the
> configure script does is tries to create a program that just returns 0 -
> something like
>
> int main()
> {
> return 0;
>
> }
>
> If that is failing, something is seriously amiss. It would help if you posted
> the output of config.log.
>
> It's possible you will find the problem goes away if you don't use the root
> account - it is quite normal for root to have different settings from normal
> users.
>
> 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.
