Re: Problem Compiling QuantLib 0.3.11 on Solaris 5.8
Posted by
Xavier.Abulker on
URL: http://quantlib.414.s1.nabble.com/Re-Problem-Compiling-QuantLib-0-3-11-on-Solaris-5-8-tp4359p4363.html
Hi Luigi
thank you for your answer.
I've tried to manually removed M_PI
in the config.hpp with:
/* pi */
//#define M_PI 3.141592653589793238462643383280
and the error is still the same:
source='parcoupon.cpp' object='parcoupon.lo'
libtool=yes \
DEPDIR=.deps depmode=none /bin/bash
../../config/depcomp \
/bin/bash ../../libtool --tag=CXX
--mode=compile CC -DHAVE_CONFIG_H -I. -I. -I../../ql -I../..
-I../.. -I/usr/local/include/boost-1_33_1/ -I/export/home/xavier/studio/SUNWspro/include
-L/usr/local/lib -L/export/home/xavier/studio/SUNWspro/include -g
-O2 -Wall -c -o parcoupon.lo parcoupon.cpp
CC -DHAVE_CONFIG_H -I. -I.
-I../../ql -I../.. -I../.. -I/usr/local/include/boost-1_33_1/ -I/export/home/xavier/studio/SUNWspro/include
-L/usr/local/lib -L/export/home/xavier/studio/SUNWspro/include -g -O2 -Wall
-c parcoupon.cpp -KPIC -DPIC -o .libs/parcoupon.o
CC: Warning: Option -Wall passed
to ld, if ld is invoked, ignored otherwise
>> Assertion:
(../lnk/init.cc, line 1032)
while processing ../../ql/history.hpp
at line 135.
*** Error code 1
I'm wondering if I correclty setup
the environement variables.
Whta I use is:
export CPPFLAGS='-I/usr/local/include/boost-1_33_1/
-I/ /export/home/xavier/studio/SUNWspro/include -L/usr/local/lib –L/export/home/xavier/studio/SUNWspro/include
'
export LDFLAGS=’-I/usr/local/include/boost-1_33_1/
-I/ /export/home/xavier/studio/SUNWspro/lib –I/usr/local/lib’
Is it how I should setup these
variables?
Thank you
Xavier
On 1/18/06, [hidden email] <[hidden email]> wrote:
> I am getting below error while compiling the Quantlib 0.3.11
on solaris 5.8
> Unix box with CC .
Hmm. From the log, what happens is that including <cmath> does not
cause M_PI to be defined, so ./configure tells QuantLib to define it
itself. Afterwards, some other header is included which defines M_PI,
causing it to be defined twice.
Why this happens is beyond me. Maybe you can track the files that get
included and see why the configure test fails?
As a workaround, you can try and manually edit ql/config.hpp after
./configure creates it so that M_PI is not defined. I'm not sure what
will happen, but you can give it a try.
Later,
Luigi
*************************************************************************
Ce message et toutes les pieces jointes (ci-apres le "message")
sont
confidentiels et etablis a l'intention exclusive de ses destinataires.
Toute utilisation ou diffusion non autorisee est interdite.
Tout message electronique est susceptible d'alteration.
La FIMAT et ses filiales declinent toute responsabilite
au titre de ce message s'il a ete altere, deforme ou falsifie.
********
This message and any attachments (the "message") are confidential
and
intended solely for the addressees.
Any unauthorised use or dissemination is prohibited.
E-mails are susceptible to alteration.
Neither FIMAT nor any of its subsidiaries or affiliates
shall be liable for the message if altered,
changed or falsified.
*************************************************************************
Ce message et toutes les pieces jointes (ci-apres le "message") sont
confidentiels et etablis a l'intention exclusive de ses destinataires.
Toute utilisation ou diffusion non autorisee est interdite.
Tout message electronique est susceptible d'alteration.
La FIMAT et ses filiales declinent toute responsabilite
au titre de ce message s'il a ete altere, deforme ou falsifie.
********
This message and any attachments (the "message") are confidential and
intended solely for the addressees.
Any unauthorised use or dissemination is prohibited.
E-mails are susceptible to alteration.
Neither FIMAT nor any of its subsidiaries or affiliates
shall be liable for the message if altered,
changed or falsified.
|