axiom-developer
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Axiom-developer] Axiom cvs 040624 build error


From: Magnus Larsson
Subject: Re: [Axiom-developer] Axiom cvs 040624 build error
Date: Sat, 26 Jun 2004 20:59:01 +0200
User-agent: KMail/1.6.2

Hello David Mentre, cc: axiom-developer,

I have moved away from my linuxfromscratch systems to a regular distro, 
SUSE-9.1 in order to make my results more traceable.  Please find my comments 
below.

On Saturday 26 June 2004 13.40, you wrote:
> Magnus Larsson <address@hidden> writes:
> > This does not work:
> > I can still not build Axiom CVS 040624 on my original system using
> > gcc-3.3.1, gcl-2.7.0 ANSI, binutils 2.15.90.0.3 20040415, NPTL.  I might
> > have trashed something on this system, but I am not aware of any seroius
> > malconfiguration. (CVS 5-june-2004 does build on this system)
> > The Binutils version is the only difference I can pinpoint right now.
>
> This might pinpoint an issue with GCL. Axiom is using its own version of
> GCL (2.6.2-something) but there might be an issue with this release of
> GCL and the releases of binutils and other utilities on your system.

Ooops, I did not know, for sure, that Axiom relied on its own GCL 2.6.
Will it not be hard to maintain a separate GCL version for Axiom alone? Why 
not rely on the build platfrom to supply GCL? Well, I am sure this has been 
discussed already and I do not mind the current strategy.

>
> Yours,
> d.

SUSE 9.1, standard installation, results using Axiom CVS 040624:

SUSE-9.1 utilises GCC-3.3.3 and Binutils 2.15.90.0.1.1 20040303 (Suse Linux)

This build fails due to a GCC-3.3.3 problem with the GMP version used in Axiom 
(or GCL). Why not rely on the build platform to supply GMP?

...
aorsmul.c:44: error: conflicting types for `__gmpz_aorsmul'
aorsmul.c:39: error: previous declaration of `__gmpz_aorsmul'
...

Please refer to the suse-9.1-standard-gcc3.3.3 log attached.

This GMP fault is a known issue. I think that there are GMP patches, or at 
least a patch strategy around this problem.

===========================

SUSE 9.1 results using Axiom CVS 040624, GCC downgraded to GCC-3.3.1:

GCC-3.3.1 is compatible with the GMP code supplied. The Binutils version is 
unchanged 2.15.90.0.1.1 20040303.

However, this build fails with the same result as originaly reported when I 
started this thread.

...
making /home/magnus/usr/source/axiom/cvs-040624/axiom/int/interp/apply.clisp 
from /home/magnus/usr/source/axiom/cvs-040 
624/axiom/src/interp/apply.boot.pamphlet

>
Error: Caught fatal error [memory may be damaged]
Fast links are on: do (si::use-fast-links nil) for debugging
Error signalled by LET.
Broken at APPLY.  Type :H for Help.
BOOT>>10 
making /home/magnus/usr/source/axiom/cvs-040624/axiom/obj/linux/interp/apply.o 
from /home/magnus/usr/source/axiom /cvs-040624/axiom/int/interp/apply.clisp

>
The source 
file /home/magnus/usr/source/axiom/cvs-040624/axiom/int/interp/apply.clisp is 
not found.
9 
making 
/home/magnus/usr/source/axiom/cvs-040624/axiom/mnt/linux/autoload/apply.o 
from /home/magnus/usr/source/axiom/cvs- 040624/axiom/obj/linux/interp/apply.o
cp: cannot stat 
`/home/magnus/usr/source/axiom/cvs-040624/axiom/obj/linux/interp/apply.o': No 
such file or directory
make[3]: *** 
[/home/magnus/usr/source/axiom/cvs-040624/axiom/mnt/linux/autoload/apply.o] 
Error 1
make[3]: Leaving directory 
`/home/magnus/usr/source/axiom/cvs-040624/axiom/src/interp'
make[2]: *** [interpdir] Error 2
make[2]: Leaving directory 
`/home/magnus/usr/source/axiom/cvs-040624/axiom/src'
make[1]: *** [srcdir] Error 2
make[1]: Leaving directory `/home/magnus/usr/source/axiom/cvs-040624/axiom'
make: *** [all] Error 2
...
There are several "The source file .../int/interp/<filename> is not found" 
before the final error reference to "... int/interp/apply.clisp is not found" 
shown in the text above.
...

SUSE-9.1 is a fairly common Linux distro. (The system I normally use is not).

I do value the excellent work of the Axiom community. I hope that Axiom will 
permit using SUSE (and other distros) as a build platform when released, in 
order not to exlude SUSE users from Axiom. :-)

Conclusion?
SUSE-9.1 can not build Axiom CVS, not even after a GCC downgrade in order to 
work around the GMP problem.

A SUSE-9.1 system downgraded to GCC-3.3.1 fails with the same problem as 
originally reported, starting this thread.

I can build Axiom CVS using GCC-3.3.1 a binutils 2.14 system.

This might pinpoint an issue with GCL, as you, David, pointed out. 

If Binutils problem:
Please note, I think Binutils 2.15.90.xx is becoming more common among Linux 
distros, aiming for NPTL instead of Linuxthreads, as a thread linrary. 
Binutils 2.14 does not support NPTL. (you need Binutils 2.14.0.7 or .8 for 
that). I am not in a position to make any definitive statements regarding 
this. I am not familiar with the details of Binutils.

Best regards,

Magnus Larsson

Attachment: suse-9.1-standard-gcc3.3.3.log
Description: Text Data


reply via email to

[Prev in Thread] Current Thread [Next in Thread]