Yingcal,
SAC will not compile or run properly in 64 bit mode. You need to
compile it
in 32 bit mode. This is why the configure script insists on putting
the -m32 flag
as a compile time option.
Running SAC on a 64 bit system as a 32 bit binary is not harmful and
does
not show reduced performance.
Cheers,
Brian
On Feb 14, 2008, at 9:36 PM, Yingcai Zheng wrote:
i have the SAC-101.1 source code and i wanted to compile it on my
64bit redhat linux machine and wanted to create
64-bit static .a library.
even i used :
./configure --prefix=mypath CFLAGS=-m64 LDFLAGS=-m64
how come it's still 32-bit library?
here is an output of the
'configure' ...........................................
CFLAGS = -m32 -m32
LDFLAGS = -m32 -m64
LIBS = -ldl -lm -lncurses
Debug =
Optimization =
Database = off
X11-buffer = on
X11-depth = on
X_LIBS = -L/usr/lib64
X_CFLAGS = -I/usr/include
Readline = off
Editline = on
Install Base = /auto/home/yzheng/sftw/sac_source-101.1/sac-101.1
System = linux_x86_64 (x86_64-unknown-linux-gnu)
thanks. yingcai
_______________________________________________
sac-help mailing list
sac-help<at>iris.washington.edu
http://www.iris.washington.edu/mailman/listinfo/sac-help
ying
Brian Savage
NSF SAGE Facility has been
certified as a trustworthy data repository
by the CoreTrustSeal Standards and Certification Board
