Can Brian or anyone else tell me what the plans are to provide the
sacio.a library for 64 bit machines? This seems an urgent matter to me
because most of us have tons of software that we cannot recompile with
a 32 bit flag without getting into messy problems.
best wishes,
Guust
nolet<at>geoazur.unice.fr
Geosciences Azur
250, Rue Albert Einstein
06560 Sophia Antipolis
France
+33.4.92.94.26.32
http://geoweb.princeton.edu/people/faculty/nolet/
sacio.a library for 64 bit machines? This seems an urgent matter to me
because most of us have tons of software that we cannot recompile with
a 32 bit flag without getting into messy problems.
best wishes,
Guust
nolet<at>geoazur.unice.fr
Geosciences Azur
250, Rue Albert Einstein
06560 Sophia Antipolis
France
+33.4.92.94.26.32
http://geoweb.princeton.edu/people/faculty/nolet/
-
Guust,
We are planning to create a 64 bit friendly version of sacio.a soon.
It is a large undertaking due to the history and age of SAC.
Cheers
Brian
On Feb 26, 2009, at 6:32 AM , Guust Nolet wrote:
Can Brian or anyone else tell me what the plans are to provide the
sacio.a library for 64 bit machines? This seems an urgent matter to
me because most of us have tons of software that we cannot
recompile with a 32 bit flag without getting into messy problems.
best wishes,
Guust
nolet<at>geoazur.unice.fr
Geosciences Azur
250, Rue Albert Einstein
06560 Sophia Antipolis
France
+33.4.92.94.26.32
http://geoweb.princeton.edu/people/faculty/nolet/
_______________________________________________
sac-help mailing list
sac-help<at>iris.washington.edu
http://www.iris.washington.edu/mailman/listinfo/sac-help
-
As a quick and dirty solution maybe you could try to use the -m32 flag
in the compiling time ... don't forgette to install the lib32 version
of libraries.
[]'s
marcelob
2009/2/26 Brian Savage <savage<at>uri.edu>:
Guust,
--
We are planning to create a 64 bit friendly version of sacio.a soon.
It is a large undertaking due to the history and age of SAC.
Cheers
Brian
On Feb 26, 2009, at 6:32 AM , Guust Nolet wrote:
Can Brian or anyone else tell me what the plans are to provide the sacio.a
_______________________________________________
library for 64 bit machines? This seems an urgent matter to me because most
of us have tons of software that we cannot recompile with a 32 bit flag
without getting into messy problems.
best wishes,
Guust
nolet<at>geoazur.unice.fr
Geosciences Azur
250, Rue Albert Einstein
06560 Sophia Antipolis
France
+33.4.92.94.26.32
http://geoweb.princeton.edu/people/faculty/nolet/
_______________________________________________
sac-help mailing list
sac-help<at>iris.washington.edu
http://www.iris.washington.edu/mailman/listinfo/sac-help
sac-help mailing list
sac-help<at>iris.washington.edu
http://www.iris.washington.edu/mailman/listinfo/sac-help
:: "This is all about life !" ::
:: Find me @ http://www.foo4fun.net/ ::
-
Hi!
Because I had the same Problem, I wrote a little sacio module in
Python, which does not depend on sacio.a. Of course this won't solve
the general problem of the 32 bit sacio.a, but maybe it is of interest
to those who only want to be able to read and write some SAC files
from Python.
BTW, -m32 also does not solve the problem, because in a large
application, which uses lots of libraries, all of these libs would
have to be compiled with -m32, which is not always easy. Also -m32
limits the amount of memory the app can address, which prohibits the
most interesting applications.
Cheers,
Sebastian
On 26.02.2009, at 22:16, Marcelo Bianchi wrote:
As a quick and dirty solution maybe you could try to use the -m32 flag
in the compiling time ... don't forgette to install the lib32 version
of libraries.
-
-