First commit

William Daniau
Showing 6 changed files with 301 additions and 0 deletions Side-by-side Diff
Make.inc.gfortran.atlas
README
bin/.bin
include/.include
lib/.lib
modules/.modules
@@ -0,0 +1,291 @@
+
+# IMPORTANT :
+# Variable BTREE must have been set to the build directory
+# ( export BTREE=/home/daniau/sources/build )
+# It is possible to build with the same sources under win32 with PGI Compiler
+# For Windows : use a cygwin bash shell and set BTREE using cygwin path ex: 
+# export BTREE=/c/dev/build
+
+# Location of qmake utility for qt3 and qt4, this is specific to each linux distribution
+QMAKE3=/usr/lib/qt3/bin/qmake
+QMAKE4=/usr/bin/qmake
+
+# How many thread for Make Qt programs
+#NBTHREAD=2
+
+###############################################################################
+#
+# Extensions
+#
+# This define the extension names for :
+#   + static libraries  : libext
+#   + dynamic libraries : soext 
+#   + executable        : exext
+#
+# Uncomment the following according to your platform
+
+
+# Windows
+#libext=.lib
+#exext=.exe
+
+
+# Linux
+#
+libext=.a
+soext=.so
+exext=
+
+###############################################################################
+# 
+# Dynamic libraries
+#
+# Set BUILDSO to y to build dynamic versions of libraries if available
+#
+# This has been only tested with gfortran under linux for now
+###############################################################################
+BUILDSO=n
+
+###############################################################################
+#
+# OpenMP setup
+#
+# The variable OMP contains either nothing, either the compiler switch to
+# enable OpenMP
+#
+# If you want to build a pure serial version leave OMP empty
+# OMP =
+# for PGI :
+# OMP = -mp
+# for gfortran :
+# OMP = -fopenmp
+###############################################################################
+OMP = -fopenmp
+
+###############################################################################
+#
+# C Compiler Configuration
+#
+###############################################################################
+#
+# CC = C compiler
+# CFLAGS = flags that are used for compiling C files
+# 
+# Debug setting :
+# CC = gcc
+# CFLAGS = -g -fpic -m64
+#
+# Production setting :
+# CC = gcc
+# CFLAGS = -O2 -fpic -m64
+#
+# Or for pgcc :
+# CC = pgcc
+# CFLAGS = -g -fpic 
+# or CFLAGS = -O2 -fpic
+
+# For Compiling under Windows 32bits with PGI add -DPGIW32 to CFLAGS
+#CC = pgcc
+#CFLAGS = -O2 -Bstatic -DPGIW32
+
+CC = gcc
+CFLAGS = -O2 -fpic
+
+
+###############################################################################
+#
+# Fortran 95 Compiler Configuration
+#
+###############################################################################
+#
+# F95 = fortran 95 compiler
+# F95FLAGS = flags to be used when building objects
+#
+# Debug settings
+# F95 = pgf95
+# F95FLAGS = -g -fpic -I$(BTREE)/modules
+#
+# Production settings
+# F95 = pgf95
+# F95FLAGS = -fastsse -Mipa=fast -fpic -I$(BTREE)/modules
+#
+# Note that .mod files will be put in $(BTREE)/modules by makefiles
+# this is the reason for -I$(BTREE)/modules
+#
+# An other note for portland compiler at least : by default the compiler will use
+# all possible optimisations for the current processor, so the binaries may or may not 
+# work on another one. For example a binary compiled on an Opteron64 may not work
+# on an Intel x86_64. If you plan to use your binaries on different platforms,
+# you should use the -tp option
+#
+# -tp k8-64 => produce a binary optimized for AMD Opteron family
+# -tp p7-64 => produce a binary optimized for Intel x64 processors
+# -tp x64 => produce an unified binary which will run on both AMD and Intel
+# no -tp option => produce a binary optimized for the running processor
+
+#F95 = pgf95
+#F95FLAGS = -g -fpic -I$(BTREE)/modules
+#F95FLAGS = -fastsse -fpic -I$(BTREE)/modules
+F95 = gfortran
+F95FLAGS = -ffree-line-length-none -O2 -fpic -I$(BTREE)/modules
+
+# For Compiling under Windows 32bits with PGI
+# Paths for -I must be specified in a windows way (not cygwin way)
+# that is -I"c:\dev\build\modules" and not -I/c/dev/build/modules
+#F95 = pgf95
+#F95FLAGS = -g -Munix -Bstatic -I"c:\dev\build\modules"
+
+# Win32 production setting :
+#F95FLAGS = -fastsse -Munix -Bstatic -I"c:\dev\build\modules"
+
+###############################################################################
+#
+# Linking Configuration
+#
+###############################################################################
+#
+# LINK = linker program, usually same as compiler
+# LINKFLAGS = flags to be used when linking programs
+#
+# Debug settings 
+# LINK = pgf95
+# LINKFLAGS = -g -L$(BTREE)/lib
+#
+# Production settings
+# LINK = pgf95
+# LINKFLAGS = -fastsse -Mipa=fast -L$(BTREE)/lib
+#
+# Note that .a files will be put in $(BTREE)/lib by makefiles
+# this is the reason for -L$(BTREE)/lib
+#LINK = pgf95
+#LINKFLAGS = -g -L$(BTREE)/lib
+#LINKFLAGS = -fastsse -L$(BTREE)/lib
+
+LINK = gfortran
+LINKFLAGS = -ffree-line-length-none -O2 -L$(BTREE)/lib
+
+# For Compiling under Windows 32bits with PGI
+# Paths for -I must be specified in a windows way (not cygwin way)
+# that is -L"c:\dev\build\lib" and not -I/c/dev/build/lib
+#LINK = pgf95
+#LINKFLAGS = -g -Munix -Bstatic -L"c:\dev\build\lib"
+
+# Win32 production setting :
+#LINKFLAGS = -fastsse -Munix -Bstatic -L"c:\dev\build\lib"
+
+
+###############################################################################
+#
+# BLAS/LAPACK/ACML Configuration
+#
+###############################################################################
+#
+# Location of blas and lapack
+#
+# Commercial fortran compilers comes with their own optimized versions of blas 
+# and lapack. If you're running on an AMD processor, you should use acml
+# http://developer.amd.com/acml.jsp , which is an optimized version of both 
+# blas and lapack (and also some more functionnalities).
+#
+# Our Portland Fortran compiler comes with the 3 libraries. As we're running
+# AMD processors, we use acml.
+#
+# EXTERNALLIBPATH may contain a -Ldirectory directive
+# LAPACK = directive for lapack
+# BLAS = directive for blas
+# ACML = directive for acml
+#
+# Example 1:
+# EXTERNALLIBPATH = -L/usr/local/pgi/linux86-64/6.1/lib/
+# LAPACK = -llapack
+# BLAS = -lblas
+# ACML =
+#
+# Example 2:
+# EXTERNALLIBPATH = 
+# LAPACK = /usr/local/pgi/linux86-64/6.1/lib/liblapack.a
+# BLAS = /usr/local/pgi/linux86-64/6.1/lib/libblas.a
+# ACML =
+#
+# Example 3:
+# EXTERNALLIBPATH = -L/usr/local/pgi/linux86-64/6.1/lib/
+# LAPACK =
+# BLAS =
+# ACML = -lacml
+#
+# Example 4:
+# EXTERNALLIBPATH = 
+# LAPACK =
+# BLAS =
+# ACML = /usr/local/pgi/linux86-64/6.1/lib/libacml.a
+#
+# Simple rule is that if you set ACML then leave BLAS and LAPACK empty.
+#
+#
+
+#EXTERNALLIBPATH =
+#LAPACK = 
+#BLAS = 
+#ACML = /usr/local/pgi/linux86-64/7.0/lib/libacml.a
+
+# With gfortran and reference implementation 
+#EXTERNALLIBPATH =
+#LAPACK = $(BTREE)/lib/lapack_LINUX.a
+#BLAS = $(BTREE)/lib/blas_LINUX.a
+#ACML =
+
+# With gfortran and acml
+#EXTERNALLIBPATH =
+#LAPACK =
+#BLAS =
+#ACML = /usr/local/acml4.1.0/gfortran64/lib/libacml.a
+
+# With atlas compiled with gfortran and gcc
+#EXTERNALLIBPATH =
+#LAPACK = $(BTREE)/lib/liblapack.a
+#BLAS = $(BTREE)/lib/libf77blas.a $(BTREE)/lib/libcblas.a $(BTREE)/lib/libatlas.a
+#PTBLAS = $(BTREE)/lib/libptf77blas.a $(BTREE)/lib/libptcblas.a $(BTREE)/lib/libatlas.a
+#ACML =
+
+# With dynamic versions of atlas compiled with gfortran and gcc
+EXTERNALLIBPATH =
+LAPACK = $(BTREE)/lib/liblapack.so
+BLAS = $(BTREE)/lib/libf77blas.so $(BTREE)/lib/libcblas.so $(BTREE)/lib/libatlas.so
+ACML =
+
+
+
+# Libs that may be necessary for compiling umfpack, for exemple
+# EXTRALIBS = -lm -L/usr/local/pgi/linux86-64/7.0/lib -lpgftnrtl -lpgc -lrt 
+# is necessary for using portland fortran blas
+#
+#EXTRALIBS = -lm -L/usr/local/pgi/linux86-64/7.0/lib -lpgftnrtl -lpgc -lrt
+#EXTRALIBS = -lm
+
+# Win32 settings
+#EXTERNALLIBPATH =  
+#LAPACK = -llapack
+#BLAS = -lblas 
+#ACML = 
+#EXTRALIBS = -llapack -lpgftnrtl
+
+
+###############################################################################
+#
+# FVN Configuration
+#
+###############################################################################
+#
+# LINKFVN should not be changed, it defines the linking directives to link 
+# with fvn as it needs both blas and lapack, and also umfpack and amd
+# which are both compiled within fvn
+#
+#LINKFVN = -lfvn -lfvn_fnlib -lumfpack -lamd $(EXTERNALLIBPATH) $(LAPACK) $(BLAS) $(ACML)
+LINKFVN = -lfvn $(EXTERNALLIBPATH) $(LAPACK) $(BLAS) $(ACML)
+
+
+#
+# AR = archive utility
+#
+AR = ar
+RANLIB = ranlib
@@ -0,0 +1,10 @@
+This is a minimum build structure for building and using fvn
+
+1) Clone the following repositories : fvnbtree, atlas, fvn 
+1) Setup environment variable BTREE to point to the fvnbtree directory
+2) copy file Make.inc.gfortran.atlas to Make.inc
+3) read the comments and adapt Make.inc to your needs
+4) go to atlas directory and follow instructions, after the 
+"make install", atlas libraries will be in $BTREE/lib
+5) go to fvn directory and do "make" the "make install"
+6) go to fvn_test, and type "make", this should build the example programs.
...	...	@@ -0,0 +1,291 @@
	1	+
	2	+# IMPORTANT :
	3	+# Variable BTREE must have been set to the build directory
	4	+# ( export BTREE=/home/daniau/sources/build )
	5	+# It is possible to build with the same sources under win32 with PGI Compiler
	6	+# For Windows : use a cygwin bash shell and set BTREE using cygwin path ex:
	7	+# export BTREE=/c/dev/build
	8	+
	9	+# Location of qmake utility for qt3 and qt4, this is specific to each linux distribution
	10	+QMAKE3=/usr/lib/qt3/bin/qmake
	11	+QMAKE4=/usr/bin/qmake
	12	+
	13	+# How many thread for Make Qt programs
	14	+#NBTHREAD=2
	15	+
	16	+###############################################################################
	17	+#
	18	+# Extensions
	19	+#
	20	+# This define the extension names for :
	21	+# + static libraries : libext
	22	+# + dynamic libraries : soext
	23	+# + executable : exext
	24	+#
	25	+# Uncomment the following according to your platform
	26	+
	27	+
	28	+# Windows
	29	+#libext=.lib
	30	+#exext=.exe
	31	+
	32	+
	33	+# Linux
	34	+#
	35	+libext=.a
	36	+soext=.so
	37	+exext=
	38	+
	39	+###############################################################################
	40	+#
	41	+# Dynamic libraries
	42	+#
	43	+# Set BUILDSO to y to build dynamic versions of libraries if available
	44	+#
	45	+# This has been only tested with gfortran under linux for now
	46	+###############################################################################
	47	+BUILDSO=n
	48	+
	49	+###############################################################################
	50	+#
	51	+# OpenMP setup
	52	+#
	53	+# The variable OMP contains either nothing, either the compiler switch to
	54	+# enable OpenMP
	55	+#
	56	+# If you want to build a pure serial version leave OMP empty
	57	+# OMP =
	58	+# for PGI :
	59	+# OMP = -mp
	60	+# for gfortran :
	61	+# OMP = -fopenmp
	62	+###############################################################################
	63	+OMP = -fopenmp
	64	+
	65	+###############################################################################
	66	+#
	67	+# C Compiler Configuration
	68	+#
	69	+###############################################################################
	70	+#
	71	+# CC = C compiler
	72	+# CFLAGS = flags that are used for compiling C files
	73	+#
	74	+# Debug setting :
	75	+# CC = gcc
	76	+# CFLAGS = -g -fpic -m64
	77	+#
	78	+# Production setting :
	79	+# CC = gcc
	80	+# CFLAGS = -O2 -fpic -m64
	81	+#
	82	+# Or for pgcc :
	83	+# CC = pgcc
	84	+# CFLAGS = -g -fpic
	85	+# or CFLAGS = -O2 -fpic
	86	+
	87	+# For Compiling under Windows 32bits with PGI add -DPGIW32 to CFLAGS
	88	+#CC = pgcc
	89	+#CFLAGS = -O2 -Bstatic -DPGIW32
	90	+
	91	+CC = gcc
	92	+CFLAGS = -O2 -fpic
	93	+
	94	+
	95	+###############################################################################
	96	+#
	97	+# Fortran 95 Compiler Configuration
	98	+#
	99	+###############################################################################
	100	+#
	101	+# F95 = fortran 95 compiler
	102	+# F95FLAGS = flags to be used when building objects
	103	+#
	104	+# Debug settings
	105	+# F95 = pgf95
	106	+# F95FLAGS = -g -fpic -I$(BTREE)/modules
	107	+#
	108	+# Production settings
	109	+# F95 = pgf95
	110	+# F95FLAGS = -fastsse -Mipa=fast -fpic -I$(BTREE)/modules
	111	+#
	112	+# Note that .mod files will be put in $(BTREE)/modules by makefiles
	113	+# this is the reason for -I$(BTREE)/modules
	114	+#
	115	+# An other note for portland compiler at least : by default the compiler will use
	116	+# all possible optimisations for the current processor, so the binaries may or may not
	117	+# work on another one. For example a binary compiled on an Opteron64 may not work
	118	+# on an Intel x86_64. If you plan to use your binaries on different platforms,
	119	+# you should use the -tp option
	120	+#
	121	+# -tp k8-64 => produce a binary optimized for AMD Opteron family
	122	+# -tp p7-64 => produce a binary optimized for Intel x64 processors
	123	+# -tp x64 => produce an unified binary which will run on both AMD and Intel
	124	+# no -tp option => produce a binary optimized for the running processor
	125	+
	126	+#F95 = pgf95
	127	+#F95FLAGS = -g -fpic -I$(BTREE)/modules
	128	+#F95FLAGS = -fastsse -fpic -I$(BTREE)/modules
	129	+F95 = gfortran
	130	+F95FLAGS = -ffree-line-length-none -O2 -fpic -I$(BTREE)/modules
	131	+
	132	+# For Compiling under Windows 32bits with PGI
	133	+# Paths for -I must be specified in a windows way (not cygwin way)
	134	+# that is -I"c:\dev\build\modules" and not -I/c/dev/build/modules
	135	+#F95 = pgf95
	136	+#F95FLAGS = -g -Munix -Bstatic -I"c:\dev\build\modules"
	137	+
	138	+# Win32 production setting :
	139	+#F95FLAGS = -fastsse -Munix -Bstatic -I"c:\dev\build\modules"
	140	+
	141	+###############################################################################
	142	+#
	143	+# Linking Configuration
	144	+#
	145	+###############################################################################
	146	+#
	147	+# LINK = linker program, usually same as compiler
	148	+# LINKFLAGS = flags to be used when linking programs
	149	+#
	150	+# Debug settings
	151	+# LINK = pgf95
	152	+# LINKFLAGS = -g -L$(BTREE)/lib
	153	+#
	154	+# Production settings
	155	+# LINK = pgf95
	156	+# LINKFLAGS = -fastsse -Mipa=fast -L$(BTREE)/lib
	157	+#
	158	+# Note that .a files will be put in $(BTREE)/lib by makefiles
	159	+# this is the reason for -L$(BTREE)/lib
	160	+#LINK = pgf95
	161	+#LINKFLAGS = -g -L$(BTREE)/lib
	162	+#LINKFLAGS = -fastsse -L$(BTREE)/lib
	163	+
	164	+LINK = gfortran
	165	+LINKFLAGS = -ffree-line-length-none -O2 -L$(BTREE)/lib
	166	+
	167	+# For Compiling under Windows 32bits with PGI
	168	+# Paths for -I must be specified in a windows way (not cygwin way)
	169	+# that is -L"c:\dev\build\lib" and not -I/c/dev/build/lib
	170	+#LINK = pgf95
	171	+#LINKFLAGS = -g -Munix -Bstatic -L"c:\dev\build\lib"
	172	+
	173	+# Win32 production setting :
	174	+#LINKFLAGS = -fastsse -Munix -Bstatic -L"c:\dev\build\lib"
	175	+
	176	+
	177	+###############################################################################
	178	+#
	179	+# BLAS/LAPACK/ACML Configuration
	180	+#
	181	+###############################################################################
	182	+#
	183	+# Location of blas and lapack
	184	+#
	185	+# Commercial fortran compilers comes with their own optimized versions of blas
	186	+# and lapack. If you're running on an AMD processor, you should use acml
	187	+# http://developer.amd.com/acml.jsp , which is an optimized version of both
	188	+# blas and lapack (and also some more functionnalities).
	189	+#
	190	+# Our Portland Fortran compiler comes with the 3 libraries. As we're running
	191	+# AMD processors, we use acml.
	192	+#
	193	+# EXTERNALLIBPATH may contain a -Ldirectory directive
	194	+# LAPACK = directive for lapack
	195	+# BLAS = directive for blas
	196	+# ACML = directive for acml
	197	+#
	198	+# Example 1:
	199	+# EXTERNALLIBPATH = -L/usr/local/pgi/linux86-64/6.1/lib/
	200	+# LAPACK = -llapack
	201	+# BLAS = -lblas
	202	+# ACML =
	203	+#
	204	+# Example 2:
	205	+# EXTERNALLIBPATH =
	206	+# LAPACK = /usr/local/pgi/linux86-64/6.1/lib/liblapack.a
	207	+# BLAS = /usr/local/pgi/linux86-64/6.1/lib/libblas.a
	208	+# ACML =
	209	+#
	210	+# Example 3:
	211	+# EXTERNALLIBPATH = -L/usr/local/pgi/linux86-64/6.1/lib/
	212	+# LAPACK =
	213	+# BLAS =
	214	+# ACML = -lacml
	215	+#
	216	+# Example 4:
	217	+# EXTERNALLIBPATH =
	218	+# LAPACK =
	219	+# BLAS =
	220	+# ACML = /usr/local/pgi/linux86-64/6.1/lib/libacml.a
	221	+#
	222	+# Simple rule is that if you set ACML then leave BLAS and LAPACK empty.
	223	+#
	224	+#
	225	+
	226	+#EXTERNALLIBPATH =
	227	+#LAPACK =
	228	+#BLAS =
	229	+#ACML = /usr/local/pgi/linux86-64/7.0/lib/libacml.a
	230	+
	231	+# With gfortran and reference implementation
	232	+#EXTERNALLIBPATH =
	233	+#LAPACK = $(BTREE)/lib/lapack_LINUX.a
	234	+#BLAS = $(BTREE)/lib/blas_LINUX.a
	235	+#ACML =
	236	+
	237	+# With gfortran and acml
	238	+#EXTERNALLIBPATH =
	239	+#LAPACK =
	240	+#BLAS =
	241	+#ACML = /usr/local/acml4.1.0/gfortran64/lib/libacml.a
	242	+
	243	+# With atlas compiled with gfortran and gcc
	244	+#EXTERNALLIBPATH =
	245	+#LAPACK = $(BTREE)/lib/liblapack.a
	246	+#BLAS = $(BTREE)/lib/libf77blas.a $(BTREE)/lib/libcblas.a $(BTREE)/lib/libatlas.a
	247	+#PTBLAS = $(BTREE)/lib/libptf77blas.a $(BTREE)/lib/libptcblas.a $(BTREE)/lib/libatlas.a
	248	+#ACML =
	249	+
	250	+# With dynamic versions of atlas compiled with gfortran and gcc
	251	+EXTERNALLIBPATH =
	252	+LAPACK = $(BTREE)/lib/liblapack.so
	253	+BLAS = $(BTREE)/lib/libf77blas.so $(BTREE)/lib/libcblas.so $(BTREE)/lib/libatlas.so
	254	+ACML =
	255	+
	256	+
	257	+
	258	+# Libs that may be necessary for compiling umfpack, for exemple
	259	+# EXTRALIBS = -lm -L/usr/local/pgi/linux86-64/7.0/lib -lpgftnrtl -lpgc -lrt
	260	+# is necessary for using portland fortran blas
	261	+#
	262	+#EXTRALIBS = -lm -L/usr/local/pgi/linux86-64/7.0/lib -lpgftnrtl -lpgc -lrt
	263	+#EXTRALIBS = -lm
	264	+
	265	+# Win32 settings
	266	+#EXTERNALLIBPATH =
	267	+#LAPACK = -llapack
	268	+#BLAS = -lblas
	269	+#ACML =
	270	+#EXTRALIBS = -llapack -lpgftnrtl
	271	+
	272	+
	273	+###############################################################################
	274	+#
	275	+# FVN Configuration
	276	+#
	277	+###############################################################################
	278	+#
	279	+# LINKFVN should not be changed, it defines the linking directives to link
	280	+# with fvn as it needs both blas and lapack, and also umfpack and amd
	281	+# which are both compiled within fvn
	282	+#
	283	+#LINKFVN = -lfvn -lfvn_fnlib -lumfpack -lamd $(EXTERNALLIBPATH) $(LAPACK) $(BLAS) $(ACML)
	284	+LINKFVN = -lfvn $(EXTERNALLIBPATH) $(LAPACK) $(BLAS) $(ACML)
	285	+
	286	+
	287	+#
	288	+# AR = archive utility
	289	+#
	290	+AR = ar
	291	+RANLIB = ranlib
...	...	@@ -0,0 +1,10 @@
	1	+This is a minimum build structure for building and using fvn
	2	+
	3	+1) Clone the following repositories : fvnbtree, atlas, fvn
	4	+1) Setup environment variable BTREE to point to the fvnbtree directory
	5	+2) copy file Make.inc.gfortran.atlas to Make.inc
	6	+3) read the comments and adapt Make.inc to your needs
	7	+4) go to atlas directory and follow instructions, after the
	8	+"make install", atlas libraries will be in $BTREE/lib
	9	+5) go to fvn directory and do "make" the "make install"
	10	+6) go to fvn_test, and type "make", this should build the example programs.