Gaby, On Sunday, August 27, 2006 10:24 PM you wrote: > > Hi the patchlet below adds support for --with-gcl. > > By default, configure will try to detect the presence of a gcl > command in the build environment, and use it. You can instruct > Axiom not to autotect through the configure option --without-gcl. > Of course, you can also explicitly tell Axiom the availability of > GCL throught --with-gcl. All this follows standard GNU build > tools semantics. > > When I tried this, I had > * an outright segmentation fault with a _separately_ installed > GCL-2.6.8pre. That SIGSEV was preceeded by failure to load > sysdef.lsp from GCL-2.6.8pre installation. Investigation > revealed that indeed, that file is missing from the installation > repository. That seems a plain bug from GCL part. >
I think it might be the case that 'compiler::link' expects that gcl is built with option '--enable-ansi'. At least in that case I did not get the error you quote. > ... > Notice that none of the above problems manifests if one uses > GCL as part of the Axiom sources. Consequently, until the above > issues are fixed, be sure to specify --without-gcl when invoking > configure. > After repeat attempts with different options # make clean # ./configure ... # make I observed that lsp/stamp-gcldir is not being removed by 'make clean'. I hate these stupid "stamp-xxx" files. Surely there is a way to specify a proper dependency for gcl, no? Thanks for your continuing work on this branch! Regards, Bill Page. _______________________________________________ Axiom-developer mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/axiom-developer
