On Wednesday 28 April 2010 01:37:04 pm linux fan wrote: > On 4/21/10, lux-integ <[email protected]> wrote: > > I forgot to add that I followed the recipe for creating shared libs > > (for atlas using gfortran) given here:- > > [again] > Have a look at what blfs gcc says re: fortran > http://www.linuxfromscratch.org/blfs/view/svn/general/gcc.html > > configure ... > --enable-languages=c,c++,ada,fortran,java,objc,obj-c++ && > > I thought the fortran in that line might make the gfortran if that works. thanks for your suggestion. I have made a little progress I hope (see below ) though amd seems to supply a 64-bit fortran library already incoprporaed in gcc http://developer.amd.com/documentation/articles/pages/ACMLwithDifferentGCCGFORTRAN.aspx (which does not seem obvious when you compile gcc).
I have completed a build of gcc-4.5.0. I had a good nose around a fedora12-machine and also noticed they had libgfortran.a and lingfortran.so under /usr/lib64//gcc-version/x86_64-redhat-linux. I then compared the new gcc-4.5.0 build with a previous (cblfs) build of GCC-4.4.2. They are the same. I have in ~/lib64/gcc/gcc-version/x86_64-unknown-linux-gnu -libgfortranbegin.a (no libgfortran.a nor libgfortran.so). BUT in ~/lib64 I have libgfortran.a and libgfortran.so (as with fedora). I did a gcc -v on the fedora machine and noticed they passed --build=x86_64-redhat-linux. I have two questions:- : QUESTION A) Are stuff(s) in ~lib(64)/gcc-version/x86_64-unknown-linux-gnu and ~/lib(64) directories interchangable? (In otherwords can I build say atlas (optimised for x86_64 cpu with stuff from the ~/lib(64) if it is missing from the ~lib(64)/gcc-version/x86_64-unknown-linux-gnu directory? QUESTION B) Is the labelling done by fedora (i.e. the --build=swith) significant and is this something we should be considering for blfs/cblfs builds and if so what are the implications? comments welcomed. ps I am having another run with this switch. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
