posted Nov 24, 2008 10:33 AM by Nikolaos Vasiloglou II
Lapack Blas fix for cygwin
Lapack doesn't compile properly with gcc4 on cygwin. We added an option, so when you compile it gives you an option to link with the precompiled cygwin versions of BLAS and LAPACK. If you have upgraded to the last version of Fastlib, remove the lock files from the fastlib/la directory. Also make sure you have installed the lapack module with the cygwin installer. Next time you build fastlib it will prompt you about blas lapack. Just choose version 3 if you are working unde cygwin
|
posted Nov 19, 2008 1:53 PM by Dongryeol Lee
If you have checked out from the svn repository between yesterday and today, you will notice
that your code does not compile any more. This is due to the new release of LAPACK
(on 11/16/2008), which in effect forces to upgrade to use a newer version of GCC and gfortran.
Please do an "svn update" to apply the fix. Now you are required to have GCC4 and GFortran
installed on your machine to compile FASTlib. Please note that we are in the process of
moving to a better build system very soon.
|
posted Oct 28, 2008 9:06 AM by Dongryeol Lee
LAPACK now compiles on machines with Fortran compilers with missing "_etime" definitions. These definitions
are used only during the compilation to measure how long a sequence of 100 SAXPY operations take. I have
changed to use INT_CPU_TIME, rather than the default value of EXT_ETIME defined in the Makefile. I have
checked to make sure that this change also works on all of our machines.
|
posted Oct 27, 2008 9:33 PM by Nikolaos Vasiloglou II
Fastlib now compiles on a Mac after Dong fixes of curl/wget. There was a lapack compilation problem. It turns out we needed to update to the latest xcode patch. So before installing fastlib, make sure you have the latest xcode installed on your mac |
posted Oct 24, 2008 4:33 PM by Dongryeol Lee
I have checked in fixes to our build system - now it auto-detects which of the two
is installed. Please report any strange behaviors - as far as I know, it worked both
with curl and wget.
|
posted Oct 24, 2008 8:42 AM by Dongryeol Lee
[
updated Oct 24, 2008 8:51 AM
]
From Nick, we finally have a fix:
"By the way Fastlib wouldn't compile on CYGWIN, there was a missing macro definition LINE_MAX in datanode.cc
This definition doesn't exist in CYGWIN so I added it... I also fixed the memory manager so now it compiles
under CYGWIN"
As a reminder, you can do "svn update" under $FASTLIBPATH to stay up to date with the current repository.
|
posted Oct 22, 2008 11:15 AM by Dongryeol Lee
I have added the fl- build- all script under fastlib2/fastlib/script/. You can do the following in any module containing build.py fl- build- all [-mode=<type of mode>] [--recursive]
and it will build every librule/binrule and generate appropriate symbolic links to them. If --recursive flag is provided,
then the script will automatically search for every build.py file and compile every possible rule specified in it. Otherwise,
it will compile only the rules specified in the build.py in the current directory. I would like to ask everyone to give this
new feature a try.
|
posted Oct 14, 2008 11:31 PM by Parikshit Ram
The FASTlib tutorial is added along with the coding style and cookbook pages. Relevant files are also added. The (very few) FAQs are added to the site. Now it needs work to be updated to the current condition.
|
posted Oct 10, 2008 2:11 PM by Parikshit Ram
The FASTlib website is up now. The initial idea is to make pages for the FASTlib manual and tutorial. Once they are up, we plan to add the FAQs to this site. This page will contain any new updates regarding the library. The idea of making a googlegroup to serve us as a forum is still not settled.
|
|
