aldor build, cont
Bertfried Fauser
I have compiled now fricas (without aldor support) even if a second try failed
(so I am still confused)
patch didn't worked for me (error in line 55) so I substitured by hand
the lined you
provided for domains.mk
The compilation worked so fare fine, and even parts of the aldor support were
compiled, then a certain switch seems to irritate the compiler, any hint?
Sorry for all this mess and buzzing, but I am just not experieced with
these tools.
Ciao
BF.
--
% PD Dr Bertfried Fauser
% Research Fellow, School of Computer Science, Univ. of Birmingham
% Honorary Associate, University of Tasmania
% Privat Docent: University of Konstanz, Physics Dept
<http://www.uni-konstanz.de>
% contact |-> URL : http://clifford.physik.uni-konstanz.de/~fauser/
% Phone : +49 1520 9874517
Added 32 pages and/or macros from WUTSET.pht
Added 78 pages and/or macros from XPBWPOLY.pht
Added 28 pages and/or macros from XPOLY.pht
Added 30 pages and/or macros from XPR.pht
Added 56 pages and/or macros from ZDSOLVE.pht
Added 16 pages and/or macros from ZLINDEP.pht
make[2]: Leaving directory `/home/fauser/fricas-1.0.7/build-dir/src/paste'
cd aldor && make
make[2]: Entering directory `/home/fauser/fricas-1.0.7/build-dir/src/aldor'
echo ')lisp (load "../../../src/aldor/gendepap.lsp")' > mkinit.lsp
echo ')lisp (generate-init "initlist.lst")' >> mkinit.lsp
echo ')lisp (quit)' >> mkinit.lsp
echo ')lisp (load "../../../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 ../../../src/aldor/initlist.as
sed -e 's/\([->A-Za-z0-9\\]\+\)/|\1|/g' tmp/initlist.ap > initlist.ap
DAASE=/home/fauser/fricas-1.0.7/build-dir/target/i686-suse-linux
/home/fauser/fricas-1.0.7/build-dir/target/i686-suse-linux/bin/AXIOMsys
< mkeasy.lsp > tmp/mkeasy.log
test -f easylist.lsp
mkdir -p init_ap
touch -t 199901010000 init_ap/.dir
mkdir -p ap
touch -t 199901010000 ap/.dir
mkdir -p gendeps
touch -t 199901010000 gendeps/.dir
DAASE=/home/fauser/fricas-1.0.7/build-dir/target/i686-suse-linux
/home/fauser/fricas-1.0.7/build-dir/target/i686-suse-linux/bin/AXIOMsys
< mkinit.lsp > tmp/mkinit.log
test -f initlist.lst
sed -e 's/^/initaxiom /' initlist.lst > libaxiom.lst
for i in lang; do echo "lang $i" >> libaxiom.lst; done
for i in minimach boolean0 attrib; do echo "base $i" >>
libaxiom.lst; done
for i in subsetc; do echo "base $i" >> libaxiom.lst; done
for i in ; do echo "axiom $i" >> libaxiom.lst; done
for i in axextend axlit; do echo "aldorext $i" >> libaxiom.lst; done
aldor -mno-abbrev -mno-mactext -laldor -fx -dTRACE
../../../src/aldor/cliques.ascc1: error: unrecognized command line
option "-fwritable-strings"
#1 (Fatal Error) C compile failed. Command was: unicl
-I/usr/local/aldor/linux/1.0.3/include -c cliques.c
#1 (Warning) Removing file `cliques.c'.
make[2]: *** [cliques] Error 1
make[2]: Leaving directory `/home/fauser/fricas-1.0.7/build-dir/src/aldor'
make[1]: *** [all-aldor] Error 2
make[1]: Leaving directory `/home/fauser/fricas-1.0.7/build-dir/src'
make: *** [all-src] Error 2
fauser@moby:~/fricas-1.0.7/build-dir>
Ralf Hemmecke
This also goes to ald...@aldor.org because the issue seems to be
connected to an aldor compiler problem. The orginal thread is
http://groups.google.com/group/fricas-devel/browse_thread/thread/967c7862de93b8b9
No problem with your asking for help... If you have trouble that might
also be a deficiency of the system. So any feedback is welcome.
You should, however, give more information of your system.
> patch didn't worked for me (error in line 55) so I substitured by hand
> the lined you
> provided for domains.mk
Why? You should send the error messages you see on your screen. Only
then I get a clue what the problem might have been. Just "didn't work"
tells me nothing.
> The compilation worked so fare fine, and even parts of the aldor support were
> compiled, then a certain switch seems to irritate the compiler, any hint?
Arrrrrhhhhhh. That is an ugly one.
../../../src/aldor/cliques.ascc1: error: unrecognized command line
option "-fwritable-strings"
#1 (Fatal Error) C compile failed. Command was: unicl
-I/usr/local/aldor/linux/1.0.3/include -c cliques.c
#1 (Warning) Removing file `cliques.c'.
Have you ever been able to compile a simple aldor file to an executable?
---- sometest.as
#include "aldor"
#include "aldorio"
stdout << "This is a simple test." << newline;
---- end sometest.as
aldor -fx -laldor -c args='-lm' sometest.as
./sometest
Should output the text above.
This -fwritable-strings could be connected to $ALDORROOT/include/aldor.conf.
Could you send that file to me together with the result of the commands
'uname -a' and 'gcc -v'.
Mine you find here: http://sage.math.washington.edu/home/hemmecke/pub/
Also look into the aldor-l archive there once was a discussion about
writable-strings.
http://www.aldor.org/pipermail/aldor-l/2007-June/000638.html
http://www.aldor.org/pipermail/aldor-l/2007-November/000788.html
It's so unfortunate that Aldor is no longer developed and it hasn't yet
been released under a truely open source licence. As you can see on the
mailing list there wasn't any support from Aldor.org since July 2008. :-(
Ralf
Bertfried Fauser
> You should, however, give more information of your system.
fauser@moby:~> uname -a
Linux moby 2.6.16.21-0.25-smp #1 SMP Tue Sep 19 07:26:15 UTC 2006 i686
i686 i386 GNU/Linux
fauser@moby:~> gcc -v
Using built-in specs.
Target: i586-suse-linux
Configured with: ../configure --enable-threads=posix --prefix=/usr
--with-local-prefix=/usr/local --infodir=/usr/share/info
--mandir=/usr/share/man --libdir=/usr/lib --libexecdir=/usr/lib
--enable-languages=c,c++,objc,fortran,java,ada
--enable-checking=release
--with-gxx-include-dir=/usr/include/c++/4.1.0 --enable-ssp
--disable-libssp --enable-java-awt=gtk --enable-gtk-cairo
--disable-libjava-multilib --with-slibdir=/lib --with-system-zlib
--enable-shared --enable-__cxa_atexit --enable-libstdcxx-allocator=new
--without-system-libunwind --with-cpu=generic --host=i586-suse-linux
Thread model: posix
gcc version 4.1.0 (SUSE Linux)
[patch]
> Why? You should send the error messages you see on your screen.
I do possibly not know properly how to use patch, anythow, after copying
the lines fro domains.mk by hand into Makefile.in it worked well.
> Have you ever been able to compile a simple aldor file to an executable?
>
> ---- sometest.as
> #include "aldor"
> #include "aldorio"
> stdout << "This is a simple test." << newline;
> ---- end sometest.as
>
> aldor -fx -laldor -c args='-lm' sometest.as
> ./sometest
>
> Should output the text above.
But does:
fauser@moby> aldor -fx -laldor -c args='-lm' sometest.as
cc1: error: unrecognized command line option "-fwritable-strings"
#1 (Fatal Error) C compile failed. Command was: unicl -lm
-I/usr/local/aldor/linux/1.0.3/include -c sometest.c
#1 (Warning) Removing file `sometest.c'.
> This -fwritable-strings could be connected to $ALDORROOT/include/aldor.conf.
>
> Could you send that file to me together with the result of the commands
> 'uname -a' and 'gcc -v'.
>
> Mine you find here: http://sage.math.washington.edu/home/hemmecke/pub/
OK, I have changed my aldor.conf against yours and the test aldor file
compiles and if I execute it it prints the desired text. So my
aldor.conf seems to be outdated :-(
Its lunch break at the conference and I have not time to run another
compilation of fricas
now, but the aldor issue seems to be solved by now, hope so at least.
Thank you very much
leh...@bayou.uni-linz.ac.at
On Wed, Sep 30, 2009 at 12:17:37PM +0200, Ralf Hemmecke wrote:
> Have you ever been able to compile a simple aldor file to an executable?
I am having a similar problem here on ubuntu 8.04, 32bit.
(A year ago it worked)
> aldor -fx -laldor -c args='-lm' sometest.as
sh: gcc32: not found
#1 (Fatal Error) C compile failed. Command was: unicl -lm
-I/homes/lehner/usr/local/aldor/linux/1.0.3/include -c sometest.c
#1 (Warning) Removing file sometest.c'.
what is gcc32? Debian at least does not know about it.
> 'uname -a'
Linux xdf40 2.6.24-24-generic #1 SMP Sat Aug 22 01:06:14 UTC 2009 i686 GNU/Linux
> 'gcc -v'.
Using built-in specs.
Target: i486-linux-gnu
Configured with: ../src/configure -v
--enable-languages=c,c++,fortran,objc,obj-c++,treelang --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.2 --program-suffix=-4.2
--enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc
--enable-mpfr --enable-targets=all --enable-checking=release
--build=i486-linux-gnu --host=i486-linux-gnu --target=i486-linux-gnu
Thread model: posix
gcc version 4.2.4 (Ubuntu 4.2.4-1ubuntu4)
regards,
Franz
Ralf Hemmecke
> sh: gcc32: not found
> #1 (Fatal Error) C compile failed. Command was: unicl -lm
> -I/homes/lehner/usr/local/aldor/linux/1.0.3/include -c sometest.c
> #1 (Warning) Removing file sometest.c'.
>
> what is gcc32? Debian at least does not know about it.
gcc32 is a *manually* configurable way to choose your c compiler.
There was a time when Aldor was not properly working with gcc version 4.
(That's the -writable-strings problem, which (I think) is still not
properly solved, but check the aldor-l archive.)
I think Laurentiu Dragan but gcc32 into aldor.conf in order to tell that
Aldor must be compiled using version 3.2 of gcc and gcc32 was probably
the name of gcc version 3.2 in his environment. :-(
Just compare my aldor.conf at
http://sage.math.washington.edu/home/hemmecke/pub/aldor.conf
#cc-name = gcc-3.3
#link-name = gcc-3.3
I've simply commented these lines out, so the usual gcc on your system
(i.e. gcc 4.2.4) will be chosen. (And pray that it'll work.)
The compilation worked fine for me with gcc 4.3.2 on my system (32bit),
but I haven't looked into the Aldor compiler to be able to tell where
exactly gcc 4 will not work.
Ralf