-
Notifications
You must be signed in to change notification settings - Fork 11
Build libFLAME
Here are the steps to build libFLAME.
-
Run configure script. Example below shows few sample options. Enable/disable other flags as needed
$ ./configure --enable-lapack2flame --enable-cblas-interfaces --enable-dynamic-build --prefix=<path to install>
-
Make and install. By default the library will be installed to $HOME/flame
- $ make
- $ make install
-
Run tests. Link with AMD optimized BLIS library
- $ cd test
create a directory for object files
- $ mkdir obj
Edit the Makefile.Change LDFLAGS as
LDFLAGS := -lm -lpthread
Modify the definition of LIBBLAS as : LIBBLAS :=
Comment out LIBLAPACK_PATH
Change LIBLAPACK to
LIBLAPACK :=
Save the Makefile
* $ make
* $ ./test_libflame.x
Depending on the target system, build environment and type of application that link with libFLAME, one would have to enable/disable suitable configure options.
Following suggests few options which are not enabled by default but comes handy in certain cases. For a complete list of options and their description, type ./configure --help
-
--enable-lapack2flame : This creates a FORTRAN compatibility layer. This option can be used by applications that have LAPACK API invocations. Enabling this option maps the LAPACK calls to FLAME/C implementations
-
--enable-max-arg-list-hack : On some build environments, compiling libFLAME might throw 'Argument list too long' error message when make tries to archive the object files to library. In such case, in order to reduce the length of argument list, one needs to enable this option.
-
--enable-cblas-interfaces : This option enable code that interfaces libFLAME's external wrapper routines to the BLAS via the CBLAS rather than the traditional Fortran-77 API.