From: Charlie Zender <zender@uci.edu>
To: GSL Discussion List <gsl-discuss@sources.redhat.com>
Subject: disable shared libs to build on AIX, Alpha
Date: Wed, 19 Dec 2001 13:20:00 -0000 [thread overview]
Message-ID: <200108091801.f79I16W20231@cgd85.cgd.ucar.edu> (raw)
Hi,
A few days ago I reported that building GSL 0.9 failed on AIX.
Brian Gough suggested that the problem was with libtool.
Although I was unable to build libtool from scratch on our AIX
system, I did learn through trial and error that GSL 0.9 built
fine if I simply turned off the shareable library features, i.e.,
babyblue.ucar.edu AIX 4.3.3:
setenv CC 'xlc'
setenv CFLAGS '-O -qmaxmem=8192'
./configure --disable-shared --disable-libtool-lock
make --jobs=1
works for me with AIX.
I also successfully built GSL 0.9 on our 8 processor compaq alpha
system. There, the shareable libraries built fine, but my executables
could not link to them at run time, and died with a system error
"cannot map libgsl.so". Once again, removing the shared libraries
did the trick, and the static libraries work fine.
prospect.ucar.edu ev6-dec-osf5.0 OSF1:
setenv CC 'cc'
setenv CFLAGS '-O2'
./configure --disable-shared
This suggests to me that some sort of installation hint be given to
user's of "exotic" systems that they try turning of the shared
libraries if GSL does not build or link correctly the first time.
Charlie
--
Charlie Zender zender@uci.edu (949) 824-2987/FAX-3256, Department of
Earth System Science, University of California, Irvine CA 92697-3100
Visiting NCAR CGD Jul 1-Aug 31: Room ML-304A (303) 497-1738/FAX-1324
Work Address: NCAR CGD, 1850 Table Mesa Dr., Boulder, CO, 80303-5602
next reply other threads:[~2001-12-19 13:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-19 13:20 Charlie Zender [this message]
2001-12-19 13:20 ` Brian Gough
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200108091801.f79I16W20231@cgd85.cgd.ucar.edu \
--to=zender@uci.edu \
--cc=gsl-discuss@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).