GAP (cvec) - Chapter 2: Installation of the cvec-Package

Goto Chapter: Top 1 2 3 4 5 6 7 8 9 Bib Ind
[Top of Book] [Contents] [Previous Chapter] [Next Chapter]

[MathJax on]

2 Installation of the cvec-Package

### 2 Installation of the cvec-Package

To get the newest version of this GAP 4 package download one of the archive files

- `cvec-x.x.tar.gz`

- `cvec-x.x.tar.bz2`

- `cvec-x.x.zip`

and unpack it using

    gunzip cvec-x.x.tar.gz; tar xvf cvec-x.x.tar

or

    bzip2 -d cvec-x.x.tar.bz2; tar xvf cvec-x.x.tar

or

    unzip -x cvec-x.x.zip

respectively.

Do this in a directory called "`pkg`", preferably (but not necessarily) in the "`pkg`" subdirectory of your GAP 4 installation. It creates a subdirectory called "`cvec`".

The package will not work without the following compilation step.

To compile the C part of the package do (in the `pkg` directory)

        cd cvec
        ./configure
        make

If you installed the package in another "`pkg`" directory than the standard "`pkg`" directory in your GAP 4 installation, then you have to do two things. Firstly during compilation you have to use the option `--with-gaproot=PATH` of the `configure` script where "PATH" is a path to the main GAP root directory (if not given the default "`../..`" is assumed).

Secondly you have to specify the path to the directory containing your "`pkg`" directory to GAP's list of directories. This can be done by starting GAP with the "`-l`" command line option followed by the name of the directory and a semicolon. Then your directory is prepended to the list of directories searched. Otherwise the package is not found by GAP. Of course, you can add this option to your GAP startup script.

If you installed GAP on several architectures, you must execute the configure/make step for each of the architectures. You can either do this immediately after configuring and compiling GAP itself on this architecture, or alternatively (when using version 4.5 of GAP or newer) set the environment variable `CONFIGNAME` to the name of the configuration you used when compiling GAP before running `./configure`. Note however that your compiler choice and flags (environment variables `CC` and `CFLAGS`) need to be chosen to match the setup of the original GAP compilation. For example you have to specify 32-bit or 64-bit mode correctly!

[Top of Book] [Contents] [Previous Chapter] [Next Chapter]
Goto Chapter: Top 1 2 3 4 5 6 7 8 9 Bib Ind

generated by GAPDoc2HTML