Re: [Axiom-developer] Building Axiom 11/15/2004 on Solaris 9 Sparc

[root]

Kostas,

>I am trying to compile the Axiom sources dated 11/15/2004 on a Sun Solaris 9 
>system.
>The build ends with lisp dumping core:
>
>--------------------------------------------------------------------------------------------------
>Loading /home/build/axiom/int/boot/npextras.lisp
>Finished loading /home/build/axiom/int/boot/npextras.lisp
>Compiling tytree1.lisp.
>; (DEFUN |bfMDef| ...) is being compiled.
>;; Warning: The variable |defOp| is not used.

[....snip....]

>Illegal Instruction - core dumped
>make[3]: *** [/home/build/axiom/obj/solaris/bin/bootsys] Error 132
>make[3]: Leaving directory `/home/build/axiom/src/boot'
>make[2]: *** [bootdir] Error 2
>make[2]: Leaving directory `/home/build/axiom/src'
>make[1]: *** [srcdir] Error 2
>make[1]: Leaving directory `/home/build/axiom'
>make: *** [
>bash-2.05$
>bash-2.05$ cd ../../obj/solaris/bin
>bash-2.05$ gdb -c core
>GNU gdb 6.1
>Copyright 2004 Free Software Foundation, Inc.
>GDB is free software, covered by the GNU General Public License, and you are
>welcome to change it and/or distribute copies of it under certain conditions.
>Type "show copying" to see the conditions.
>There is absolutely no warranty for GDB.  Type "show warranty" for details.
>This GDB was configured as "sparc-sun-solaris2.8".
>Core was generated by `/home/build/axiom/obj/solaris/bin/lisp'.
>Program terminated with signal 4, Illegal instruction.
>#0  0x007affd0 in ?? ()
>(gdb) q

This appears to be a failure in the saved image of lisp. The axiom build
first builds GCL and saves the image as obj/${SYS}/bin/lisp. This is the
first step.

This lisp image is used to compile the boot language compiler (in the
src/boot subdirectory). The compiled files for the boot language compiler
are loaded into a lisp and saved as obj/${SYS}/bin/bootsys. This is the
second step.

Clearly the saved bootsys image is failing but I don't know why.

Camm is the person most likely to know and I've copied him on this.


[... snip ...]

>Edit Makefile:
>      tar -> gtar

I assume that gtar is gnu-tar. I'll have to make the system aware
that the 'tar' command can change and fix this everywhere.


>make noweb
>
>Edit the shell script "mnt/solaris/bin/document" to set
>
>weave="$AXIOM/bin/lib/noweave -delay -x"

This doesn't seem necessary as I append the -delay to the command
whenever it is used. Did you find a case where this is missing?

>1. Edit Makefile.pamphlet to add [11pt] and
>
>\usepackage[hypertex,colorlinks=true,linkcolor=blue,filecolor=webgreen,extension=dvi]{hyperref}

As far as I know there are no hyperlinks in the Makefile.pamphlet files.
This will be more of an issue once I get the hyperdoc browser working.
The plan is to have the .dvi files viewed in-line in hyperdoc but the
details are still to be worked out. 

>2. Study Makefile.dvi, edit Makefile.pamphlet:
>
>(a) Check the GCL version of GCL:
>
>GCLVERSION=gcl-2.6.5
>
>Then rm lsp/Makefile
>
>NOTE: Axiom contains its own distribution of GCL!

Yes, this is true and a source of some discussion. Please search the
archive of this mailing list and you'll see the reasons pro-and-con.
Essentially GCL is there because (a) I need to change the image and
(b) Axiom needs to be tested with a known version. Both points have
been discussed and in the future this may change but there are other
things that need attention first.

[...snip...]

>(c) Add a <<Makefile.solaris>> chunk in section 2.  Should have really been
>     "solaris9g".

Please send me the chunk.

>(d) Edit lsp/Makefile.pamphlet and globaly change @tar to @$(TAR).

I'll fix this in the release version.


>2. Building the GCL within Axiom (or outside of it, for that matter) is a mess!
>
>  - I had to edit the patch
>       zips/gcl-2.6.5.cmpnew.gcl_cmpflet.lsp.patch
>    supplied by Axiom so that it would match, and to put "patch -l" in the
>    Makefile, so that this patch would ignore blanks.

I'll look into this. This should not fail in the production version.

>  - Do alias awk=gawk in the shell.

I'll look into this.

>  - Do export CFLAGS=-I/opt/csw/include in the shell, otherwise BFD won't
>    compile.  Why doesn't GCL use its own binutils subdirectory?

It is possible to get GCL to use its own binutils directory.
Check the configure script. One of the options allows you to do this.
The configure command is included in the lsp/Makefile.pamphlet file.
If you want a special version for solaris it needs a new chunk.

If you're interested in working on a solaris port further I can 
arrange for you to become a developer. We've set up an arch server
that has branches for various pieces of work. Look at
http://arch.axiom-developer.org

In order to be a developer with write access I need to get an ssh
key from you. On linux this is done with:

ssh-keygen -t dsa

which creates a file called .ssh/id_dsa.pub which you need to send to
me. Installing this key on the host will give you write access to the
arch archive.

I don't have a nearby solaris machine but there are a few in work.
I can probably get write access to one so I can help with the port.

Tim Daly
address@hidden