[SAC-HELP] sacio.a for Intel Mac

[Arthur Snoke]

Georgia,

IRIS has two SAC packages: compiled versions for different OS (mac, linux, 
solaris) and a version with source code and makefiles.  The top directory 
in the binaries-only is ./sac and there ;is no ./sac/src.  The top 
directory in the more complete package is ./SAC, and the Makefile is in 
.SAC/src.  (This is all discussed in ./SAC/Readme.buildsac.)  From what 
you say, you have the binaries-only distribution.

The error messages indicates that sacio.a is not being accessed.  As you 
are on an intel mac and the pre-built binaries and sacio.a were built on a 
non-intel mac, even if you have sacio.a in your library path, it probably 
will not work.  (I do not have access to an intel mac, so do not know 
exactly how far rosetta goes in allowing one on Intel mac to use things 
built on non-intel mac.)

Kevin's report is good news -- that it is possible to build sac from 
sources on intel mac and get it to work.  That is the first report I have 
heard along these lines.

Arthur

On Wed, 13 Sep 2006, Georgia Cua wrote:

> Thanks for your reply Kevin.
>
> Are you using the version 100.1 beta?
>
> I also have a macbook pro with intel processors. Thus far, I am using sac 
> v100, and when I untarred the file, there was no /sac/src directory. I 
> actually have a sacio.a file, but when I try linking to it, I get messages 
> like the following..
>
> /usr/bin/ld: warning /Applications/sac/lib/sacio.a archive's cputype (18, 
> architecture ppc) does not match cputype (7) for specified -arch flag: i386 
> (can't load from it)
> /usr/bin/ld: Undefined symbols:
> _getfhv_
> _rsac1_
> _setfhv_
> _setnhv_
> _ttlayr_
> _ttset_
> _wsac0_
> collect2: ld returned 1 exit status
>
> Perhaps I will try  100.1 beta.
>
> Thanks again,
>
>
> Georgia
>
>
> On Sep 12, 2006, at 6:15 PM, Kevin Mayeda wrote:
>
>> Hi Georgia...
>> 
>> I downloaded everything from IRIS.  After untarring
>> the file, I went into /sac/src and found the
>> 'makefile'.   I just simply typed 'make SACIO and it
>> created the sacio.a file in the /sac/lib directory.
>> 
>> Voila!  It worked!
>> 
>> good luck..., let me know if you have issues...,
>> perhaps I can help.  Keep in mind that I have a
>> MacBook Pro w/Intel processors..., your environment
>> might be different.
>> 
>> - Kevin Mayeda