| SPECFE: a User Friendly Front End to Spec | ||
|---|---|---|
| <<< Previous | Detailed Installation Instructions | |
Once you have finished configuring the specfe package it should be straightforward to compile the code. Type
make
and wait... examine the resulting output to look for any errors. If the compilation completed successfully you should then type make install, or, if you are installing specfe in a directory that you would not normally have write access to, type:
sudo make install
If there are any errors during the compilation or installation step you may be able to correct them
by choosing different configuration options. Generally, the first error message to appear is the 'true'
one, but it may be followed by a 'cascade' of subsequent errors. I'll list a few common errors below, but
I cannot anticipate every possible problem, if you are unable to resolve them yourself, try sending a copy
of the compilation output to me at <jennings@anl.gov> and I will try to help.
The Makefile generated by the GNU autotools has a large number of useful extra options. The most useful of these are given below.
make distclean
Attempts to return the source directory to the state it was in immediately after unpacking the tar archive. You would then need to run ./configure again.
make clean
Attempts to remove the files generated by a previous 'make' command and return the source directory to the state it was in after running ./configure. You can then run make again
make install
Attempts to install the package files in their final destinations. In many cases you may need to run this command as root since you may not have the necessary privileges to write into the installation directories.
make uninstall
Attempts to delete the package files installed by a previous use of make install.
make dist
Creates a tar archive of the necessary source files of the package. Currently, this will create both a '.tar.gz' and a '.tar.bz2' file. You can generate one or other of these individually by typing make dist-gzip or make dist-bzip2 respectively.
This is useful if you have made useful changes to specfe and would like to send them back to me at
<jennings@anl.gov>
'make' fails complaining about a missing Makefile
make
make: *** No targets specified and no makefile found. Stop. |
You probably forgot to run configure, or there was some error that prevented configure from completing. Try running ./configure again and look carefully at the output for error messages.
You get a compilation error after typing 'make'
make
... more output ... specwatcher.c:13:22: spec_shm.h: No such file or directory specwatcher.c: In function `main': specwatcher.c:217: dereferencing pointer to incomplete type specwatcher.c:218: dereferencing pointer to incomplete type specwatcher.c:220: dereferencing pointer to incomplete type specwatcher.c:221: dereferencing pointer to incomplete type specwatcher.c:224: dereferencing pointer to incomplete type specwatcher.c:236: dereferencing pointer to incomplete type specwatcher.c:237: dereferencing pointer to incomplete type specwatcher.c:239: dereferencing pointer to incomplete type specwatcher.c:240: dereferencing pointer to incomplete type specwatcher.c:243: dereferencing pointer to incomplete type specwatcher.c:447: dereferencing pointer to incomplete type specwatcher.c:449: dereferencing pointer to incomplete type specwatcher.c:466: dereferencing pointer to incomplete type specwatcher.c:468: dereferencing pointer to incomplete type make[2]: *** [specwatcher-specwatcher.o] Error 1 make[2]: Leaving directory `/home/oxygen9/JENNINGS/specfe-1.4a7' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/oxygen9/JENNINGS/specfe-1.4a7' make: *** [all] Error 2 |
You were attempting to compile specfe on a system without an actual spec installation
present. You can avoid this problem by adding --without-watcher to your
configure options, or use the --with-specd=SPECD to specify the correct
directory path where the spec auxiliary files are stored
'./configure' cannot find the tcl and/or tk configuration files
./configure
checking build system type... sparc-sun-solaris2.9 checking host system type... sparc-sun-solaris2.9 checking target system type... sparc-sun-solaris2.9 checking for a BSD-compatible install... /opt/gnu/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for specwatcher program... yes checking for spec installation... SPECD = /usr/local/lib/spec.d checking for default spec geometry... fourc checking for using exafs code by default... yes checking for using powder code by default... yes checking for N-up printing capability... yes checking for generating specfe documentation... yes checking for Tcl configuration... configure: WARNING: Can't find Tcl configuration definitions apollo% |
You'll need to specify the location of the files tclConfig.sh and
tkConfig.sh from your tcl/tk installation. In the example above, you
would add --with-tclconfig=/opt/local/lib/tclConfig.sh
--with-tkconfig=/opt/local/lib/tkConfig.sh to your configure command.
The configure script couldn't find the BLT libraries
./configure
... more output ... checking dynamic linker characteristics... solaris2.9 ld.so checking whether make sets $(MAKE)... (cached) yes checking for BLT libraries... no no no checking for ANSI C header files... (cached) yes checking for stdlib.h... (cached) yes ... more output ... |
make
... more output ... specfesh_cmds.c:5: blt.h: No such file or directory ... more output ... |
You'll need to specify the location of the BLT installation explicitly. In the
example above you would add --with-blt=/opt/local to your configure command.
The documentation is not built
./configure
... more output ... checking for gs... /opt/local/bin/gs checking for psnup... /opt/local/bin/psnup checking for docbook2html... no checking for docbook2pdf... no checking for docbook2rtf... no checking for docbook2man... no docbook2html not found, disabling doc generation checking for g++... g++ checking for C++ compiler default output... a.out ... more output ... |
If you don't have the 'docbook' package available you will not be able to build the specfe
documentation. The configure script recognizes that docbook is not available and disables the
rules to build the documentation. You can remove these messages from the configure output
by adding --without-docs to your configure command.
Note that the distribution tarfiles include built copies of the documentation in any case, so being able to build the document is only important if you made any changes.
| <<< Previous | Home | |
| Configuration and configuration options | Up |