A forum for SAC users to exchange ideas and ask questions about SAC usage, installation, portability, etc.
This list has moved to https://groups.google.com/a/earthscope.org/g/sac-community.
- Email address
- sac-help@lists.ds.iris.edu
- Type
-
Help
Help lists are for submitting support questions. Anyone can post a question for SAGE (or another team) to answer.
- Moderated by
- IRIS Webmaster
- Related tags
- SAC Software SAC
April
March
February
January
March
February
January
December
November
October
September (1)
August
July
June (4)
May (11)
April (3)
March (5)
February (2)
January (8)
November
October
September (1)
August
July
June (4)
May (11)
April (3)
March (5)
February (2)
January (8)
Active Message Threads for February 2010
Norman Heckscher
Hi Derek,
Over the last few days I have been attempting to move to a pure 64 bit
environment. I am currently working with Ubuntu 9.10. During the
process I have attempted to compile SAC as a pure 64 bit application.
I encountered a similar error to yours during the compile process. I
have managed to successfully compile SAC by editing the following file
and commenting out the header code which defines getline on my system.
Comment out the following code from /usr/include/stdio.h
##########…
[more]
No replies
Derek Schutt
2009-09-08 17:07:12
- 2010-02-22 23:43:22
Hi,
I've been trying to install SAC on my Fedora 11 box (kernel
2.6.29.6-217.2.8.fc11.x86_64), but I've run into a compilation problem:
When I do a no-option configure, then type "make", I get:
>make
Making all in libedit
make[1]: Entering directory `/usr/local/build/libedit'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/usr/local/build/libedit'
Making all in utils
make[1]: Entering directory `/usr/local/build/utils'
make[1]: Nothing to…
[more]
Replies
-
Re: troubles compiling sac 101.3b on 64-bit linux (Fedora 11) - Norman Heckscher - 2010-02-22 23:43:22
Rob_Porritt
Hi all,
I've recently downloaded sac101.3b. I want to use the libraries (libsac.a)
and so proceeded through the examples in the documentation, but the makefile
returned errors. I was able to make it by adding -I../../include,
-L../../lib, and -lm to the FFLAGS and CFLAGS:
FFLAGS=-Wall `sac-config --cflags` -I../../include -L../../lib -lm
CFLAGS=-Wall `sac-config --cflags` -I../../include -L../../lib -lm
I also had to add a standard header to wsac5c.c to define INT32_MAX
#include <stdint.h>
H…
[more]
No replies
Fiona Darbyshire
I inherited a code for conversion of SAC to ASCII with extra information
going into the top of the ASCII file (ready for input to another program).
It's something I haven't used for quite some time and I've installed SAC
101.2 since the last time I used it. Something seems to have changed with
respect to some of the data formatting, so I recompiled the source code and
reran it. This solved one of my data formatting problems, but appears to
have created another. There appears to be some spurious…
[more]
