File: INSTALL

package info (click to toggle)
mopac7 1.15-6
  • links: PTS, VCS
  • area: main
  • in suites: bullseye, buster, jessie, jessie-kfreebsd, sid, stretch
  • size: 3,748 kB
  • ctags: 5,768
  • sloc: fortran: 35,321; sh: 9,039; ansic: 417; makefile: 80
file content (39 lines) | stat: -rw-r--r-- 1,280 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
You can compile and install this package using commands

	./autogen.sh
	
export F77='g77 -fno-automatic'
export F77='gfortran -std=legacy -fno-automatic'
	
	./configure
	make
	make install

In installation only the libmopac library is installed, not the standalone
mopac7 executable which is also generated in the compilation stage.

You can use the run_mopac7 script to start the standalone mopac7 application,
for example to run some of the test files:

	./run_mopac7 tests/force

##########################################################################

20051011 ; the mopac7 package should now be gcc-4 compliant, but if you still
wish to use an older compiler, you need to do the following:

        CC=gcc-3.2 ./configure

This makes sure that gcc-3 compiler is used.

20051106 ; if building on Mac OS X or Darwin, Geoff Hutchison recommends
using Fink and:

CFLAGS="-I/sw/include -fno-common" LDFLAGS="-L/sw/lib -Wl,-undefined \
-Wl,dynamic_lookup -Wl,-m -Wl,bind_at_load" ./configure

20070921 ; the fortran code is now re-converted using a more recent version
of f2c and the compiler issues seem to disappear (gcc-4.1.2 works fine).

20080805 ; the configure-script now uses fortran compiler instead of
f2c/gcc combination (no need to link with libf2c/libg2c anymore).