Aldor interface (was: converting sage expressions to fricas)
Bill Page
I have not been able to build it on my Debian 5.0 system for at least
the last several revisions (two or three months).
This causes some problems with installing FriCAS in Sage if one
already has Aldor installed in the same system. It might be necessary
to manually --disable-aldor at the configure stage to avoid this but
it would be nice if we didn't have to do this.
Regards,
Bill Page.
---------- Forwarded message ----------
From: MaxTheMouse <maxth...@googlemail.com>
Date: Fri, Aug 28, 2009 at 12:07 PM
Subject: [sage-devel] Re: converting sage expressions to fricas
To: sage-devel <sage-...@googlegroups.com>
> Aldor is the "second generation" alternative to the Spad compiler. It
> is not part of FriCAS because of different (non-free) license
> restrictions. The aldor interface itself is part of FriCAS but it is
> only built by default if Aldor is first separately installed on the
> same computer.
>
> I personally think that Aldor is a very important part of FriCAS
> because it is much more flexible and reliable compiler than Spad.
> Others Axiom/FriCAS users might disagree - I think primarily because
> of the licensing issues.
>
> If Aldor and the FriCAS Aldor interface is installed, then it is
> possible to use Aldor from Sage the same way as using Spad. Some
> months ago I submitted a patch to sage-devel to implement the FriCAS
> ')compile' command from the Sage axiom.py interface but I don't think
> it ever got into trac. Are you (or is anyone else) interested in this?
>
>
For fun, I got the SVN version of aldor and built it. It worked
properly for a simple test. When I tried to build fricas I got the
error as mentioned previously. I should note that I also get an error
if I run the aldor tests using 'make testaxl' so perhaps there is an
issue with my aldor installation.
Adam
leh...@bayou.uni-linz.ac.at
> Is anyone able to build the Aldor interface with a recent revision of FriCAS?
Both debian etch and lenny on amd64 work for me with aldor 1.1.0.
regards,
Franz
Bill Page
What flavor and version of Lisp are you using?
I tried again with the most recent FriCAS sources. It still fails in
the command:
make[3]: Leaving directory `/home/wspage/fricas-build/src/aldor'
echo ')lisp (compile-file
"/home/wspage/fricas-build/src/aldor/lsp/runtime.lsp" :output-file
"/home/wspage/fricas-build/src/aldor/lib/runtime.o")' >
tmp/mko_runtime.lsp
echo ')lisp (quit)' >> tmp/mko_runtime.lsp
mkdir -p ao
touch -t 199901010000 ao/.dir
ar x /home/wspage/aldor-src/aldor/install/aldor/linux/1.1.0/lib/libfoam.al
runtime.ao
mkdir -p lsp
touch -t 199901010000 lsp/.dir
aldor -flsp=lsp/runtime.lsp runtime.ao
mkdir -p lib
touch -t 199901010000 lib/.dir
DAASE=/home/wspage/fricas-build/target/i686-pc-linux
/home/wspage/fricas-build/target/i686-pc-linux/bin/AXIOMsys <
tmp/mko_runtime.lsp > tmp/mko_runtime.log
Does anyone have an idea about what the following error message in the
file 'tmp/mko_runtime.log' might mean?
>> System error:
A package error occurred on #<"FOAM-USER" package>: "Cannot use
package as it will produce a name conflict".
at the end of this email might mean?
Is this an issue with the version of GCL that I am using?
I am using an up to date 32 bit Debian 5.0 (Lenny) system on an Intel chip.
Partial build log follows. (I can send or post the complete log some
where if it will help.)
wspage@debian:~$ cat /etc/debian_version
5.0.2
wspage@debian:~$ cat /etc/issue
Debian GNU/Linux 5.0 \n \l
wspage@debian:~$ uname -a
Linux debian 2.6.26-2-686 #1 SMP Sun Jul 26 21:25:33 UTC 2009 i686 GNU/Linux
wspage@debian:~$ gcc --version
gcc (Debian 4.3.2-1.1) 4.3.2
wspage@debian:~$ which gcl
/usr/bin/gcl
wspage@debian:~$ gcl
GCL (GNU Common Lisp) 2.6.7 CLtL1 Sep 1 2008 14:01:57
Source License: LGPL(gcl,gmp), GPL(unexec,bfd,xgcl)
Binary License: GPL due to GPL'ed components: (XGCL READLINE BFD UNEXEC)
Modifications of this banner must retain notice of a compatible license
Dedicated to the memory of W. Schelter
Use (help) to get some basic information on how to use GCL.
Temporary directory for compiler files set to /tmp/
>(quit)
wspage@debian:~$ aldor -v
Aldor version 1.1.0 for LINUX(glibc-unknown)
#1 (Warning) No files! Type `aldor -help' for help.
Totals:
Time 0.0 s
Store 592 K pool, 238K alloc - 41K free - 19K gc = 178K final
wspage@debian:~/fricas-src$ svn update
...
Updated to revision 665.
wspage@debian:~/fricas-src$ cd ..
wspage@debian:~$ cd fricas-build
wspage@debian:~/fricas-build$ rm -rf *
wspage@debian:~/fricas-build$ ../fricas-src/configure
checking build system type... i686-pc-linux
checking host system type... i686-pc-linux
checking target system type... i686-pc-linux
checking for make... make
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for a BSD-compatible install... /usr/bin/install -c
checking for touch... touch
checking for mktemp... mktemp
checking for gawk... gawk
checking for gtar... no
checking for tar... tar
checking for ranlib... ranlib
checking for ar... ar
checking for latex... /usr/bin/latex
checking for makeindex... makeindex
checking for notangle... notangle
checking for noweave... noweave
checking for gcl... /usr/bin/gcl
checking Lisp implementation... GCL (GNU Common Lisp) 2.6.7 CLtL1
Sep 1 2008 14:01:57
Source License: LGPL(gcl,gmp), GPL(unexec,bfd,xgcl)
Binary License: GPL due to GPL'ed components: (XGCL READLINE BFD UNEXEC)
Modifications of this banner must retain notice of a compatible license
Dedicated to the memory of W. Schelter
Use (help) to get some basic information on how to use GCL.
Temporary directory for compiler files set to /tmp/
>
Loading /home/wspage/fricas-src/config.lisp
gcl
o
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking signal.h usability... yes
checking signal.h presence... yes
checking for signal.h... yes
checking whether sigaction is declared... yes
checking for sys/stat.h... (cached) yes
checking for unistd.h... (cached) yes
checking whether getuid is declared... yes
checking whether geteuid is declared... yes
checking whether getgid is declared... yes
checking whether getegid is declared... yes
checking whether kill is declared... yes
checking sys/socket.h usability... yes
checking sys/socket.h presence... yes
checking for sys/socket.h... yes
checking util.h usability... no
checking util.h presence... no
checking for util.h... no
checking pty.h usability... yes
checking pty.h presence... yes
checking for pty.h... yes
checking whether openpty is declared... yes
checking for openpty in -lc... no
checking for openpty in -lutil... yes
checking sys/wait.h usability... yes
checking sys/wait.h presence... yes
checking for sys/wait.h... yes
checking whether wait is declared... yes
checking whether fork is declared... yes
checking for X... libraries , headers
checking for gethostbyname... yes
checking for connect... yes
checking for remove... yes
checking for shmat... yes
checking for IceConnectionNumber in -lICE... yes
checking for XpmReadFileToImage in -lXpm... yes
checking regex.h usability... yes
checking regex.h presence... yes
checking for regex.h... yes
checking for aldor... aldor
checking for svn... svn
checking for curl... no
checking for wget... wget
configure: Aldor interface will be built.
configure: creating ./config.status
config.status: creating src/clef/Makefile
config.status: creating src/sman/Makefile
config.status: creating src/graph/Makefile
config.status: creating src/graph/Gdraws/Makefile
config.status: creating src/graph/view2D/Makefile
config.status: creating src/graph/view3D/Makefile
config.status: creating src/graph/viewAlone/Makefile
config.status: creating src/graph/viewman/Makefile
config.status: creating src/paste/Makefile
config.status: creating src/hyper/Makefile
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating src/lib/Makefile
config.status: creating src/lisp/Makefile
config.status: creating src/boot/Makefile
config.status: creating src/interp/Makefile
config.status: creating src/share/Makefile
config.status: creating src/algebra/Makefile
config.status: creating src/input/Makefile
config.status: creating src/etc/Makefile
config.status: creating src/aldor/Makefile
config.status: creating src/aldor/Makefile2
config.status: creating contrib/emacs/Makefile
config.status: creating build/scripts/document
config.status: creating config/axiom-c-macros.h
extracting list of SPAD type definitions
Type 'make' (without quotes) to build FriCAS
wspage@debian:~/fricas-build$ nohup make &
[1] 12016
wspage@debian:~/fricas-build$ nohup: ignoring input and appending
output to `nohup.out'
wspage@debian:~/fricas-build$ tail -1000 nohup.out
Added 16 pages and/or macros from ZLINDEP.pht
make[2]: Leaving directory `/home/wspage/fricas-build/src/paste'
cd aldor && make
make[2]: Entering directory `/home/wspage/fricas-build/src/aldor'
Makefile:262: domains.mk: No such file or directory
echo "domains := \\" > domains.mk
grep '^)abbrev' /home/wspage/fricas-build/src/algebra/*.spad | gawk
'{print $3,"\\"}' >> domains.mk
echo >> domains.mk
make[2]: Leaving directory `/home/wspage/fricas-build/src/aldor'
make[2]: Entering directory `/home/wspage/fricas-build/src/aldor'
svn cat https://svn.origo.ethz.ch/algebraist/trunk/aldor/lib/libax0/axiom.as
> axiom.as
echo ')lisp (load "../../../fricas-src/src/aldor/gendepap.lsp")' > mkinit.lsp
echo ')lisp (generate-init "initlist.lst")' >> mkinit.lsp
echo ')lisp (quit)' >> mkinit.lsp
echo ')lisp (load "../../../fricas-src/src/aldor/gendepap.lsp")' > mkeasy.lsp
echo ')lisp (generate-easy "easylist.lsp")' >> mkeasy.lsp
echo ')lisp (quit)' >> mkeasy.lsp
mkdir -p tmp
touch -t 199901010000 tmp/.dir
aldor -Fap=tmp/initlist.ap ../../../fricas-src/src/aldor/initlist.as
...
ar: creating al/libaxiom_ZMOD.al
aldor -Wname=axiom -Mno-abbrev -Mpreview -Y al -L AxiomLib=axiom_ZMOD
-fao=ao/ZMOD.ao ap/ZMOD.ap
ar r al/libaxiom.al ao/lang.ao ao/attrib.ao ao/boolean0.ao
ao/minimach.ao ao/subsetc.ao ao/BASTYPE.ao ao/KOERCE.ao
ao/init_OUTFORM.ao ao/SETCAT.ao ao/init_PI.ao ao/init_SINT.ao
ao/ABELSG.ao ao/init_NNI.ao ao/ABELMON.ao ao/ABELGRP.ao ao/ATFINAG.ao
ao/AGG.ao ao/AHYP.ao ao/ATCS.ao ao/ATNZDIV.ao ao/ATSHMUT.ao
ao/ATUNIKN.ao ao/CABMON.ao ao/init_LIST.ao ao/IEVALAB.ao ao/init_EQ.ao
ao/EVALAB.ao ao/HOAGG.ao ao/SGROUP.ao ao/MONOID.ao ao/SRNG.ao
ao/SRING.ao ao/A1AGG.ao ao/ARR2CAT.ao ao/ATADDVA.ao ao/ATAPPRO.ao
ao/ATARBEX.ao ao/ATARBPR.ao ao/ATCANCL.ao ao/ATCANON.ao ao/ATCUNOR.ao
ao/ATMULVA.ao ao/ATPOSET.ao ao/ATRIG.ao ao/BGAGG.ao ao/COMPAR.ao
ao/FINITE.ao ao/KONVERT.ao ao/LOGIC.ao ao/ORDSET.ao ao/init_INFORM.ao
ao/BOOLEAN.ao ao/ORDFIN.ao ao/CHAR.ao ao/CLAGG.ao ao/DIOPS.ao
ao/DIAGG.ao ao/SETAGG.ao ao/FSAGG.ao ao/CCLASS.ao ao/CFCAT.ao
ao/CHARNZ.ao ao/CHARZ.ao ao/DIFRING.ao ao/ELEMFUN.ao ao/ELTAB.ao
ao/ELTAGG.ao ao/init_SUP.ao ao/GCDDOM.ao ao/PID.ao ao/EUCDOM.ao
ao/HYPCAT.ao ao/IXAGG.ao ao/KDAGG.ao ao/init_MATRIX.ao
ao/init_VECTOR.ao ao/LINEXP.ao ao/OASGP.ao ao/OAMON.ao ao/OCAMON.ao
ao/OAMONS.ao ao/NNI.ao ao/NONE.ao ao/OAGROUP.ao ao/ORDRING.ao
ao/OINTDOM.ao ao/init_OMDEV.ao ao/OM.ao ao/init_DFLOAT.ao
ao/init_SYMBOL.ao ao/OUTFORM.ao ao/PDRING.ao ao/RCAGG.ao
ao/init_FLOAT.ao ao/REAL.ao ao/RETRACT.ao ao/SAOS.ao ao/SEXCAT.ao
ao/SPFCAT.ao ao/STEP.ao ao/TBAGG.ao ao/TRIGCAT.ao ao/TRANFUN.ao
ao/init_FR.ao ao/UFD.ao ao/URAGG.ao ao/init_UNISEG.ao ao/LIST.ao
ao/LZSTAGG.ao ao/MATCAT.ao ao/VECTCAT.ao ao/VECTOR.ao ao/MATRIX.ao
ao/PI.ao ao/SEGCAT.ao ao/SEGXCAT.ao ao/SEG.ao ao/SINT.ao ao/STREAM.ao
ao/UNISEG.ao ao/axlit.ao ao/axextend.ao ao/COMPCAT.ao ao/IDPC.ao
ao/INDE.ao ao/POLY.ao ao/ACF.ao ao/CACHSET.ao ao/KERNEL.ao ao/ES.ao
ao/GROUP.ao ao/SMP.ao ao/FS.ao ao/ACFS.ao ao/PTCAT.ao ao/POINT.ao
ao/PPCURVE.ao ao/ACPLOT.ao ao/AF.ao ao/ONECOMP.ao ao/FPC.ao
ao/TABLE.ao ao/FFIELDC.ao ao/FINRALG.ao ao/FRAMALG.ao ao/MONOGEN.ao
ao/AN.ao ao/ALGFACT.ao ao/FFCAT.ao ao/ALGFF.ao ao/ALGMANIP.ao
ao/ALGMFACT.ao ao/MONAD.ao ao/NARNG.ao ao/NAALG.ao ao/FINAALG.ao
ao/FRNAALG.ao ao/ALGPKG.ao ao/CARD.ao ao/VSPACE.ao ao/DIRPCAT.ao
ao/DIRPROD.ao ao/RMATCAT.ao ao/SMATCAT.ao ao/SQMATRIX.ao ao/ALGSC.ao
ao/ANON.ao ao/LALG.ao ao/ANTISYM.ao ao/ANY1.ao ao/OREPCAT.ao
ao/APPLYORE.ao ao/RULE.ao ao/APPRULE.ao ao/ARRAY1.ao ao/ARRAY12.ao
ao/ARRAY2.ao ao/LODOCAT.ao ao/ASSOCEQ.ao ao/SKAGG.ao ao/ASTACK.ao
ao/AUTOMOR.ao ao/BALFACT.ao ao/BRAGG.ao ao/BTCAT.ao ao/BBTREE.ao
ao/BEZOUT.ao ao/RADIX.ao ao/BINARY.ao ao/FILECAT.ao ao/FNCAT.ao
ao/FNAME.ao ao/BINFILE.ao ao/BTAGG.ao ao/BITS.ao ao/BOP1.ao
ao/BOUNDZRO.ao ao/PADICCT.ao ao/BPADIC.ao ao/CONTFRAC.ao
ao/BPADICRT.ao ao/BRILL.ao ao/BSTREE.ao ao/BTOURN.ao ao/BTREE.ao
ao/GRMOD.ao ao/GRALG.ao ao/CARTEN.ao ao/CARTEN2.ao ao/CDEN.ao
ao/CHARPOL.ao ao/CHVAR.ao ao/CINTSLPE.ao ao/QFORM.ao ao/CLIF.ao
ao/PLOT.ao ao/CLIP.ao ao/CMPLXRT.ao ao/COLOR.ao ao/init_SEGBIND.ao
ao/COMBF.ao ao/COMBINAT.ao ao/COMBOPC.ao ao/COMM.ao ao/COMMONOP.ao
ao/COMMUPC.ao ao/COMPFACT.ao ao/COMPLEX2.ao ao/COMPLPAT.ao
ao/COMPPROP.ao ao/COORDSYS.ao ao/CPIMA.ao ao/CPMATCH.ao ao/CRAPACK.ao
ao/CRFP.ao ao/CSTTOOLS.ao ao/PRIMCAT.ao ao/LFCAT.ao ao/EXPR.ao
ao/CTRIGMNP.ao ao/CVMP.ao ao/PRTITION.ao ao/SYMPOLY.ao ao/CYCLES.ao
ao/CYCLOTOM.ao ao/DLIST.ao ao/QEQUAT.ao ao/DBASE.ao ao/DBLRESP.ao
ao/DDFACT.ao ao/DECIMAL.ao ao/ORDCOMP.ao ao/DEFINTEF.ao ao/DEFINTRF.ao
ao/DEGRED.ao ao/QUAGG.ao ao/DQAGG.ao ao/DEQUEUE.ao ao/DERHAM.ao
ao/DFINTTLS.ao ao/DFSFUN.ao ao/DHMATRIX.ao ao/DIOSP.ao ao/DIRPROD2.ao
ao/DISPLAY.ao ao/DLAGG.ao ao/DLP.ao ao/OVAR.ao ao/DMP.ao ao/DPMM.ao
ao/DPMO.ao ao/DVARCAT.ao ao/DPOLCAT.ao ao/PALETTE.ao ao/SUBSPACE.ao
ao/SPACEC.ao ao/SPACE3.ao ao/DROPT.ao ao/GRIMAGE.ao ao/PARPCURV.ao
ao/PARSCURV.ao ao/PARSURF.ao ao/VIEW2D.ao ao/VIEW3D.ao ao/DRAW.ao
ao/DRAWCFUN.ao ao/DRAWCURV.ao ao/DRAWCX.ao ao/DRAWHACK.ao ao/DRAWPT.ao
ao/DROPT0.ao ao/DROPT1.ao ao/DSMP.ao ao/EAB.ao ao/EF.ao ao/EFSTRUC.ao
ao/PSCAT.ao ao/PTRANFN.ao ao/UPSCAT.ao ao/ULSCAT.ao ao/UTSCAT.ao
ao/ULSCCAT.ao ao/EFULS.ao ao/UPXSCAT.ao ao/UPXSCCA.ao ao/EFUPXS.ao
ao/ELFUTS.ao ao/EMR.ao ao/SUCH.ao ao/EP.ao ao/EQ.ao ao/EQ2.ao
ao/EQTBL.ao ao/ERROR.ao ao/ES1.ao ao/ES2.ao ao/EVALCYC.ao ao/EXIT.ao
ao/VARIABLE.ao ao/UP.ao ao/UTS.ao ao/ULS.ao ao/UPXS.ao ao/EXPUPXS.ao
ao/UPXSSING.ao ao/EXPEXPAN.ao ao/EXPR2.ao ao/EXPR2UPS.ao ao/EXPRODE.ao
ao/PSCURVE.ao ao/PLOT3D.ao ao/TUBE.ao ao/EXPRTUBE.ao ao/FACTFUNC.ao
ao/FACUTIL.ao ao/FAMONC.ao ao/FAGROUP.ao ao/FAMONOID.ao ao/FAMR2.ao
ao/FARRAY.ao ao/XF.ao ao/FAXF.ao ao/FMTC.ao ao/MINT.ao ao/MFLOAT.ao
ao/MCMPLX.ao ao/SWITCH.ao ao/FC.ao ao/FCOMP.ao ao/FCPAK1.ao
ao/FRIDEAL.ao ao/FDIVCAT.ao ao/FDIV.ao ao/FDIV2.ao ao/FEXPR.ao
ao/PF.ao ao/FF.ao ao/FFCAT2.ao ao/PRIMARR.ao ao/FFCG.ao ao/FFCGP.ao
ao/FFCGX.ao ao/FFF.ao ao/FFFG.ao ao/FFFGF.ao ao/FFHOM.ao
ao/FFINTBAS.ao ao/FFNB.ao ao/FFNBP.ao ao/FFNBX.ao ao/FFP.ao
ao/FFPOLY.ao ao/FFPOLY2.ao ao/FFSLPE.ao ao/FFX.ao ao/FGLMICPK.ao
ao/FGROUP.ao ao/FILE.ao ao/FLAGG2.ao ao/FMCAT.ao ao/LIECAT.ao
ao/OSGROUP.ao ao/ORDMON.ao ao/OFMONOID.ao ao/MAGMA.ao ao/LWORD.ao
ao/XALG.ao ao/XFALG.ao ao/XPOLYC.ao ao/XDPOLY.ao ao/XRPOLY.ao
ao/FLALG.ao ao/FLASORT.ao ao/FLOATCP.ao ao/FLOATRP.ao ao/FM.ao
ao/FM2.ao ao/FORTCAT.ao ao/FST.ao ao/FT.ao ao/SYMTAB.ao ao/FMC.ao
ao/FMFUN.ao ao/FMONOID.ao ao/FNLA.ao ao/STACK.ao ao/FOP.ao
ao/FORDER.ao ao/FORMULA.ao ao/FORMULA1.ao ao/SYMS.ao ao/FORT.ao
ao/FORTFN.ao ao/FORTRAN.ao ao/FPARFRAC.ao ao/FR.ao ao/FR2.ao
ao/FRAC2.ao ao/FRIDEAL2.ao ao/FRNAAF2.ao ao/FRUTIL.ao ao/FS2.ao
ao/FS2EXPXP.ao ao/FS2UPS.ao ao/FSAGG2.ao ao/IR.ao ao/FSCINT.ao
ao/FSERIES.ao ao/FSFUN.ao ao/FSINT.ao ao/FSPECF.ao ao/FSPRMELT.ao
ao/FSRED.ao ao/FSUPFACT.ao ao/FTEM.ao ao/FUNCTION.ao ao/FVC.ao
ao/FVFUN.ao ao/MDAGG.ao ao/MSETAGG.ao ao/MSET.ao ao/SET.ao
ao/GALFACT.ao ao/GALFACTU.ao ao/GALPOLYU.ao ao/GALUTIL.ao
ao/GAUSSFAC.ao ao/GB.ao ao/GBEUCLID.ao ao/GBF.ao ao/GBINTERN.ao
ao/GCDBAS.ao ao/GCNAALG.ao ao/GDMP.ao ao/GENEEZ.ao ao/GENMFACT.ao
ao/GENPGCD.ao ao/GENUFACT.ao ao/GENUPS.ao ao/GHENSEL.ao ao/MODMONOM.ao
ao/GMODPOL.ao ao/GOPT.ao ao/GOPT0.ao ao/GOSPER.ao ao/RPOLCAT.ao
ao/PSETCAT.ao ao/GPOLSET.ao ao/GRAY.ao ao/GRDEF.ao ao/HDP.ao
ao/HDMP.ao ao/GROEBSOL.ao ao/GSERIES.ao ao/GSTBL.ao ao/TSETCAT.ao
ao/GTSET.ao ao/UFPS.ao ao/GUESS.ao ao/GUESSAN.ao ao/GUESSF.ao
ao/GUESSF1.ao ao/GUESSINT.ao ao/GUESSP.ao ao/HACKPI.ao ao/HASHTBL.ao
ao/HB.ao ao/PRQAGG.ao ao/HEAP.ao ao/HELLFDIV.ao ao/HEUGCD.ao
ao/HEXADEC.ao ao/IALGFACT.ao ao/IAN.ao ao/IARRAY1.ao ao/IARRAY2.ao
ao/IBACHIN.ao ao/IBATOOL.ao ao/IBITS.ao ao/IBPTOOLS.ao ao/ICARD.ao
ao/ICDEN.ao ao/IDEAL.ao ao/IDPAG.ao ao/IDPAM.ao ao/IDPO.ao
ao/IDPOAM.ao ao/IDPOAMS.ao ao/IFAMON.ao ao/IFARRAY.ao ao/IPF.ao
ao/IFF.ao ao/IIARRAY2.ao ao/ILIST.ao ao/IMATLIN.ao ao/IMATQF.ao
ao/IVECTOR.ao ao/IMATRIX.ao ao/INBFF.ao ao/INCRMAPS.ao ao/INEP.ao
ao/INFINITY.ao ao/INFORM.ao ao/INFORM1.ao ao/INFPROD0.ao ao/INFSP.ao
ao/INMODGCD.ao ao/INNMFACT.ao ao/INPRODFF.ao ao/INPRODPF.ao
ao/INPSIGN.ao ao/INTABL.ao ao/INTAF.ao ao/INTALG.ao ao/INTBIT.ao
ao/INTCAT.ao ao/INTEF.ao ao/INTFACT.ao ao/INTG0.ao ao/INTHEORY.ao
ao/INTHERAL.ao ao/INTHERTR.ao ao/INTPAF.ao ao/INTPM.ao ao/INTRAT.ao
ao/INTRET.ao ao/INTRF.ao ao/INTRVL.ao ao/INTSLPE.ao ao/INTTOOLS.ao
ao/LAUPOL.ao ao/INTTR.ao ao/INVLAPLA.ao ao/IPADIC.ao ao/IPRNTPK.ao
ao/IR2.ao ao/IR2F.ao ao/IROOT.ao ao/IRREDFFX.ao ao/IRRF2F.ao
ao/PERMCAT.ao ao/PERM.ao ao/IRSN.ao ao/RSETCAT.ao ao/SFRTCAT.ao
ao/IRURPK.ao ao/ISTRING.ao ao/ISUMP.ao ao/REF.ao ao/ISUPS.ao
ao/ITAYLOR.ao ao/ITUPLE.ao ao/ITFUN2.ao ao/ITFUN3.ao ao/ITRIGMNP.ao
ao/JORDAN.ao ao/KAFILE.ao ao/KERNEL2.ao ao/KOVACIC.ao ao/LA.ao
ao/LAPLACE.ao ao/LAZM3PK.ao ao/LEADCDET.ao ao/LPOLY.ao ao/PBWLB.ao
ao/XPBWPOLY.ao ao/LEXP.ao ao/NSMP.ao ao/RGCHAIN.ao ao/SREGSET.ao
ao/LEXTRIPK.ao ao/LF.ao ao/LGROBP.ao ao/LIB.ao ao/LIE.ao ao/LIMITPS.ao
ao/LIMITRF.ao ao/LINDEP.ao ao/LIST2.ao ao/LIST2MAP.ao ao/LIST3.ao
ao/LMDICT.ao ao/LMOPS.ao ao/LO.ao ao/LODEEF.ao ao/LODO.ao ao/LODO1.ao
ao/LODO2.ao ao/LODOF.ao ao/LODOOPS.ao ao/LPEFRAC.ao ao/LSMP.ao
ao/LSMP1.ao ao/LSPP.ao ao/LSQM.ao ao/M3D.ao ao/MAPHACK1.ao
ao/MAPHACK2.ao ao/MAPHACK3.ao ao/MAPPKG1.ao ao/MAPPKG2.ao
ao/MAPPKG3.ao ao/MATCAT2.ao ao/MATLIN.ao ao/MATSTOR.ao ao/MCALCFN.ao
ao/MCDEN.ao ao/MDDFACT.ao ao/MESH.ao ao/MFINFACT.ao ao/MHROWRED.ao
ao/MKBCFUNC.ao ao/MKCHSET.ao ao/MKFLCFN.ao ao/MKFUNC.ao ao/MKRECORD.ao
ao/MKUCFUNC.ao ao/MLIFT.ao ao/MLO.ao ao/MMAP.ao ao/MMLFORM.ao
ao/MODFIELD.ao ao/MODMON.ao ao/MODOP.ao ao/MODRING.ao ao/MOEBIUS.ao
ao/MONADWU.ao ao/MONOTOOL.ao ao/MPC2.ao ao/MPC3.ao ao/MPCPF.ao
ao/MPOLY.ao ao/MPRFF.ao ao/MRATFAC.ao ao/MRCAT.ao ao/MRING.ao
ao/MRF2.ao ao/MSYSCMD.ao ao/MTHING.ao ao/MTSCAT.ao ao/MULDEP.ao
ao/MULTFACT.ao ao/MULTSQFR.ao ao/NASRING.ao ao/NCEP.ao ao/NCNTFRAC.ao
ao/NCODIV.ao ao/NEWTON.ao ao/NFINTBAS.ao ao/NLINSOL.ao ao/NODE1.ao
ao/NONE1.ao ao/NORMMA.ao ao/NORMPK.ao ao/NORMRETR.ao ao/NPCOEF.ao
ao/NREP.ao ao/NSUP.ao ao/NSUP2.ao ao/NTPOLFN.ao ao/NTSCAT.ao
ao/NUMERIC.ao ao/NUMFMT.ao ao/NUMODE.ao ao/NUMQUAD.ao ao/NUMTUBE.ao
ao/OC.ao ao/QUATCAT.ao ao/QUAT.ao ao/OCT.ao ao/OCTCT2.ao
ao/ODECONST.ao ao/ODEEF.ao ao/ODEINT.ao ao/ODEPAL.ao ao/ODEPRIM.ao
ao/ODEPRRIC.ao ao/ODERAT.ao ao/ODERED.ao ao/ODESYS.ao ao/ODETOOLS.ao
ao/ODP.ao ao/ODVAR.ao ao/ODPOL.ao ao/ODR.ao ao/OMCONN.ao ao/OMENC.ao
ao/OMDEV.ao ao/OMERRK.ao ao/OMERR.ao ao/OMEXPR.ao ao/OMLO.ao
ao/OMPKG.ao ao/OMSAGG.ao ao/OMSERVER.ao ao/ONECOMP2.ao ao/OP.ao
ao/OPQUERY.ao ao/ORDCOMP2.ao ao/ORDFUNS.ao ao/OREPCTO.ao ao/ORESUP.ao
ao/OREUP.ao ao/ORTHPOL.ao ao/OSI.ao ao/OUT.ao ao/OWP.ao ao/PADE.ao
ao/PADEPAC.ao ao/PADIC.ao ao/PADICRAT.ao ao/PADICRC.ao ao/PAN2EXPR.ao
ao/PARPC2.ao ao/PARSC2.ao ao/PARSU2.ao ao/PARTPERM.ao ao/PATLRES.ao
ao/PATMATCH.ao ao/PATRES2.ao ao/PATTERN1.ao ao/PATTERN2.ao ao/PCOMP.ao
ao/PDECOMP.ao ao/TREE.ao ao/PENDTREE.ao ao/PERMAN.ao ao/PERMGRP.ao
ao/PFBR.ao ao/PFBRU.ao ao/PFO.ao ao/PFOQ.ao ao/PFOTOOLS.ao ao/PFR.ao
ao/PFRPAC.ao ao/PGCD.ao ao/PGE.ao ao/PGROEB.ao ao/PICOERCE.ao
ao/PINTERP.ao ao/PINTERPA.ao ao/PLEQN.ao ao/PLOT1.ao ao/PLOTTOOL.ao
ao/PMASS.ao ao/PMASSFS.ao ao/PMDOWN.ao ao/PMFS.ao ao/PMINS.ao
ao/PMKERNEL.ao ao/PMLSAGG.ao ao/PMPLCAT.ao ao/PMPRED.ao ao/PMPREDFS.ao
ao/PMQFCAT.ao ao/PMSYM.ao ao/PMTOOLS.ao ao/PNTHEORY.ao ao/POLTOPOL.ao
ao/POLUTIL.ao ao/POLY2.ao ao/POLY2UP.ao ao/POLYCATQ.ao ao/POLYLIFT.ao
ao/POLYROOT.ao ao/PR.ao ao/PREASSOC.ao ao/PRIMARR2.ao ao/PRIMELT.ao
ao/PRIMES.ao ao/PRINT.ao ao/PRODUCT.ao ao/PRS.ao ao/PSETPK.ao
ao/PSEUDLIN.ao ao/PSQFR.ao ao/PTFUNC2.ao ao/PTPACK.ao ao/PUSHVAR.ao
ao/PWFFINTB.ao ao/QALGSET.ao ao/QCMPACK.ao ao/QFCAT2.ao ao/QUAT2.ao
ao/QUATCT2.ao ao/QUEUE.ao ao/RADFF.ao ao/RADUTIL.ao ao/RANDSRC.ao
ao/RATFACT.ao ao/RATRET.ao ao/RCFIELD.ao ao/RDEEF.ao ao/RDEEFS.ao
ao/RDETR.ao ao/RDETRS.ao ao/RDIST.ao ao/RDIV.ao ao/REAL0.ao
ao/REAL0Q.ao ao/REALSOLV.ao ao/RRCC.ao ao/ROIRC.ao ao/RECLOS.ao
ao/RECOP.ao ao/REDORDER.ao ao/REGSET.ao ao/REP.ao ao/REP1.ao
ao/REP2.ao ao/REPDB.ao ao/REPSQ.ao ao/RESLATC.ao ao/RESRING.ao
ao/RESULT.ao ao/RETSOL.ao ao/RF.ao ao/RFDIST.ao ao/RFFACT.ao
ao/RFFACTOR.ao ao/RINTERP.ao ao/RMATRIX.ao ao/RMCAT2.ao ao/ROMAN.ao
ao/RSDCMPK.ao ao/RSETGCD.ao ao/RULECOLD.ao ao/RULESET.ao ao/RURPK.ao
ao/SAE.ao ao/SAEFACT.ao ao/SAERFFC.ao ao/SCACHE.ao ao/SCPKG.ao
ao/SDVAR.ao ao/SDPOL.ao ao/SEG2.ao ao/SEGBIND.ao ao/SEGBIND2.ao
ao/SETMN.ao ao/SEXOF.ao ao/SFORT.ao ao/SFQCMPK.ao ao/SFRGCD.ao
ao/SGCF.ao ao/SHDP.ao ao/SHP.ao ao/SIGNEF.ao ao/SIGNRF.ao ao/SIMPAN.ao
ao/SMITH.ao ao/SMTS.ao ao/SNTSCAT.ao ao/SOLVEFOR.ao ao/SOLVERAD.ao
ao/SOLVESER.ao ao/SOLVETRA.ao ao/SORTPAK.ao ao/SPECOUT.ao
ao/SPLNODE.ao ao/SPLTREE.ao ao/SRDCMPK.ao ao/STBL.ao ao/STINPROD.ao
ao/STNSR.ao ao/STREAM1.ao ao/STREAM2.ao ao/STREAM3.ao ao/STRTBL.ao
ao/STTAYLOR.ao ao/STTF.ao ao/STTFNC.ao ao/SUBRESP.ao ao/SUTS.ao
ao/SULS.ao ao/SUMFS.ao ao/SUMRF.ao ao/SUP2.ao ao/SUPFRACF.ao
ao/SUPXS.ao ao/SYMFUNC.ao ao/SYSSOLP.ao ao/TABLEAU.ao ao/TABLBUMP.ao
ao/TANEXP.ao ao/TBCMPPK.ao ao/TEMUTL.ao ao/TESTAUX.ao ao/TESTCNT.ao
ao/TESTUNIT.ao ao/TEX.ao ao/TEX1.ao ao/TEXTFILE.ao ao/TOOLSIGN.ao
ao/TOPSP.ao ao/TRIGMNIP.ao ao/TRIMAT.ao ao/TRMANIP.ao ao/TS.ao
ao/TUBETOOL.ao ao/TUPLE.ao ao/TWOFACT.ao ao/TYPE.ao ao/UDPO.ao
ao/UDVO.ao ao/UFPS1.ao ao/ULS2.ao ao/ULSCONS.ao ao/UNIFACT.ao
ao/UNISEG2.ao ao/UP2.ao ao/UPCDEN.ao ao/UPDECOMP.ao ao/UPDIVP.ao
ao/UPMP.ao ao/UPOLYC2.ao ao/UPSQFREE.ao ao/UPXS2.ao ao/UPXSCONS.ao
ao/UTS2.ao ao/UTSODE.ao ao/UTSODETL.ao ao/VECTOR2.ao ao/VIEW.ao
ao/VIEWDEF.ao ao/VOID.ao ao/WEIER.ao ao/WFFINTBS.ao ao/WP.ao
ao/WUTSET.ao ao/XEXPPKG.ao ao/XPOLY.ao ao/XPR.ao ao/YSTREAM.ao
ao/ZDSOLVE.ao ao/ZLINDEP.ao ao/ZMOD.ao
ar: creating al/libaxiom.al
rm ao/.dir
make[3]: Leaving directory `/home/wspage/fricas-build/src/aldor'
echo ')lisp (compile-file
"/home/wspage/fricas-build/src/aldor/lsp/runtime.lsp" :output-file
"/home/wspage/fricas-build/src/aldor/lib/runtime.o")' >
tmp/mko_runtime.lsp
echo ')lisp (quit)' >> tmp/mko_runtime.lsp
mkdir -p ao
touch -t 199901010000 ao/.dir
ar x /home/wspage/aldor-src/aldor/install/aldor/linux/1.1.0/lib/libfoam.al
runtime.ao
mkdir -p lsp
touch -t 199901010000 lsp/.dir
aldor -flsp=lsp/runtime.lsp runtime.ao
mkdir -p lib
touch -t 199901010000 lib/.dir
DAASE=/home/wspage/fricas-build/target/i686-pc-linux
/home/wspage/fricas-build/target/i686-pc-linux/bin/AXIOMsys <
tmp/mko_runtime.lsp > tmp/mko_runtime.log
test -f lib/runtime.o
make[2]: *** [lib/runtime.o] Error 1
make[2]: Leaving directory `/home/wspage/fricas-build/src/aldor'
make[1]: *** [all-aldor] Error 2
make[1]: Leaving directory `/home/wspage/fricas-build/src'
make: *** [all-src] Error 2
wspage@debian:~/fricas-build$
wspage@debian:~/fricas-build/src/aldor$ cat tmp/mko_runtime.log
GCL (GNU Common Lisp) 2.6.7 CLtL1 Sep 1 2008 14:01:57
Source License: LGPL(gcl,gmp), GPL(unexec,bfd,xgcl)
Binary License: GPL due to GPL'ed components: (XGCL READLINE BFD UNEXEC)
Modifications of this banner must retain notice of a compatible license
Dedicated to the memory of W. Schelter
Use (help) to get some basic information on how to use GCL.
Temporary directory for compiler files set to /tmp/
openServer result -2
FriCAS (AXIOM fork) Computer Algebra System
Version: FriCAS 2009-07-20
Timestamp: Friday August 28, 2009 at 17:09:58
-----------------------------------------------------------------------------
Issue )copyright to view copyright notices.
Issue )summary for a summary of useful system commands.
Issue )quit to leave FriCAS and return to shell.
-----------------------------------------------------------------------------
Using local database
/home/wspage/fricas-build/target/i686-pc-linux/algebra/compress.daase..
Using local database
/home/wspage/fricas-build/target/i686-pc-linux/algebra/interp.daase..
Using local database
/home/wspage/fricas-build/target/i686-pc-linux/algebra/operation.daase..
Using local database
/home/wspage/fricas-build/target/i686-pc-linux/algebra/category.daase..
Using local database
/home/wspage/fricas-build/target/i686-pc-linux/algebra/browse.daase..
(1) ->
>> System error:
A package error occurred on #<"FOAM-USER" package>: "Cannot use
package as it will produce a name conflict".
; (IN-PACKAGE "FOAM-USER" ...) is being compiled.
;;; The form (IN-PACKAGE "FOAM-USER" :USE '("FOAM" "LISP")) was not
evaluated successfully.
;;; You are recommended to compile again.
No FASL generated.
Value = NIL
(1) -> wspage@debian:~/fricas-build/src/aldor$
---
Regards,
Bill Page.
leh...@bayou.uni-linz.ac.at
> What flavor and version of Lisp are you using?
regards,
Franz
Bill Page
Thanks! I can confirm that the Aldor interface builds properly using
wspage@debian:~$ sbcl
This is SBCL 1.0.18.debian, an implementation of ANSI Common Lisp.
---
Installed via apt-get from the standard Debian Lenny repositories.
Conclusion: Don't use the Debian Lenny binary distribution of GCL to
build FriCAS with the Aldor interface.
BTW, has anyone ever successfully built the FriCAS and the Aldor
interface using ECL?
Regards,
Bill Page.
Ralf Hemmecke
I've tried to build FriCAS with Aldor with GCL and failed on Ubuntu
9.04. I don't know about the status of GCL and don't even know whether I
should invest time to make the Aldor-Interface working also with GCL?
Isn't SBCL better?
Ralf
Bill Page
On Mon, Aug 31, 2009 at 6:10 AM, you wrote:
>
> Hi Bill,
>
> I've tried to build FriCAS with Aldor with GCL and failed on Ubuntu
> 9.04. I don't know about the status of GCL and don't even know whether
> I should invest time to make the Aldor-Interface working also with GCL?
> Isn't SBCL better?
>
That is a good question. Yes, probably SBCL is better. SBCL does seem
to work for me. GCL might be more or less dead but it seems that it is
still the default lisp for FriCAS. Maybe ECL would be a good
replacement for GCL since ECL is derived from the same base code and
appears to have a very active developer. And the Sage project is now
using ECL to support Maxima.
I am sure that the Aldor-interface used to build with GCL. But rather
than invest time to continue to support it maybe it would be better to
try to make sure that the Aldor interface will build with ECL.
Regards,
Bill Page.
Ralf Hemmecke
> than invest time to continue to support it maybe it would be better to
> try to make sure that the Aldor interface will build with ECL.
OK, I'll look at that as soon as possible. Which ECL version should I take?
Didn't I once have problems with building FriCAS on ECL?
http://www.mail-archive.com/fricas...@googlegroups.com/msg01304.html
And there was a problem with the big array in aldor-combinat...
http://groups.google.at/group/fricas-devel/browse_thread/thread/b71cc6df59864b0b
But I don't know whether that is ECL specific and still existing.
Ralf
Bill Page
>
>> I am sure that the Aldor-interface used to build with GCL. But rather
>> than invest time to continue to support it maybe it would be better to
>> try to make sure that the Aldor interface will build with ECL.
>
> OK, I'll look at that as soon as possible. Which ECL version should I take?
>
Probably it would be best to work with the most recently released
version if possible. I think 9.7.1 is the most recent release:
but from the sage-devel list I know there have been some significant
changes especially in the gmp memory management in the last few weeks.
So I think one should expect a new release soon.
> Didn't I once have problems with building FriCAS on ECL?
> http://www.mail-archive.com/fricas...@googlegroups.com/msg01304.html
>
0.9j is now quite old. Note: There was also a version numbering change
in the mean time.
> And there was a problem with the big array in aldor-combinat...
> http://groups.google.at/group/fricas-devel/browse_thread/thread/b71cc6df59864b0b
> But I don't know whether that is ECL specific and still existing.
>
I think Waldek regularly builds FriCAS using ECL. I hope he will comment.
Regards,
Bill Page.
Aleksej Saushev
>> I am sure that the Aldor-interface used to build with GCL. But rather
>> than invest time to continue to support it maybe it would be better to
>> try to make sure that the Aldor interface will build with ECL.
>
> OK, I'll look at that as soon as possible. Which ECL version should I take?
>
> Didn't I once have problems with building FriCAS on ECL?
> http://www.mail-archive.com/fricas...@googlegroups.com/msg01304.html
I maintain FriCAS package and use mostly ECL.
--
CE3OH...
Bill Page
What version(s) have ECL have you used? What operating system:
Debian?, SuSE?, Windows?
Regards,
Bill Page.
Waldek Hebisch
>
> I think Waldek regularly builds FriCAS using ECL. I hope he will comment.
>
ATM I am not up to date concerning ECL. The newset ECL is 9.8.4.
I did not try this version, but Juan Jose Garcia-Ripoll
(the ECL developer) tried and FriCAS builds fine. This was
ECL 9.8.4 on 64 bit Debian with Unicode version of ECL
(in the past Unicode version of ECL had problems, so this
indicates that the problems are worked out).
Some versions of ECL have problems, for example build with
9.7.1 did not work (this is fixed in later versions). After
fixing build problem with 9.7.1 I got a few extra testsute
failures. I still have to find out if the testsuite failures
persist in newer ECL versions.
Let me remark that recently ECL got significantly better at
optimization. As byproduct some bugs may show up. For
example 9.7.1 problem was in an old optimization which
apparently for long time was unused and only in 9.7.1
got used and the problem surfaced.
--
Waldek Hebisch
heb...@math.uni.wroc.pl
Waldek Hebisch
>
> Bill Page wrote:
> >
> > I think Waldek regularly builds FriCAS using ECL. I hope he will comment.
> >
>
> ATM I am not up to date concerning ECL.
I have now tried ECL-9.8.4. On 64-bit Fedora 9 FriCAS revision 666
builds fine using this version of ECL. There are a few extra
testsuite failures compared to sbcl, but I would say that
results looks reasonably good.
--
Waldek Hebisch
heb...@math.uni.wroc.pl
Aleksej Saushev
> On Mon, Aug 31, 2009 at 12:26 PM, Aleksej Saushev wrote:
>> I maintain FriCAS package and use mostly ECL.
>>
>
> What version(s) have ECL have you used?
9.8.4 is the last one.
> What operating system: Debian?, SuSE?, Windows?
My primary platforms are NetBSD and FreeBSD, other reports here:
http://mail-index.netbsd.org/pkgsrc-bulk/
--
CE3OH...
Bill Page
I just completed a full compile of FriCAS rev. 666 from source with
ECL 9.8.4 including the Aldor interface. It finished with no problems
and seems to run fine.
So what is failing at the moment seems to be building the Aldor
interface from a *cached lisp* distribution created with:
../fricas/src/scripts/mkdist.sh --copy_lisp
Ref. http://sagetrac.org/sage_trac/ticket/4461
Building FriCAS in Sage using the spkg from:
http://sagetrac.org/sage_trac/ticket/6517
when Aldor is previously installed, fails when it attempts to build
the Aldor interface.
The error: " undefined reference to `log' " when building 'cliques.as'
is cured by adding '-lm' to
CLIQUEOPTS=-mno-abbrev -mno-mactext -laldor -lm -fx
in src/aldor/Makefile.in
I don't know why '-lm' isn't also necessary when building FriCAS
outside of Sage. It must have something to so with the load library
environment inside the Sage "shell".
But after including '-lm' it fails again with the following error:
touch -t 199901010000 lib/.dir
DAASE=/home/wspage/sage-4.1.1/spkg/build/fricas-1.0.7.p0/build-dir/target/i686-pc-linux
/home/wspage/sage-4.1.1/spkg/build/fricas-1.0.7.p0/build-dir/target/i686-pc-linux/bin/AXIOMsys
< tmp/mko_runtime.lsp > tmp/mko_runtime.log
test -f lib/runtime.fas
echo ')lisp (compile-file
"/home/wspage/sage-4.1.1/spkg/build/fricas-1.0.7.p0/build-dir/src/aldor/lsp/lang.lsp"
:output-file "/home/wspage/sage-4.1.1/spkg/build/fricas-1.0.7.p0/build-dir/src/aldor/lib/lang.fas")'
> tmp/mko_lang.lsp
echo ')lisp (quit)' >> tmp/mko_lang.lsp
# The .ao file will be built via Makefile2.
aldor -flsp=lsp/lang.lsp ao/lang.ao
#1 (Fatal Error) Could not open file `ao/lang.ao'.
make[2]: *** [lsp/lang.lsp] Error 1
make[2]: Leaving directory
`/home/wspage/sage-4.1.1/spkg/build/fricas-1.0.7.p0/build-dir/src/aldor'
make[1]: *** [all-aldor] Error 2
make[1]: Leaving directory
`/home/wspage/sage-4.1.1/spkg/build/fricas-1.0.7.p0/build-dir/src'
make: *** [all-src] Error 2
***********************************************************
Failed to make FriCAS.
***********************************************************
wspage@debian:~/sage-4.1.1/spkg/build/fricas-1.0.7.p0$
Regards,
Bill Page.
On Mon, Aug 31, 2009 at 11:01 AM, Ralf Hemmecke wrote:
>
>> I am sure that the Aldor-interface used to build with GCL. But rather
>> than invest time to continue to support it maybe it would be better to
>> try to make sure that the Aldor interface will build with ECL.
>
> OK, I'll look at that as soon as possible. Which ECL version should I take?
>
> ...
Ralf Hemmecke
Bill, could you send me the exact list of commands to arrive at this
error. Maybe you even have the full log of this 'make'.
Are you sure that you have the files lang.as etc. from the Aldor.org
server? Actually these files could be distributed (maybe as a separate
spkg because of license issues) so that there would be no need for
internet access at build time.
Ralf
Bill Page
I am sorry, I don't the logs to send but if you have any problems with
the instructions below, then I can reproduce and send them later.
Assuming that you already have Aldor and Sage installed, the commends:
$ cd ~/sage-4.1.1
$ wget http://www.mediafire.com/file/im5zd201mh0/fricas-1.0.7.p0.spkg
$ ./sage -f fricas-1.0.7.spkg
Produces the error: " undefined reference to `log' ". (about 15 minutes)
After the failure, follow the instructions printed by Sage to enter
the Sage "shell" - the environment in which Sage and all it's spkg's
run. As indicated 'cd' to the fricas-1.0.7 directory inside Sage.
Now changing
CLIQUEOPTS=-mno-abbrev -mno-mactext -laldor -lm -fx
in the file './src/src/aldor/Makefile.in' and re-running the biuld via
./spkg-install
produces the error I showed in my previous email.
Except for the " undefined reference to `log' " message, the same
error occurs outside of Sage. To reproduce do this:
First install ECL 9.8.4, then build FriCAS from source using ecl in
the usual way. E.g
$ svn update ~/fricas
$ mkdir ~/fricas-build
$ cd ~/fricas-build
$ ../fricas/configure --with-lisp=ecl
After it finishes run the command:
$ ../fricas/src/scripts/mkdist.sh --copy_lisp
The result will be a new sub-directory named 'dist' in your build
directory. This directory is identical to the 'src' directory in the
Sage fricas-1.0.7 directory (except a little newer). Copy the whole
sub-directory somewhere, e.g.
$ cp -r dist ~/fricas-dist
$ cd ~/fricas-dist
Now build FriCAS in the usual way
$ ./configure --with-lisp=ecl
$ make
It fails at:
echo ')lisp (quit)' >> tmp/mko_lang.lsp
# The .ao file will be built via Makefile2.
aldor -flsp=lsp/lang.lsp ao/lang.ao
#1 (Fatal Error) Could not open file `ao/lang.ao'.
The file '~/fricas-dist/src/aldor/tmp/mko_lang.lsp' refers to 'lsp/lang.lsp':
$ cat ~/fricas-dist/src/aldor/tmp/mko_lang.lsp
)lisp (compile-file "/home/wspage/fricas-dist/src/aldor/lsp/lang.lsp"
:output-file "/home/wspage/fricas-dist/src/aldor/lib/lang.fas")
)lisp (quit)
wspage@debian:~/fricas-dist/src/aldor$
---
but the lsp directory only contains 'runtime.lsp'
$ ls -l /home/wspage/fricas-dist/src/aldor/lsp
total 392
-rw-r--r-- 1 wspage wspage 395221 2009-09-02 21:48 runtime.lsp
Although the 'lang.as' file is present:
$ cd ~/fricas-dist
$ find . -name lang.as
./src/aldor/lang.as
I don't think there was any problem with access to svn for these
files. But maybe in the future it would be possible to just distribute
the cached lisp files generated by Aldor the same way as those
generated by FriCAS? I don't see how that would violate any licenses.
Please let me know if you would still like me to produce and send the log.
Regards,
Bill Page.
Ralf Hemmecke
On 09/03/2009 02:48 PM, Bill Page wrote:
> Ralf,
>
> I am sorry, I don't the logs to send but if you have any problems with
> the instructions below, then I can reproduce and send them later.
>
> Assuming that you already have Aldor and Sage installed, the commends:
>
> $ cd ~/sage-4.1.1
> $ wget http://www.mediafire.com/file/im5zd201mh0/fricas-1.0.7.p0.spkg
> $ ./sage -f fricas-1.0.7.spkg
>
> Produces the error: " undefined reference to `log' ". (about 15 minutes)
Your wget does not quite work that way, but I got the file anyway from
there to my ~/scratch directory.
Then I issued "sage -f fricas-1.0.7.spkg" inside ~/scratch. sage is in
my PATH.
That seems to extract and then starts doing something, but without
success. I have sage 4.1. Do I really need 4.1.1?
Is it relevant whether or not I run on a 32bit system?
I don't have ecl on my system. Shouldn't the fricas spkg just use the
lisp provided by sage? Or do I have to install ECL?
Ralf
...
fricas-1.0.7.p0/src/src/ChangeLog.bu
fricas-1.0.7.p0/src/confignotes.tex
Finished extraction
****************************************************
Host system
uname -a:
Linux woodpecker 2.6.28-15-generic #49-Ubuntu SMP Tue Aug 18 18:40:08
UTC 2009 i686 GNU/Linux
****************************************************
****************************************************
GCC Version
gcc -v
Using built-in specs.
Target: i486-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu
4.3.3-5ubuntu4' --with-bugurl=file:///usr/share/doc/gcc-4.3/README.Bugs
--enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr
--enable-shared --with-system-zlib --libexecdir=/usr/lib
--without-included-gettext --enable-threads=posix --enable-nls
--with-gxx-include-dir=/usr/include/c++/4.3 --program-suffix=-4.3
--enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc
--enable-mpfr --enable-targets=all --with-tune=generic
--enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu
--target=i486-linux-gnu
Thread model: posix
gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4)
****************************************************
checking build system type... i686-pc-linux
checking host system type... i686-pc-linux
checking target system type... i686-pc-linux
checking for make... make
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for a BSD-compatible install... /usr/bin/install -c
checking for touch... touch
checking for mktemp... mktemp
checking for gawk... gawk
checking for gtar... no
checking for tar... tar
checking for gpatch... no
checking for patch... patch
checking for ranlib... ranlib
checking for ar... ar
checking for latex... /usr/bin/latex
checking for makeindex... makeindex
checking for notangle... notangle
checking for noweave... noweave
checking Lisp implementation... ECL (Embeddable Common-Lisp) 9.4.1
Copyright (C) 1984 Taiichi Yuasa and Masami Hagiya
Copyright (C) 1993 Giuseppe Attardi
Copyright (C) 2000 Juan J. Garcia-Ripoll
ECL is free software, and you are welcome to redistribute it
under certain conditions; see file 'Copyright' for details.
Type :h for Help. Top level.
>
;;; Loading
"/home/hemmecke/software/sage/spkg/build/fricas-1.0.7.p0/src/config.lisp"
Filesystem error with pathname #P"SYS:cmp.NEWEST".
Either
1) the file does not exist, or
2) we are not allow to access the file, or
3) the pathname points to a broken symbolic link.
Broken at SI:BYTECODES.No restarts available.
Broken at SI:BYTECODES. File:
#P"/home/hemmecke/software/sage-4.1-linux-Ubuntu_9.04-i686-Linux/spkg/build/fricas-1.0.7.p0/src/config.lisp"
(Form #1)
>>
configure: error: Unable to determine Lisp flavor
***********************************************************
Failed to configure FriCAS.
***********************************************************
real 0m5.143s
user 0m0.736s
sys 0m0.548s
sage: An error occurred while installing fricas-1.0.7.p0
Please email sage-devel http://groups.google.com/group/sage-devel
explaining the problem and send the relevant part of
of /home/hemmecke/software/sage/install.log. Describe your computer,
operating system, etc.
If you want to try to fix the problem, yourself *don't* just cd to
/home/hemmecke/software/sage/spkg/build/fricas-1.0.7.p0 and type 'make'.
Instead type "/home/hemmecke/software/sage/sage -sh"
in order to set all environment variables correctly, then cd to
/home/hemmecke/software/sage/spkg/build/fricas-1.0.7.p0
(When you are done debugging, you can type "exit" to leave the
subshell.)
Bill Page
On Thu, Sep 3, 2009 at 5:32 PM, Ralf Hemmecke wrote:
>
> On 09/03/2009 02:48 PM, Bill Page wrote:
>> I am sorry, I don't the logs to send but if you have any problems with
>> the instructions below, then I can reproduce and send them later.
>>
>> Assuming that you already have Aldor and Sage installed, the commends:
>>
>> $ cd ~/sage-4.1.1
>> $ wget http://www.mediafire.com/file/im5zd201mh0/fricas-1.0.7.p0.spkg
>> $ ./sage -f fricas-1.0.7.spkg
>>
>> Produces the error: " undefined reference to `log' ". (about 15 minutes)
>
> Your wget does not quite work that way, but I got the file anyway from
> there to my ~/scratch directory.
>
Ok, sorry. I guess it is on some kind of "sharing" site that forces
you to read annoying advertisements or something. I don't know why the
developer did not put it directly on the sage site.
> Then I issued "sage -f fricas-1.0.7.spkg" inside ~/scratch. sage is in
> my PATH.
>
> That seems to extract and then starts doing something, but without
> success. I have sage 4.1. Do I really need 4.1.1?
>
I don't think so. I think 4.1 should be ok. But for sure you do need a
version of Sage where ECL is the default lisp.
> Is it relevant whether or not I run on a 32bit system?
>
No, I don't think so.
> I don't have ecl on my system. Shouldn't the fricas spkg just use the
> lisp provided by sage?
Yes. Your log shows that it found "ECL (Embeddable Common-Lisp) 9.4.1".
> Or do I have to install ECL?
>
No, it is not necessary to install ECL separately to install FriCAS in Sage.
But as Nils pointed out, ECL 9.4.1 is now also a little old. I think
Waldek mentioned earlier that he had a problem building FriCAS with
9.4.1 or similar version. I had forgotten that for other reasons I
had already upgraded the ECL version in version 4.1.1 of Sage that I
have installed on my system. You should definitely ECL also upgrade
via
sage -i -s http://sage.math.washington.edu/home/ghitza/ecl-9.8.4.spkg
> ...
Regards,
Bill Page.
Ralf Hemmecke
and then again
sage -f fricas-1.0.7.spkg
But, Bill, different from your error message
> Produces the error: " undefined reference to `log' ". (about 15 minutes)
(which appeared after about 45 min --- interesting to me since it seemed
that everything was rebuild. See
http://www.risc.uni-linz.ac.at/people/hemmecke/pub/fricas/fricas-1.0.7.p0.spkg.log.bz2
for the full log. Can somebody check whether this compilation should
happen this way?)
Anyway, my error message was different!
The first error already appears here!
==============
make[2]: Leaving directory
`/home/hemmecke/software/sage-4.1-linux-Ubuntu_9.04-i686-Linux/spkg/build/fricas-1.0.7.p0/build-dir/src/paste'
cd aldor && make
make[2]: Entering directory
`/home/hemmecke/software/sage-4.1-linux-Ubuntu_9.04-i686-Linux/spkg/build/fricas-1.0.7.p0/build-dir/src/aldor'
Makefile:262: domains.mk: No such file or directory
echo "domains := \\" > domains.mk
grep '^)abbrev'
/home/hemmecke/software/sage/spkg/build/fricas-1.0.7.p0/build-dir/src/algebra/*.spad
| gawk '{print $3,"\\"}' >> domains.mk
grep:
/home/hemmecke/software/sage/spkg/build/fricas-1.0.7.p0/build-dir/src/algebra/*.spad:
No such file or directory
echo >> domains.mk
==============
It tries to create domains.mk, but this file will be basically empty,
because the spkg does not contain *.spad files.
I see the *.spad.pamphlet files, but spad files are not created.
The relevant part in aldor/Makefile.in is
domains.mk:
echo "domains := \\" > $@
grep '^)abbrev' $(spaddir)/*.spad | $(AWK) '{print $$3,"\\"}' >> $@
echo >> $@
This was written having in mind that the fricas build appears before and
thus the .spad files would be in the above location.
So that must be fixed before going on.
It seems that I first have to study what happens when the .spkg file is
created.
==================================================================
Anyway, before I go on, let me ask some stupid questions.
1) What is the license of the .spkg file?
2) Since the whole stuff under src/aldor is just for two things
A) create libaxiom.al
B) create runtime files from some aldor.org's *.as files.
Why not just distribute libaxiom.al in the spkg?
That file is machine independent. And the problem with the .spad
files would be gone. (Together with 1 hour of build time on the
user's machine.)
3) Runtime (and perhaps also libaxiom.al) from 2) contain code under the
Aldor Public license 2.0. So I would suggest to make two packages.
A) FriCAS (which explicitly does not build the Aldor interface).
(mBSD-licenced)
B) libaxiom.al plus code to create the runtime files (APL2-licenced)
Of course B) depends on A), but I believe there is a way to say this
in an .spkg file.
I must say, I rather like to go for 3).
Any comments?
Ralf
Bill Page
On Fri, Sep 4, 2009 at 5:32 PM, Ralf Hemmecke wrote:
>
> So, I've done
>
> sage -i -s http://sage.math.washington.edu/home/ghitza/ecl-9.8.4.spkg
>
> and then again
>
> sage -f fricas-1.0.7.spkg
>
> But, Bill, different from your error message
>
>> Produces the error: " undefined reference to `log' ". (about 15 minutes)
>
> (which appeared after about 45 min --- interesting to me since it seemed
> that everything was rebuild. See
>
> http://www.risc.uni-linz.ac.at/people/hemmecke/pub/fricas/fricas-1.0.7.p0.spkg.log.bz2
>
> for the full log. Can somebody check whether this compilation should
> happen this way?)
>
The log looks right to me up until you get the error. I am surprised
that you say this took 45 minutes but I don't think "everything was
rebuilt" since I do not see any spad compiler output - just output for
the list compiler.
> Anyway, my error message was different!
> The first error already appears here!
> ...
It is possible that I just missed this earlier error. You do also get
the "undefined reference ..." message just a little later.
Ah, I see. The building the Aldor interface needs the .spad files.
Yes, I think it could be arranged that the dist directory also contain
the .spad files. Maybe another option on the makedist script?
> It seems that I first have to study what happens when the .spkg file is
> created.
>
See
../fricas/src/scripts/mkdist.sh --copy_lisp
Ref. http://sagetrac.org/sage_trac/ticket/4461
> ==================================================================
>
> Anyway, before I go on, let me ask some stupid questions.
>
> 1) What is the license of the .spkg file?
fricas...spkg is an optional package for Sage so I don't think there
is any restriction on the license other than what is required by
FriCAS.
> 2) Since the whole stuff under src/aldor is just for two things
> A) create libaxiom.al
> B) create runtime files from some aldor.org's *.as files.
> Why not just distribute libaxiom.al in the spkg?
> That file is machine independent. And the problem with the .spad
> files would be gone. (Together with 1 hour of build time on the
> user's machine.)
Ok.
> 3) Runtime (and perhaps also libaxiom.al) from 2) contain code under the
> Aldor Public license 2.0. So I would suggest to make two packages.
> A) FriCAS (which explicitly does not build the Aldor interface).
> (mBSD-licenced)
> B) libaxiom.al plus code to create the runtime files (APL2-licenced)
> Of course B) depends on A), but I believe there is a way to say this
> in an .spkg file.
>
> I must say, I rather like to go for 3).
>
> Any comments?
>
+1
I also very much like your option 3)
Regards,
Bill Page.
Ralf Hemmecke
>
> Produces the error: " undefined reference to `log' ". (about 15 minutes)
>
> After the failure, follow the instructions printed by Sage to enter
> the Sage "shell" - the environment in which Sage and all it's spkg's
> run. As indicated 'cd' to the fricas-1.0.7 directory inside Sage.
>
> Now changing
>
> CLIQUEOPTS=-mno-abbrev -mno-mactext -laldor -lm -fx
>
> in the file './src/src/aldor/Makefile.in' and re-running the biuld via
>
> ./spkg-install
>
> produces the error I showed in my previous email.
I guess the missing '-lm' is due to the fact that in the shell started
by 'sage -sh' the variable CC is set to gcc.
That changes the behaviour of the Aldor compiler. Usually (if CC is not
set) it calls "unicl" (a program that comes with aldor) and that program
(if I am not totally wrong) uses
https://svn.origo.ethz.ch/algebraist/trunk/aldor/aldor/src/aldor.conf
to figure out the options for the C compiler. And there I see a line...
lib-extra = m
Maybe src/aldor/Makefile.in should rather contain
====BEGIN
cliques: cliques.as
unset CC && $(ALDOR) $(CLIQUEOPTS) $<
====END
But don't bother too much. I'm currently trying to figure out how to
distribute libaxiom.al directly without building it on the user side.
Ralf
William Stein
>
>> $ ./sage -f fricas-1.0.7.spkg
>>
>> Produces the error: " undefined reference to `log' ". (about 15 minutes)
>>
>> After the failure, follow the instructions printed by Sage to enter
>> the Sage "shell" - the environment in which Sage and all it's spkg's
>> run. As indicated 'cd' to the fricas-1.0.7 directory inside Sage.
>>
>> Now changing
>>
>> CLIQUEOPTS=-mno-abbrev -mno-mactext -laldor -lm -fx
>>
>> in the file './src/src/aldor/Makefile.in' and re-running the biuld via
>>
>> ./spkg-install
>>
>> produces the error I showed in my previous email.
>
> I guess the missing '-lm' is due to the fact that in the shell started
> by 'sage -sh' the variable CC is set to gcc.
William
>
> That changes the behaviour of the Aldor compiler. Usually (if CC is not
> set) it calls "unicl" (a program that comes with aldor) and that program
> (if I am not totally wrong) uses
> https://svn.origo.ethz.ch/algebraist/trunk/aldor/aldor/src/aldor.conf
> to figure out the options for the C compiler. And there I see a line...
>
> lib-extra = m
>
> Maybe src/aldor/Makefile.in should rather contain
> ====BEGIN
> cliques: cliques.as
> unset CC && $(ALDOR) $(CLIQUEOPTS) $<
> ====END
>
> But don't bother too much. I'm currently trying to figure out how to
> distribute libaxiom.al directly without building it on the user side.
>
> Ralf
>
> >
>
William Stein
Associate Professor of Mathematics
University of Washington
http://wstein.org