Thread: Re: sacio.a for Intel Mac

Started: 2006-09-13 17:17:18
Last activity: 2006-09-13 17:17:18
Topics: SAC Help
Georgia Cua
2006-09-13 17:17:18
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


--- Georgia Cua <georgia.cua<at>sed.ethz.ch> wrote:

Dear Kevin,

I am a bit embarrassed to ask this question..

but how did you compile sacio.a with your c
compiler? (I usually just
use rsac and wsac, so your solution would work fine
for me..)

Thanks,
Georgia


On Sep 4, 2006, at 7:14 PM, Kevin Mayeda wrote:

All-

I've scripted with SAC macros for over 14 years
and
need some advice on how to make the full
transition to
the Intel MacBook Pro.

I've got the latest version of SAC to work on my
Mac,
but I use a fair amount of IO with Fortran codes
(I
use WSAC, RSAC, WBBF, WBBV etc). I compiled
sacio.a
on my machine using the Mac's C-compiler and WSAC
and
RSAC work just fine (80% of my battle). However,
the
subroutines related to the blackboad variables and
blackboard variable files do not work (but no
error is
given). Peter Goldstein thinks it must be
something
fairly trivial, but unfortunately, I'm not versed
in C
and need some help/suggestions.

One possibility that he brought up, was building
sacio.a using the old fortran codes. What do you
think of this? I only have the C-codes (from
IRIS),
but I think I'm very close to shedding my
dependence
on SUN Unix that I'm hopeful there is a solution
around the corner.

thanks in advance...

- Kevin Mayeda


__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam
protection around
http://mail.yahoo.com
_______________________________________________
sac-help mailing list
sac-help<at>iris.washington.edu


http://www.iris.washington.edu/mailman/listinfo/sac-help



-----------------------------
Dr. Georgia Cua
Swiss Seismological Service
Institute of Geophysics
ETH Hoenggerberg HPP P
CH-8093 Zurich
Switzerland

Tel: +41-044-633-7574
Fax: +41-044-633-1065

georgia.cua<at>sed.ethz.ch
-----------------------------





__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com



-----------------------------
Dr. Georgia Cua
Swiss Seismological Service
Institute of Geophysics
ETH Hoenggerberg HPP P
CH-8093 Zurich
Switzerland

Tel: +41-044-633-7574
Fax: +41-044-633-1065

georgia.cua<at>sed.ethz.ch
-----------------------------



  • Arthur Snoke
    2006-09-13 15:25:04
    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

Page built 08:13:57 | v.b'ea7a92