The macosxhints Forums

The macosxhints Forums (http://hintsforums.macworld.com/index.php)
-   UNIX - General (http://hintsforums.macworld.com/forumdisplay.php?f=16)
-   -   Blas Help (http://hintsforums.macworld.com/showthread.php?t=12154)

Nsee 05-30-2003 04:06 PM

Currently, I need to know if I can quit the terminal, it still doing all that checking and compilng, and my system will be fine. I cannot leave this machine in administrator over the weekend. Sorry.

sao 05-30-2003 05:03 PM

Nsee,

I think something is going very wrong with your installation of Fink, it shouldn't take so long, so you better stop the compilation, we will cleanup later and start again.

And I must say, we are not understanding each other very well, why didn't you downloaded the Fink installer I pointed to you?

So, which Fink installer you downloaded, can you point to the web page?

I just finished compiling 'atlas version-3.4.1-2' from source with Fink and although is a rather complicate install due to all the questions asked during the configure process, it installed without any problem.

As soon as you install Fink succesfully I will post the configuration that worked for me.

Nsee 05-30-2003 05:48 PM

Blas help
 
Thank you very much. i just have to go over several points. i did stop the installation, and do not worry, i have full administrator access over the machine, plus, i have 40 identical systems that i can "try" various configuratiosn with.
My questions are:
1) Should i try again with exclusivly your link, will that work for 10.2.6
2) Should I try darwinports instead (http://www.opendarwin.org/projects/darwinports/), using fink2dp for any missing packages http://www.opendarwin.org/pipermail/...er/000370.html
3) would it help if i used a more unix like enviroment like x11 or xfree86 or xdarwin exclusively
4) Any other requirements you belive i should follow?

sao 05-30-2003 06:03 PM

Quote:

Nsee wrote:
...Should i try again with exclusivly your link, will that work for 10.2.6
Yes, it will work.

I have to stop now and go to sleep, as it is very late in Singapore, will continue tomorrow...

sao 05-31-2003 02:32 AM

Nsee,

You might have a partial installation of Fink already, so check if you have a /sw directory. If you do, let's remove it to start a clean installation. Run in terminal.app:

sudo rm -rf /sw


Then, please follow the steps below:

1- Download the Fink Installer from here:

http://fink.sourceforge.net/download/index.php

2- Install Fink:

"Double-click "Fink-0.5.2-Installer.dmg" to mount the disk image, then double-click the "Fink 0.5.2 Installer.pkg" package inside. Follow the instructions on screen".

3- Set Fink environment following the indications here:

http://fink.sourceforge.net/doc/user...tall.php#setup

4- After that's done, open terminal.app and run:

'fink scanpackages'

When this is done, let me know.

Note before we continue:
Do you have Apple December 2002 Developer Tools installed? If you do, you can also install with Fink, the package 'atlas' from source, like I did yesterday.

Nsee 05-31-2003 10:35 AM

Yes i have the december 2002 developer tools installed, but since it is a weekend, I cannot access my work machine, so I will tell you my progress in two days.

sao 05-31-2003 04:41 PM

Nsee,

Once you installed Fink, if you want to compile 'atlas' from source from the current-stable release (this is the most recent stable version that can be installed from source for OSX 10.2), run in terminal.app in the following order:

fink selfupdate-cvs

To update the package descriptions and a few essential core packages.

fink update-all

To update your packages to the latest available versions.

Then, if you want to install Xfree86 with Fink, run:

fink install xfree86-rootless

And finally:

fink install atlas

sao 05-31-2003 04:43 PM

When compiling starts, configure will ask you a lot of questions, I selected the default answer in most cases as you can see here:
Quote:

Configure will ask a series of questions, in one of two forms. The first form
of question is a menu of choices. One option in almost all menus is
'Other/UNKNOWN'. If you are unsure of the answer, always choose this option.
The second form of question is a single line, with a default answer shown in
square braces. If you hit return without typing anything, this default answer
will be used. Again, if you are unsure of the answer, simply accept the
default.

ATLAS can detect almost everything it needs to know, so choosing the default
or 'Other/UNKNOWN' will at worst simply extend the install time (if you tell
config the answer to something ATLAS can skip some tests).

Configure makes no changes to the state of things until all questions have
been asked and answered. Therefore, if you get confused and want to start
over, feel free to break out of this program (CTRL-C, CTRL-BREAK, etc)
and start again. Alternatively, if you make a mistake you can finish the
configure process, and then edit the created make include file by hand to fix
the mistake manually (the name and location of this file will be printed
out at the end of configure).

If you have problems during configure or installation, consult the file
'ATLAS/README/TroubleShoot.txt'.

I need to know if you are using a cross-compiler (i.e., you are compiling on
a different architecture than you want the library built for).

Are you using a cross-compiler? [n]:

Probing to make operating system determination:
Operating system configured as OSX

Probing for architecture:
Enter your machine type:
1. PowerPC 604e
2. PowerPC 604
3. PowerPC G4 (7400)
4. Other/UNKNOWN
Enter machine number [4]: 3
Architecture is set to PPCG4

Probing for supported ISA extensions:
AltiVec: DETECTED!
Number of CPUs: 1

Looking for compilers:
/usr/bin//gcc : v3.1.20020420
F77 = /sw/bin/g77 -funroll-all-loops -O3
CC = /usr/bin/cc -fomit-frame-pointer -O3 -traditional-cpp -faltivec
MCC = /usr/bin/cc -fomit-frame-pointer -O2 -traditional-cpp -fschedule-insns
-fschedule-insns2 -faltivec

Looking for BLAS (this may take a while):

Unable to find usable BLAS, BLASlib left blank.
FINDING tar, gzip, AND gunzip
tar : /sw/bin//tar
gzip : /sw/bin//gzip
gunzip : /sw/bin//gunzip

sao 05-31-2003 04:45 PM

Quote:

ATLAS has default parameters for OS='OSX' and system='PPCG4'.
If you want to just trust these default values, you can use express setup,
drastically reducing the amount of questions you are required to answer

use express setup? [y]:

You need to choose a name which represents this architecture (eg. UltraSparc,
Dec21164, etc). Do not use a generic name (eg. solaris, linux), which might
apply to different hardware. This architecture name will be appended to the
name of the created make include file, and appear in all subdirectories, so
don't make it longer than you like to type. The name should follow the rules
for file names (so don't use punctuation and spaces, for instance).

Enter Architecture name (ARCH) [OSX_PPCG4AltiVec]:
<arch> set to 'OSX_PPCG4AltiVec'

This next value is the size, in kilobytes, that ATLAS must read/write in order
to completely flush your largest cache. ATLAS will flush this much memory
between timing calls, in order to ensure timings are not inflated by
cache preloading. A safe maximum is usually twice the size of your actual
largest cache size. If you do not know the size of your largest cache,
a maximum value is fine. The only drawback to making this value large
is that it requires more memory to do timings, and may slow down
the install process (if you have only a small amount of memory, it can also
invalidate the timings by causing the timers to swap). The default given
below is ATLAS's idea of either the maximum cache your system could have, or
the maximum ATLAS believes it is safe to flush. If you are certain that
your largest cache is smaller than the default given below, expedite the
install by changing it. If you are certain you have enough memory to
support the necessary memory demands without swapping, and the value
is not twice the size of your largest cache, increase it. Otherwise, just
hit enter to continue.

Enter Maximum cache size (KB) [4096]:

The ATLAS install process is heavily file-based, and this can cause major
reliability problems when interacting with an overloaded or malfunctioning
remotely mounted filesystem. ATLAS therefore has a mechanism in place to
allow for a delay before a file is declared to not be there, so that
slow NFS (i.e., waiting for amd timout) problems can be overcome, or for
handling slightly differing clocks between server/client. This problem is
magnified if doing cross-compilation. In the question below, we ask how
much of a delay, in seconds, ATLAS should tolerate between file creation
and appearance. If you are installing on a local filesystem (eg. /tmp) or
a smooth-running NFS system, answer 0; for a moderately loaded NFS server, you
may want a value in the 10 second range, and for cross-compiling systems or
NFS servers experiencing errors, you may want to go as high as a couple
of minutes (120).

Enter File creation delay in seconds [0]:

Nsee 05-31-2003 04:50 PM

thank you so much i wil tell you how everytihng goes

sao 05-31-2003 04:51 PM

Quote:

I'm going to ask you for information about your Fortran 77 compiler. ATLAS
does not need Fortran77 to build, so if you don't have a Fortran compiler,
the install can still be completed successfully. However, ATLAS built without
a Fortran compiler will not be callable from Fortran (i.e., the user should
use the C interface), and we will not be able to do full testing, since some of
the tester code is written in Fortran77.

Enter f77 compiler [/sw/bin/g77]:
Enter F77 Flags [-funroll-all-loops -O3]:
F77 & FLAGS: /sw/bin/g77 -funroll-all-loops -O3
FLINKER & FLAGS: $(F77) $(F77FLAGS)

CC & FLAGS: /usr/bin/cc -fomit-frame-pointer -O3 -traditional-cpp -faltivec
MCC & FLAGS: /usr/bin/cc -fomit-frame-pointer -O2 -traditional-cpp -fschedule-insns
-fschedule-insns2 -faltivec
CLINKER & FLAGS: $(CC) $(CCFLAGS)

Finding F77 to C calling conventions (this may take a while):

Calculated F77/C interoperation conventions:
Suffix F77 names with underscores with __
F77 INTEGER -> C int
F77 strings handled via standard sun style

The ATLAS team has provided a default install for your architecture. If you
want, these default values can be used, and ATLAS can skip most of the search
for your machine. This will greatly decrease the amount of time required for
the install, allow you to take advantage of any special features found by the
ATLAS team, and provide protection against install miscues caused by unreliable
timing results, assuming you really have the machine ATLAS thinks you have. If
your machine is non-standard in some way, or you just want to see the ATLAS
search for yourself, you should answer no to the following question. Otherwise,
it is highly recommended to accept the default of yes.

Use supplied default values for install? [y]:
After answering this last question, the compilation and tests starts.

sao 05-31-2003 04:53 PM

Once install is done, you can check the following info in /sw/share/doc/atlas:
Quote:

AtlasCredits.txt : The ATLAS team
BootSequence.txt : Rough outline of how the ATLAS install works, and what files it creates.
ChangeLog.txt : Brief summmary of changes from previous releases.
DirStruct.txt : A graphic of the general organization of the ATLAS files
INDEX.txt : This index file again
LibReadme.txt : Information on generated libraries.
TestTime.txt : Information on using the ATLAS testing and timing programs
TroubleShoot.txt : Help with troubleshooting your installation, including where to find more help
Windows.txt : Special information users of Microsoft Windows (95/98/NT/2K) should read
atlas_contrib.ps : Information on how users can speedup and contribute to ATLAS by providing low-level kernel routines
altas_over.ps : Paper describing ideas and basic methods of ATLAS
cblas.ps : Extract of the BLAST standard document, describing the standard C interface to the BLAS.
fblasqr.ps : Quick reference to the F77 interface to the BLAS.

Nsee 05-31-2003 04:55 PM

if there is nothing more too this, that is perfect
thank you very much for your help, youve done so much work on this that i could never have figured out
your probably tired, get some sleep before i end up asking too many questions (<-- joke) (and you probably can see im not too good at them either)

sao 05-31-2003 05:20 PM

Nsee,

I had already installed long ago g77 (the GNU FORTRAN77 compiler) if you don't have it in your machine, when you install the 'atlas' package, Fink will probably install it, as 'atlas' BuildDepends on g77.

Well, is important that you install Fink correctly and set up the environment first. Let me know if you have any problems. Good luck.

Nsee 05-31-2003 05:25 PM

thank you, no need to reply to this one

Nsee 06-01-2003 09:14 PM

This is not an urgent question or a problem, now that I know how to do this, once I am able to do a mathematical transform, how fast does anyone think this will be? Has anyone had any experience with this?
Another point, over the summer I may try to make the equivalent of a mac beowulf cluster to do this, maybe with pooch, its an interesting idea to begin coding.
But these are just pipe dreams, right now I'm thankful I have the instructions.

BTW Sao, you dont need to respond to this extraneous post, you've helped me a lot, and maybe you should rest. :D (maybe one day I'll do jokes well...but today is not the day.........)

hayne 06-01-2003 10:59 PM

speed?
 
Quote:

now that I know how to do this, once I am able to do a mathematical transform, how fast does anyone think this will be?
An African or a European transform? :)

Nsee 06-02-2003 02:29 PM

Oh, yeah, an African transform maybe, but not a European transform. That's my point.

Nsee 06-02-2003 02:43 PM

Quote:

Originally posted by sao

Then, please follow the steps below:

1- Download the Fink Installer from here:

http://fink.sourceforge.net/download/index.php

2- Install Fink:

"Double-click "Fink-0.5.2-Installer.dmg" to mount the disk image, then double-click the "Fink 0.5.2 Installer.pkg" package inside. Follow the instructions on screen".
I have done this part

Nsee 06-02-2003 02:47 PM

fink scanpackages returned this
_________________________________________________________
Information about 1159 packages read in 1 seconds.

dpkg-scanpackages dists/local/main/binary-darwin-powerpc override | gzip >dists/local/main/binary-darwin-powerpc/Packages.gz
Wrote 0 entries to output Packages file.
dpkg-scanpackages dists/stable/main/binary-darwin-powerpc override | gzip >dists/stable/main/binary-darwin-powerpc/Packages.gz
Wrote 0 entries to output Packages file.
dpkg-scanpackages dists/stable/crypto/binary-darwin-powerpc override | gzip >dists/stable/crypto/binary-darwin-powerpc/Packages.gz
Wrote 0 entries to output Packages file.
dpkg-scanpackages dists/local/bootstrap/binary-darwin-powerpc override | gzip >dists/local/bootstrap/binary-darwin-powerpc/Packages.gz
Wrote 0 entries to output Packages file.
_________________________________________________________


All times are GMT -5. The time now is 06:06 PM.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.
Site design © IDG Consumer & SMB; individuals retain copyright of their postings
but consent to the possible use of their material in other areas of IDG Consumer & SMB.