Subject: Maxima encountered a Lisp error on start up
From: Nicolas FRANCOIS
Date: Tue, 16 Feb 2010 13:05:08 +0100
Le Sun, 14 Feb 2010 19:35:54 +0000 (GMT),
Leo Butler <l.butler at ed.ac.uk> a ?crit :
> Nicolas,
> A good place to start is to tell us the information from
>
> build_info();
(%i1) build_info();
Maxima version: 5.17.1
Maxima build date: 14:9 7/13/2009
host type: i686-pc-linux-gnu
lisp-implementation-type: GNU Common Lisp (GCL)
lisp-implementation-version: GCL 2.6.7
> Assuming I've guessed this information correctly...
> There are two related problems which seem to have caught many
> Ubuntu packages out. The first is that Ubuntu made a decision to
> enforce a security policy at the kernel level in Karmic. The
> security policy in question is to strictly enforce the aliasing
> rules in C. My understading of the situation is that GCL, which
> your Maxima is using, is caught out here. You'll find many projects
> have been caught out (search for 'strict aliasing'), a big reason
> behind the disappointment that is karmic.
OK, I'll check the Ubuntu forum. Maybe some geek will fix the GCL
problem, or bring a package with another Lisp interpreter.
Many thanks, Leo.
\bye
--
Nicolas FRANCOIS | /\
http://nicolas.francois.free.fr | |__|
X--/\\
We are the Micro$oft. _\_V
Resistance is futile.
You will be assimilated. darthvader penguin