You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
(60) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(18) |
Feb
(4) |
Mar
(6) |
Apr
(2) |
May
|
Jun
(12) |
Jul
(48) |
Aug
(6) |
Sep
(3) |
Oct
(24) |
Nov
(15) |
Dec
(18) |
| 2002 |
Jan
(39) |
Feb
(12) |
Mar
(80) |
Apr
(72) |
May
(46) |
Jun
(27) |
Jul
(23) |
Aug
(34) |
Sep
(65) |
Oct
(71) |
Nov
(19) |
Dec
(14) |
| 2003 |
Jan
(44) |
Feb
(59) |
Mar
(18) |
Apr
(62) |
May
(54) |
Jun
(27) |
Jul
(46) |
Aug
(15) |
Sep
(44) |
Oct
(36) |
Nov
(19) |
Dec
(12) |
| 2004 |
Jan
(26) |
Feb
(33) |
Mar
(47) |
Apr
(63) |
May
(36) |
Jun
(65) |
Jul
(80) |
Aug
(163) |
Sep
(65) |
Oct
(39) |
Nov
(36) |
Dec
(39) |
| 2005 |
Jan
(97) |
Feb
(78) |
Mar
(64) |
Apr
(64) |
May
(48) |
Jun
(55) |
Jul
(89) |
Aug
(57) |
Sep
(51) |
Oct
(111) |
Nov
(86) |
Dec
(76) |
| 2006 |
Jan
(84) |
Feb
(103) |
Mar
(143) |
Apr
(92) |
May
(55) |
Jun
(58) |
Jul
(71) |
Aug
(57) |
Sep
(74) |
Oct
(59) |
Nov
(8) |
Dec
(32) |
| 2007 |
Jan
(60) |
Feb
(40) |
Mar
(50) |
Apr
(26) |
May
(61) |
Jun
(120) |
Jul
(119) |
Aug
(48) |
Sep
(121) |
Oct
(66) |
Nov
(103) |
Dec
(43) |
| 2008 |
Jan
(60) |
Feb
(109) |
Mar
(92) |
Apr
(106) |
May
(82) |
Jun
(59) |
Jul
(67) |
Aug
(118) |
Sep
(131) |
Oct
(56) |
Nov
(37) |
Dec
(69) |
| 2009 |
Jan
(75) |
Feb
(76) |
Mar
(103) |
Apr
(78) |
May
(61) |
Jun
(35) |
Jul
(66) |
Aug
(69) |
Sep
(166) |
Oct
(46) |
Nov
(72) |
Dec
(65) |
| 2010 |
Jan
(48) |
Feb
(57) |
Mar
(93) |
Apr
(85) |
May
(123) |
Jun
(82) |
Jul
(98) |
Aug
(121) |
Sep
(146) |
Oct
(86) |
Nov
(72) |
Dec
(34) |
| 2011 |
Jan
(96) |
Feb
(55) |
Mar
(73) |
Apr
(57) |
May
(33) |
Jun
(74) |
Jul
(89) |
Aug
(71) |
Sep
(103) |
Oct
(76) |
Nov
(52) |
Dec
(61) |
| 2012 |
Jan
(48) |
Feb
(54) |
Mar
(78) |
Apr
(60) |
May
(75) |
Jun
(59) |
Jul
(33) |
Aug
(66) |
Sep
(43) |
Oct
(46) |
Nov
(75) |
Dec
(51) |
| 2013 |
Jan
(112) |
Feb
(72) |
Mar
(49) |
Apr
(48) |
May
(42) |
Jun
(44) |
Jul
(80) |
Aug
(19) |
Sep
(33) |
Oct
(37) |
Nov
(38) |
Dec
(98) |
| 2014 |
Jan
(113) |
Feb
(93) |
Mar
(49) |
Apr
(106) |
May
(97) |
Jun
(155) |
Jul
(87) |
Aug
(127) |
Sep
(85) |
Oct
(48) |
Nov
(41) |
Dec
(37) |
| 2015 |
Jan
(34) |
Feb
(50) |
Mar
(104) |
Apr
(80) |
May
(82) |
Jun
(66) |
Jul
(41) |
Aug
(84) |
Sep
(37) |
Oct
(65) |
Nov
(83) |
Dec
(52) |
| 2016 |
Jan
(68) |
Feb
(35) |
Mar
(42) |
Apr
(35) |
May
(54) |
Jun
(75) |
Jul
(45) |
Aug
(52) |
Sep
(60) |
Oct
(52) |
Nov
(36) |
Dec
(64) |
| 2017 |
Jan
(92) |
Feb
(59) |
Mar
(35) |
Apr
(53) |
May
(83) |
Jun
(43) |
Jul
(65) |
Aug
(68) |
Sep
(46) |
Oct
(75) |
Nov
(40) |
Dec
(49) |
| 2018 |
Jan
(68) |
Feb
(54) |
Mar
(48) |
Apr
(58) |
May
(51) |
Jun
(44) |
Jul
(40) |
Aug
(68) |
Sep
(35) |
Oct
(15) |
Nov
(7) |
Dec
(37) |
| 2019 |
Jan
(43) |
Feb
(7) |
Mar
(22) |
Apr
(21) |
May
(31) |
Jun
(39) |
Jul
(73) |
Aug
(45) |
Sep
(47) |
Oct
(89) |
Nov
(19) |
Dec
(69) |
| 2020 |
Jan
(52) |
Feb
(63) |
Mar
(45) |
Apr
(59) |
May
(42) |
Jun
(57) |
Jul
(30) |
Aug
(29) |
Sep
(75) |
Oct
(64) |
Nov
(96) |
Dec
(22) |
| 2021 |
Jan
(14) |
Feb
(24) |
Mar
(35) |
Apr
(58) |
May
(36) |
Jun
(15) |
Jul
(18) |
Aug
(31) |
Sep
(30) |
Oct
(33) |
Nov
(27) |
Dec
(16) |
| 2022 |
Jan
(35) |
Feb
(22) |
Mar
(14) |
Apr
(20) |
May
(44) |
Jun
(53) |
Jul
(25) |
Aug
(56) |
Sep
(11) |
Oct
(47) |
Nov
(22) |
Dec
(36) |
| 2023 |
Jan
(30) |
Feb
(17) |
Mar
(31) |
Apr
(48) |
May
(31) |
Jun
(7) |
Jul
(25) |
Aug
(26) |
Sep
(61) |
Oct
(66) |
Nov
(19) |
Dec
(21) |
| 2024 |
Jan
(37) |
Feb
(29) |
Mar
(26) |
Apr
(26) |
May
(34) |
Jun
(9) |
Jul
(27) |
Aug
(13) |
Sep
(15) |
Oct
(25) |
Nov
(13) |
Dec
(8) |
| 2025 |
Jan
(13) |
Feb
(1) |
Mar
(16) |
Apr
(17) |
May
(8) |
Jun
(6) |
Jul
(9) |
Aug
|
Sep
(6) |
Oct
(15) |
Nov
(6) |
Dec
|
| 2026 |
Jan
(6) |
Feb
(4) |
Mar
(20) |
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Daniel L. <dan...@gm...> - 2022-05-04 04:50:51
|
Hi,
I still get the same error message as below,
$ ./configure --with-boost-include=usr/include/boost
--with-boost-lib=/usr/lib/x86_64-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a race-free mkdir -p... /usr/bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... no
checking whether make supports nested variables... no
checking whether UID '1000' is supported by ustar format... yes
checking whether GID '1000' is supported by ustar format... yes
checking how to create a ustar tar archive... gnutar
checking for gawk... (cached) mawk
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether gcc accepts -g... yes
checking for gcc option to enable C11 features... none needed
checking whether gcc understands -c and -o together... yes
checking whether make supports the include directive... no
checking dependency style of gcc... none
checking for g++... no
checking for c++... no
checking for gpp... no
checking for aCC... no
checking for CC... no
checking for cxx... no
checking for cc++... no
checking for cl.exe... no
checking for FCC... no
checking for KCC... no
checking for RCC... no
checking for xlC_r... no
checking for xlC... no
checking for clang++... no
checking whether the compiler supports GNU C++... no
checking whether g++ accepts -g... no
checking for g++ option to enable C++11 features... none needed
checking dependency style of g++... none
checking how to run the C preprocessor... gcc -E
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking how to print strings... printf
checking for a sed that does not truncate output... /usr/bin/sed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking how to convert x86_64-pc-linux-gnu file names to
x86_64-pc-linux-gnu format... func_convert_file_noop
checking how to convert x86_64-pc-linux-gnu file names to toolchain
format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for a working dd... /usr/bin/dd
checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1
checking for mt... mt
checking if mt is a manifest tool... no
checking for stdio.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports
shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for C++11 support... no: adding -std=c++11 to CXXFLAGS
checking for Boost development files... no
configure: error: Boost development files not found
Below is the outputs from configure file (configure.ac)
# Process this file with autoconf to produce a configure script.
AC_INIT([QuantLib], [1.26],
[qua...@li...],
[QuantLib])
AC_PREREQ(2.62)
AC_CONFIG_SRCDIR([ql/qldefines.hpp])
AC_CONFIG_AUX_DIR([config])
AC_CONFIG_HEADERS([ql/config.hpp])
AM_INIT_AUTOMAKE([foreign nostdinc subdir-objects tar-ustar])
AC_CONFIG_MACRO_DIR([m4])
AC_COPYRIGHT([
Copyright (C) 2000, 2001, 2002, 2003 RiskMap srl
Copyright (C) 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010 StatPro Italia srl
Copyright (C) 2004, 2005 Ferdinando Ametrano
This file is part of QuantLib, a free-software/open-source library
for financial quantitative analysts and developers - http://quantlib.org/
QuantLib is free software: you can redistribute it and/or modify it
under the terms of the QuantLib license. You should have received a
copy of the license along with this program; if not, please email
<qua...@li...>. The license is also available online at
<http://quantlib.org/license.shtml>.
This program is distributed in the hope that it will be useful, but WITHOUT
ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
FOR A PARTICULAR PURPOSE. See the license for more details.])
AC_PROG_AWK
AC_PROG_INSTALL
# Help the compiler find external software
AC_ARG_WITH([boost-include],
AS_HELP_STRING([--with-boost-include=INCLUDE_PATH],
[Supply the location of Boost header files]),
[ql_boost_include_path="`cd ${withval} 2>/dev/null && pwd`"],
[ql_boost_include_path=""])
if test [ -n "$ql_boost_include_path" ] ; then
AC_SUBST([BOOST_INCLUDE],["-I${ql_boost_include_path}"])
AC_SUBST([CPPFLAGS],["${CPPFLAGS} -I${ql_boost_include_path}"])
fi
AC_ARG_WITH([boost-lib],
AS_HELP_STRING([--with-boost-lib=LIB_PATH],
[Supply the location of Boost libraries]),
[ql_boost_lib_path="`cd ${withval} 2>/dev/null && pwd`"],
[ql_boost_lib_path=""])
if test [ -n "$ql_boost_lib_path" ] ; then
AC_SUBST([BOOST_LIB],["-L${ql_boost_lib_path}"])
AC_SUBST([LDFLAGS],["${LDFLAGS} -L${ql_boost_lib_path}"])
fi
# Continue setup
AC_PROG_CC
AC_PROG_CXX
AC_PROG_CPP
LT_INIT
AM_CONDITIONAL(ENABLE_STATIC, test "${enable_static}" == "yes")
AC_LANG([C++])
AC_ARG_ENABLE([openmp],
AS_HELP_STRING([--enable-openmp],
[If enabled, configure will try to detect
and enable OpenMP support.]),
[ql_openmp=$enableval],
[ql_openmp=no])
if test "$ql_openmp" = "yes" ; then
AC_OPENMP
AC_SUBST([CXXFLAGS],["${CXXFLAGS} ${OPENMP_CXXFLAGS}"])
fi
# Check for C++11 support
QL_CHECK_CPP11
# Check for Boost components
QL_CHECK_BOOST
AM_CONDITIONAL(BOOST_UNIT_TEST_FOUND, test "x${BOOST_UNIT_TEST_LIB}" != "x")
# Check for Emacs
AM_PATH_LISPDIR
AM_CONDITIONAL(EMACS_FOUND, test "${EMACS}" != "no")
# Check for tools needed for building documentation
AC_PATH_PROG([DOXYGEN], [doxygen])
AC_PATH_PROG([SED], [sed])
AC_PATH_PROG([LATEX], [latex])
AC_PATH_PROG([PDFLATEX], [pdflatex])
AC_PATH_PROG([MAKEINDEX], [makeindex])
AC_PATH_PROG([DVIPS], [dvips])
# site configuration
# AC_ARG_WITH([real],
# AS_HELP_STRING([--with-real=type],
# [The given type will be used for floating-point
# calculations.
# In case this option is not invoked, double
# will be used.]),
# [AC_DEFINE_UNQUOTED([QL_REAL],[$withval],
# [Define this as the type to be used for
# floating-point calculations.])],
# [AC_DEFINE_UNQUOTED([QL_REAL],[double],
# [Define this as the type to be used for
# floating-point calculations.])])
# AC_ARG_WITH([integer],
# AS_HELP_STRING([--with-integer=type],
# [The given type will be used for integer
# calculations. At least an int is required.
# In case this option is not invoked, int
# will be used.]),
# [AC_DEFINE_UNQUOTED([QL_INTEGER],[$withval],
# [Define this as the type to be used for
# integer calculations. At least an int
# is required.])],
# [AC_DEFINE_UNQUOTED([QL_INTEGER],[int],
# [Define this as the type to be used for
# integer calculations. At least an int
# is required.])])
# AC_ARG_WITH([big-integer],
# AS_HELP_STRING([--with-big-integer=type],
# [The given type will be used for large integer
# calculations. At least 4 bytes are required.
# In case this option is not invoked, long
# will be used.]),
# [AC_DEFINE_UNQUOTED([QL_BIG_INTEGER],[$withval],
# [Define this as the type to be used for
# large integer calculations. At least
# 4 bytes are required.])],
# [AC_DEFINE_UNQUOTED([QL_BIG_INTEGER],[long],
# [Define this as the type to be used for
# large integer calculations. At least
# 4 bytes are required.])])
AC_ARG_ENABLE([error-lines],
AS_HELP_STRING([--enable-error-lines],
[If enabled, file and line information is
added to the error messages thrown by
the library.]),
[ql_error_lines=$enableval],
[ql_error_lines=no])
AC_MSG_CHECKING([whether to add file and line information to errors])
if test "$ql_error_lines" = "yes" ; then
AC_DEFINE([QL_ERROR_LINES],[1],
[Define this if error messages should include file and line
information.])
fi
AC_MSG_RESULT([$ql_error_lines])
AC_ARG_ENABLE([error-functions],
AS_HELP_STRING([--enable-error-functions],
[If enabled, current function information
is added to the error messages thrown by
the library.]),
[ql_error_functions=$enableval],
[ql_error_functions=no])
AC_MSG_CHECKING([whether to add function information to errors])
if test "$ql_error_functions" = "yes" ; then
AC_DEFINE([QL_ERROR_FUNCTIONS],[1],
[Define this if error messages should include current function
information.])
fi
AC_MSG_RESULT([$ql_error_functions])
AC_ARG_ENABLE([tracing],
AS_HELP_STRING([--enable-tracing],
[If enabled, tracing messages might be emitted
by the library depending on run-time
settings. Enabling this option can degrade
performance.]),
[ql_tracing=$enableval],
[ql_tracing=no])
AC_MSG_CHECKING([whether to enable tracing])
if test "$ql_tracing" = "yes" ; then
AC_DEFINE([QL_ENABLE_TRACING],[1],
[Define this if tracing messages should allowed (whether they
are actually emitted will depend on run-time settings.)])
fi
AC_MSG_RESULT([$ql_tracing])
AC_MSG_CHECKING([whether to enable indexed coupons])
AC_ARG_ENABLE([indexed-coupons],
AS_HELP_STRING([--enable-indexed-coupons],
[If enabled, indexed coupons (see the
documentation) are used in floating legs.
If disabled (the default), par coupons
are used.]),
[ql_indexed_coupon=$enableval],
[ql_indexed_coupon=no])
if test "$ql_indexed_coupon" = "yes" ; then
AC_DEFINE([QL_USE_INDEXED_COUPON],[1],
[Define this to use indexed coupons instead of par coupons in
floating legs.])
fi
AC_MSG_RESULT([$ql_indexed_coupon])
AC_MSG_CHECKING([whether to enable extra safety checks])
AC_ARG_ENABLE([extra-safety-checks],
AS_HELP_STRING([--enable-extra-safety-checks],
[If enabled, extra run-time checks are added
to a few functions. This can prevent their
inlining and degrade performance.]),
[ql_belt_and_braces=$enableval],
[ql_belt_and_braces=no])
if test "$ql_belt_and_braces" = "yes" ; then
AC_DEFINE([QL_EXTRA_SAFETY_CHECKS],[1],
[Define this if extra safety checks should be performed.
This can degrade performance.])
fi
AC_MSG_RESULT([$ql_belt_and_braces])
AC_MSG_CHECKING([whether to enable sessions])
AC_ARG_ENABLE([sessions],
AS_HELP_STRING([--enable-sessions],
[If enabled, singletons will return different
instances for different sessions. You will
have to provide and link with the library
a sessionId() function in namespace QuantLib,
returning a different session id for each
session. This also implies thread-safe
Singleton initialization.]),
[ql_use_sessions=$enableval],
[ql_use_sessions=no])
if test "$ql_use_sessions" = "yes" ; then
AC_DEFINE([QL_ENABLE_SESSIONS],[1],
[Define this if you want to enable sessions.])
fi
AC_MSG_RESULT([$ql_use_sessions])
AC_MSG_CHECKING([whether to enable thread-safe observer pattern])
AC_ARG_ENABLE([thread-safe-observer-pattern],
AS_HELP_STRING([--enable-thread-safe-observer-pattern],
[If enabled, thread-safe version of the
observer pattern will be used. You should
enable it if you want to use QuantLib
via the SWIG layer within the JVM or .NET
eco system or any environment with an
async garbage collector. C++-17 is required
if this option is used together with
--enable-std-pointers]),
[ql_use_tsop=$enableval],
[ql_use_tsop=no])
AC_MSG_RESULT([$ql_use_tsop])
if test "$ql_use_tsop" = "yes" ; then
AC_DEFINE([QL_ENABLE_THREAD_SAFE_OBSERVER_PATTERN],[1],
[Define this if you want to enable
thread-safe observer pattern.])
fi
AC_MSG_CHECKING([whether to enable thread-safe singleton initialization])
AC_ARG_ENABLE([thread-safe-singleton-init],
AS_HELP_STRING([--enable-thread-safe-singleton-init],
[If enabled, singleton initialization will
be thread-safe. This requires Boost 1.58
or later. Note that --enable-sessions
implies thread-safe initialization,
whether this is defined or not]),
[ql_use_safe_singleton_init=$enableval],
[ql_use_safe_singleton_init=no])
if test "$ql_use_safe_singleton_init" = "yes" ; then
AC_DEFINE([QL_ENABLE_SINGLETON_THREAD_SAFE_INIT],[1],
[Define this if you want thread-safe singleton initialization.])
fi
AC_MSG_RESULT([$ql_use_safe_singleton_init])
if test "$ql_use_sessions" = "yes" || test "$ql_use_tsop" = "yes" ||
test "$ql_use_safe_singleton_init" = "yes"; then
QL_CHECK_BOOST_VERSION_1_58_OR_HIGHER
QL_CHECK_BOOST_TEST_THREAD_SIGNALS2_SYSTEM
else
AC_SUBST([BOOST_THREAD_LIB],[""])
fi
AC_MSG_CHECKING([whether to enable parallel unit test runner])
AC_ARG_ENABLE([parallel-unit-test-runner],
AS_HELP_STRING([--enable-parallel-unit-test-runner],
[If enabled, a parallel unit test runner is used
to execute the C++ test suite. This will reduce
the runtime on multi core CPUs.]),
[ql_use_parallel_test=$enableval],
[ql_use_parallel_test=no])
AC_MSG_RESULT([$ql_use_parallel_test])
if test "$ql_use_parallel_test" = "yes" ; then
AC_DEFINE([QL_ENABLE_PARALLEL_UNIT_TEST_RUNNER],[1],
[Define this if you want to enable
the parallel unit test runner.])
QL_CHECK_BOOST_VERSION_1_59_OR_HIGHER
if test "$ql_use_tsop" != "yes" ; then
QL_CHECK_BOOST_TEST_THREAD_SIGNALS2_SYSTEM
fi
QL_CHECK_BOOST_TEST_INTERPROCESS
else
AC_SUBST([BOOST_INTERPROCESS_LIB],[""])
fi
AC_MSG_CHECKING([whether to install examples])
AC_ARG_ENABLE([examples],
AS_HELP_STRING([--enable-examples],
[If enabled, examples are built and installed
when "make" and "make install" are invoked.
If disabled (the default) they are built
but not installed.]),
[ql_install_examples=$enableval],
[ql_install_examples=no])
AM_CONDITIONAL(AUTO_EXAMPLES, test "$ql_install_examples" != "no")
AC_MSG_RESULT([$ql_install_examples])
AC_MSG_CHECKING([whether to install the benchmark])
AC_ARG_ENABLE([benchmark],
AS_HELP_STRING([--enable-benchmark],
[If enabled, the benchmark is built and
installed when "make" and "make install"
are invoked. If disabled (the default)
it is built but not installed.]),
[ql_install_benchmark=$enableval],
[ql_install_benchmark=no])
AM_CONDITIONAL(AUTO_BENCHMARK, test "$ql_install_benchmark" != "no")
AC_MSG_RESULT([$ql_install_benchmark])
AC_MSG_CHECKING([whether to use unity build])
AC_ARG_ENABLE([unity-build],
AS_HELP_STRING([--enable-unity-build],
[If enabled, the source files in each directory
are collected into one single source file and
compiled together. This can speed up the
compilation of the library.
If disabled (the default) each source file is
compiled separately..]),
[ql_use_unity_build=$enableval],
[ql_use_unity_build=no])
AM_CONDITIONAL(UNITY_BUILD, test "$ql_use_unity_build" != "no")
AC_MSG_RESULT([$ql_use_unity_build])
AC_MSG_CHECKING([whether to enable intraday date and daycounters])
AC_ARG_ENABLE([intraday],
AS_HELP_STRING([--enable-intraday],
[If enabled, date objects will support an intraday
datetime resolution down to microseconds.
Strickly monotone daycounters (Actual360,
Actual365Fixed and ActualActual) will take
the additional information into account
and allow for accurate intraday pricing.
If disabled (the default) the smallest
resolution of date objects will be a single day.
Intraday datetime resolution is experimental.]),
[ql_use_intraday=$enableval],
[ql_use_intraday=no])
if test "$ql_use_intraday" = "yes" ; then
AC_DEFINE([QL_HIGH_RESOLUTION_DATE],[1],
[Define this if you want to enable high resolution date class.])
fi
AC_MSG_RESULT([$ql_use_intraday])
AC_MSG_CHECKING([whether to enable standard smart pointers])
AC_ARG_ENABLE([std-pointers],
AS_HELP_STRING([--enable-std-pointers],
[If enabled, std::shared_ptr and related
classes and functions will be used instead
of boost::shared_ptr.
If disabled (the default) the Boost facilities
are used.
Note that std::shared_ptr does not check
access and can cause segmentation faults.]),
[ql_use_std_pointers=$enableval],
[ql_use_std_pointers=no])
if test "$ql_use_std_pointers" = "yes" ; then
AC_DEFINE([QL_USE_STD_SHARED_PTR],[1],
[Define this if you want to use standard smart pointers.])
fi
AC_MSG_RESULT([$ql_use_std_pointers])
AC_MSG_CHECKING([whether to enable std::unique_ptr instead of std::auto_ptr])
AC_ARG_ENABLE([std-unique-ptr],
AS_HELP_STRING([--enable-std-unique-ptr],
[If enabled (the default), std::unique_ptr will
be used instead of the deprecated std::auto_ptr.
If disabled, std::auto_ptr will still be used.]),
[ql_use_unique_ptr=$enableval],
[ql_use_unique_ptr=yes])
if test "$ql_use_unique_ptr" = "yes" ; then
AC_DEFINE([QL_USE_STD_UNIQUE_PTR],[1],
[Define this if you want to replace std::auto_ptr with
std::unique_ptr.])
fi
AC_MSG_RESULT([$ql_use_unique_ptr])
AC_MSG_CHECKING([whether to enable std::function])
AC_ARG_ENABLE([std-function],
AS_HELP_STRING([--enable-std-function],
[If enabled, std::function and std::bind will be
used instead of boost::function and boost::bind.
If disabled (the default) the Boost facilities
are used.]),
[ql_use_std_function=$enableval],
[ql_use_std_function=no])
if test "$ql_use_std_function" = "yes" ; then
AC_DEFINE([QL_USE_STD_FUNCTION],[1],
[Define this if you want to use std::function and std::bind.])
fi
AC_MSG_RESULT([$ql_use_std_function])
AC_MSG_CHECKING([whether to enable std::tuple])
AC_ARG_ENABLE([std-tuple],
AS_HELP_STRING([--enable-std-tuple],
[If enabled, std::tuple and related functions
will be used instead of boost::tuple.
If disabled (the default) the Boost facilities
are used.]),
[ql_use_std_tuple=$enableval],
[ql_use_std_tuple=no])
if test "$ql_use_std_tuple" = "yes" ; then
AC_DEFINE([QL_USE_STD_TUPLE],[1],
[Define this if you want to use std::tuple.])
fi
AC_MSG_RESULT([$ql_use_std_pointers])
AC_MSG_CHECKING([whether to enable available std classes])
AC_ARG_ENABLE([std-classes],
AS_HELP_STRING([--enable-std-classes],
[This is a shortcut for --enable-std-pointers
--enable-std-unique-ptr --enable-std-function
--enable-std-tuple.
If enabled, this supersedes any --disable
option passed for the above.]),
[ql_use_std_classes=$enableval],
[ql_use_std_classes=no])
if test "$ql_use_std_classes" = "yes" ; then
AC_DEFINE([QL_USE_STD_SHARED_PTR],[1],
[Define this if you want to use standard smart pointers.])
AC_DEFINE([QL_USE_STD_UNIQUE_PTR],[1],
[Define this if you want to replace std::auto_ptr with
std::unique_ptr.])
AC_DEFINE([QL_USE_STD_FUNCTION],[1],
[Define this if you want to use std::function and std::bind.])
AC_DEFINE([QL_USE_STD_TUPLE],[1],
[Define this if you want to use std::tuple.])
fi
AC_MSG_RESULT([$ql_use_std_classes])
AC_MSG_CHECKING([whether to enable the Disposable class template])
AC_ARG_ENABLE([disposable],
AS_HELP_STRING([--enable-disposable],
[If enabled, the Disposable class
template will be used;
this should be no longer necessary in C++11
and might interfere with compiler optimizations.
If disabled (the default) the class will only
be an alias for the underlying type.]),
[ql_use_disposable=$enableval],
[ql_use_disposable=no])
if test "$ql_use_disposable" = "yes" ; then
AC_DEFINE([QL_USE_DISPOSABLE],[1],
[Define this if you want to use the Disposable class template.])
fi
AC_MSG_RESULT([$ql_use_disposable])
# manual configurations for specific hosts
case $host in
powerpc-apple-darwin*)
AC_DEFINE([QL_PATCH_DARWIN],[1],
[Define if running on a Mac OS X machine.])
;;
sparc-sun-solaris*)
AC_DEFINE([QL_PATCH_SOLARIS],[1],
[Define if running on a Sun Solaris machine.])
;;
esac
# done, output the configured files
AC_CONFIG_FILES([
Makefile
ql/Makefile
ql/cashflows/Makefile
ql/currencies/Makefile
ql/experimental/Makefile
ql/experimental/amortizingbonds/Makefile
ql/experimental/asian/Makefile
ql/experimental/averageois/Makefile
ql/experimental/barrieroption/Makefile
ql/experimental/basismodels/Makefile
ql/experimental/callablebonds/Makefile
ql/experimental/catbonds/Makefile
ql/experimental/commodities/Makefile
ql/experimental/coupons/Makefile
ql/experimental/credit/Makefile
ql/experimental/exoticoptions/Makefile
ql/experimental/finitedifferences/Makefile
ql/experimental/forward/Makefile
ql/experimental/fx/Makefile
ql/experimental/inflation/Makefile
ql/experimental/lattices/Makefile
ql/experimental/math/Makefile
ql/experimental/mcbasket/Makefile
ql/experimental/models/Makefile
ql/experimental/processes/Makefile
ql/experimental/risk/Makefile
ql/experimental/shortrate/Makefile
ql/experimental/swaptions/Makefile
ql/experimental/termstructures/Makefile
ql/experimental/variancegamma/Makefile
ql/experimental/varianceoption/Makefile
ql/experimental/volatility/Makefile
ql/indexes/Makefile
ql/indexes/ibor/Makefile
ql/indexes/inflation/Makefile
ql/indexes/swap/Makefile
ql/instruments/Makefile
ql/instruments/bonds/Makefile
ql/legacy/Makefile
ql/legacy/libormarketmodels/Makefile
ql/math/Makefile
ql/math/copulas/Makefile
ql/math/distributions/Makefile
ql/math/integrals/Makefile
ql/math/interpolations/Makefile
ql/math/matrixutilities/Makefile
ql/math/ode/Makefile
ql/math/optimization/Makefile
ql/math/randomnumbers/Makefile
ql/math/solvers1d/Makefile
ql/math/statistics/Makefile
ql/methods/Makefile
ql/methods/finitedifferences/Makefile
ql/methods/finitedifferences/meshers/Makefile
ql/methods/finitedifferences/operators/Makefile
ql/methods/finitedifferences/schemes/Makefile
ql/methods/finitedifferences/solvers/Makefile
ql/methods/finitedifferences/stepconditions/Makefile
ql/methods/finitedifferences/utilities/Makefile
ql/methods/lattices/Makefile
ql/methods/montecarlo/Makefile
ql/models/Makefile
ql/models/equity/Makefile
ql/models/marketmodels/Makefile
ql/models/marketmodels/browniangenerators/Makefile
ql/models/marketmodels/callability/Makefile
ql/models/marketmodels/correlations/Makefile
ql/models/marketmodels/curvestates/Makefile
ql/models/marketmodels/driftcomputation/Makefile
ql/models/marketmodels/evolvers/Makefile
ql/models/marketmodels/evolvers/volprocesses/Makefile
ql/models/marketmodels/models/Makefile
ql/models/marketmodels/pathwisegreeks/Makefile
ql/models/marketmodels/products/Makefile
ql/models/marketmodels/products/onestep/Makefile
ql/models/marketmodels/products/multistep/Makefile
ql/models/marketmodels/products/pathwise/Makefile
ql/models/shortrate/Makefile
ql/models/shortrate/calibrationhelpers/Makefile
ql/models/shortrate/onefactormodels/Makefile
ql/models/shortrate/twofactormodels/Makefile
ql/models/volatility/Makefile
ql/patterns/Makefile
ql/pricingengines/Makefile
ql/pricingengines/asian/Makefile
ql/pricingengines/barrier/Makefile
ql/pricingengines/basket/Makefile
ql/pricingengines/bond/Makefile
ql/pricingengines/capfloor/Makefile
ql/pricingengines/cliquet/Makefile
ql/pricingengines/credit/Makefile
ql/pricingengines/forward/Makefile
ql/pricingengines/inflation/Makefile
ql/pricingengines/lookback/Makefile
ql/pricingengines/quanto/Makefile
ql/pricingengines/swap/Makefile
ql/pricingengines/swaption/Makefile
ql/pricingengines/vanilla/Makefile
ql/processes/Makefile
ql/quotes/Makefile
ql/termstructures/Makefile
ql/termstructures/credit/Makefile
ql/termstructures/inflation/Makefile
ql/termstructures/volatility/Makefile
ql/termstructures/volatility/equityfx/Makefile
ql/termstructures/volatility/capfloor/Makefile
ql/termstructures/volatility/inflation/Makefile
ql/termstructures/volatility/optionlet/Makefile
ql/termstructures/volatility/swaption/Makefile
ql/termstructures/yield/Makefile
ql/time/Makefile
ql/time/calendars/Makefile
ql/time/daycounters/Makefile
ql/utilities/Makefile
man/Makefile
m4/Makefile
Docs/Makefile
Examples/Makefile
test-suite/Makefile])
AC_CONFIG_FILES([quantlib-config],[chmod +x quantlib-config])
AC_CONFIG_FILES([QuantLib.spec])
AC_CONFIG_FILES([quantlib.pc])
AC_OUTPUT
On Tue, 3 May 2022 at 16:43, Conrad Cole <con...@gm...> wrote:
>
> ./configure --with-boost-include=usr/include/boost
> --with-boost-lib=/usr/lib/x86_64-linux-gnu
>
> The config.log file should be in whatever directory you ran the
> configure script.
>
> On 5/3/22 06:55, Daniel Lobo wrote:
> > Also, given that my boost location is /usr/include/boost, how can I
> > execute ./configure again with the boost lib and include flags using
> > the proper directories? What will be the right code?
> >
> > Thanks,
> >
> > On Tue, 3 May 2022 at 15:54, Daniel Lobo <dan...@gm...> wrote:
> >> Many thanks for your responses.
> >>
> >> whereis boost returns below location,
> >>
> >> $ whereis boost
> >> boost: /usr/include/boost
> >>
> >> Where can I see the generated config.log file?
> >>
> >> Thanks for your time.
> >>
> >>
> >> On Tue, 3 May 2022 at 03:29, Conrad Cole <con...@gm...> wrote:
> >>> whereis boost is the command to find the location of the installed boost header files.
> >>>
> >>> On 5/2/22 17:08, Luigi Ballabio wrote:
> >>>
> >>> Can you look inside the generated config.log file and see what compiler error you're getting exactly?
> >>>
> >>> Luigi
> >>>
> >>>
> >>> On Mon, May 2, 2022 at 7:49 PM Daniel Lobo <dan...@gm...> wrote:
> >>>> Many thanks.
> >>>>
> >>>> I ran below codes to remove and reinstall boost
> >>>>
> >>>> sudo apt-get remove libboost-all-dev
> >>>> sudo apt-get install libboost-all-dev
> >>>>
> >>>> boost installed in /usr/include
> >>>>
> >>>> :/usr/include$ ls
> >>>> aio.h complex.h error.h features-time64.h getopt.h
> >>>> langinfo.h math.h netdb.h numa.h
> >>>> python3.10 setjmp.h string.h time.h video
> >>>> aliases.h cpio.h evdns.h fenv.h glob.h
> >>>> lastlog.h mcheck.h neteconet numaif.h rdma
> >>>> sgtty.h strings.h tirpc wait.h
> >>>> alloca.h crypt.h event2 finclude
> >>>> gnu-versions.h libgen.h memory.h netinet obstack.h
> >>>> re_comp.h shadow.h sudo_plugin.h ttyent.h wchar.h
> >>>> argp.h ctype.h event.h fmtmsg.h grp.h
> >>>> libintl.h misc netipx openvpn regex.h
> >>>> signal.h syscall.h uchar.h wctype.h
> >>>> argz.h dirent.h evhttp.h fnmatch.h gshadow.h
> >>>> libltdl mntent.h netiucv paths.h regexp.h
> >>>> sound sysexits.h ucontext.h wordexp.h
> >>>> ar.h dlfcn.h evrpc.h fstab.h hwloc
> >>>> libnl3 monetary.h netpacket poll.h resolv.h
> >>>> spawn.h syslog.h ulimit.h X11
> >>>> arpa drm evutil.h fts.h hwloc.h
> >>>> limits.h mqueue.h netrom printf.h rpc
> >>>> stab.h tar.h unicode x86_64-linux-gnu
> >>>> asm-generic elf.h execinfo.h ftw.h iconv.h
> >>>> link.h mtd netrose proc_service.h rpcsvc
> >>>> stdc-predef.h termio.h unistd.h xen
> >>>> assert.h endian.h expat_external.h gcalc-2 ifaddrs.h
> >>>> linux net nfs protocols sched.h
> >>>> stdint.h termios.h utime.h xorg
> >>>> boost
> >>>>
> >>>> But still get error when I run ./configure
> >>>>
> >>>> Below is the log that I get
> >>>>
> >>>> $ ./configure
> >>>> checking for a BSD-compatible install... /usr/bin/install -c
> >>>> checking whether build environment is sane... yes
> >>>> checking for a race-free mkdir -p... /usr/bin/mkdir -p
> >>>> checking for gawk... no
> >>>> checking for mawk... mawk
> >>>> checking whether make sets $(MAKE)... no
> >>>> checking whether make supports nested variables... no
> >>>> checking whether UID '1000' is supported by ustar format... yes
> >>>> checking whether GID '1000' is supported by ustar format... yes
> >>>> checking how to create a ustar tar archive... gnutar
> >>>> checking for gawk... (cached) mawk
> >>>> checking for gcc... gcc
> >>>> checking whether the C compiler works... yes
> >>>> checking for C compiler default output file name... a.out
> >>>> checking for suffix of executables...
> >>>> checking whether we are cross compiling... no
> >>>> checking for suffix of object files... o
> >>>> checking whether the compiler supports GNU C... yes
> >>>> checking whether gcc accepts -g... yes
> >>>> checking for gcc option to enable C11 features... none needed
> >>>> checking whether gcc understands -c and -o together... yes
> >>>> checking whether make supports the include directive... no
> >>>> checking dependency style of gcc... none
> >>>> checking for g++... no
> >>>> checking for c++... no
> >>>> checking for gpp... no
> >>>> checking for aCC... no
> >>>> checking for CC... no
> >>>> checking for cxx... no
> >>>> checking for cc++... no
> >>>> checking for cl.exe... no
> >>>> checking for FCC... no
> >>>> checking for KCC... no
> >>>> checking for RCC... no
> >>>> checking for xlC_r... no
> >>>> checking for xlC... no
> >>>> checking for clang++... no
> >>>> checking whether the compiler supports GNU C++... no
> >>>> checking whether g++ accepts -g... no
> >>>> checking for g++ option to enable C++11 features... none needed
> >>>> checking dependency style of g++... none
> >>>> checking how to run the C preprocessor... gcc -E
> >>>> checking build system type... x86_64-pc-linux-gnu
> >>>> checking host system type... x86_64-pc-linux-gnu
> >>>> checking how to print strings... printf
> >>>> checking for a sed that does not truncate output... /usr/bin/sed
> >>>> checking for grep that handles long lines and -e... /usr/bin/grep
> >>>> checking for egrep... /usr/bin/grep -E
> >>>> checking for fgrep... /usr/bin/grep -F
> >>>> checking for ld used by gcc... /usr/bin/ld
> >>>> checking if the linker (/usr/bin/ld) is GNU ld... yes
> >>>> checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
> >>>> checking the name lister (/usr/bin/nm -B) interface... BSD nm
> >>>> checking whether ln -s works... yes
> >>>> checking the maximum length of command line arguments... 1572864
> >>>> checking how to convert x86_64-pc-linux-gnu file names to
> >>>> x86_64-pc-linux-gnu format... func_convert_file_noop
> >>>> checking how to convert x86_64-pc-linux-gnu file names to toolchain
> >>>> format... func_convert_file_noop
> >>>> checking for /usr/bin/ld option to reload object files... -r
> >>>> checking for objdump... objdump
> >>>> checking how to recognize dependent libraries... pass_all
> >>>> checking for dlltool... no
> >>>> checking how to associate runtime and link libraries... printf %s\n
> >>>> checking for ar... ar
> >>>> checking for archiver @FILE support... @
> >>>> checking for strip... strip
> >>>> checking for ranlib... ranlib
> >>>> checking command to parse /usr/bin/nm -B output from gcc object... ok
> >>>> checking for sysroot... no
> >>>> checking for a working dd... /usr/bin/dd
> >>>> checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1
> >>>> checking for mt... mt
> >>>> checking if mt is a manifest tool... no
> >>>> checking for stdio.h... yes
> >>>> checking for stdlib.h... yes
> >>>> checking for string.h... yes
> >>>> checking for inttypes.h... yes
> >>>> checking for stdint.h... yes
> >>>> checking for strings.h... yes
> >>>> checking for sys/stat.h... yes
> >>>> checking for sys/types.h... yes
> >>>> checking for unistd.h... yes
> >>>> checking for dlfcn.h... yes
> >>>> checking for objdir... .libs
> >>>> checking if gcc supports -fno-rtti -fno-exceptions... no
> >>>> checking for gcc option to produce PIC... -fPIC -DPIC
> >>>> checking if gcc PIC flag -fPIC -DPIC works... yes
> >>>> checking if gcc static flag -static works... yes
> >>>> checking if gcc supports -c -o file.o... yes
> >>>> checking if gcc supports -c -o file.o... (cached) yes
> >>>> checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports
> >>>> shared libraries... yes
> >>>> checking whether -lc should be explicitly linked in... no
> >>>> checking dynamic linker characteristics... GNU/Linux ld.so
> >>>> checking how to hardcode library paths into programs... immediate
> >>>> checking whether stripping libraries is possible... yes
> >>>> checking if libtool supports shared libraries... yes
> >>>> checking whether to build shared libraries... yes
> >>>> checking whether to build static libraries... yes
> >>>> checking for C++11 support... no: adding -std=c++11 to CXXFLAGS
> >>>> checking for Boost development files... no
> >>>> configure: error: Boost development files not found
> >>>>
> >>>>
> >>>> Any pointer how to resolve this will be very helpful.
> >>>>
> >>>> Thanks
> >>>>
> >>>> On Sun, 1 May 2022 at 13:16, Jonathan Sweemer <sw...@gm...> wrote:
> >>>>> Hi Daniel,
> >>>>>
> >>>>> Just to confirm, you’re no longer running ./configure with the —with-boost-include and —with-boost-lib flags right?
> >>>>>
> >>>>> If so then I would expect the configure script to find your boost installation. Please check that you see boost headers in /usr/include/boost and if not, try reinstalling boost.
> >>>>>
> >>>>> If you’re still unable to get ./configure to find boost then please attach the full output including all the commands that you ran.
> >>>>>
> >>>>> Jonathan
> >>>>>
> >>>>>
> >>>>> 2022년 5월 1일 (일) 15:41, Daniel Lobo <dan...@gm...>님이 작성:
> >>>>>> Hi,
> >>>>>>
> >>>>>> Many thanks for your response.
> >>>>>>
> >>>>>> Yes I ran 'sudo apt-get install libboost-all-dev' to install boost.
> >>>>>> However still I get this error.
> >>>>>>
> >>>>>> How can I find where the boost is installed and how can I pass that
> >>>>>> information './configure ' line?
> >>>>>>
> >>>>>> Apologies for trivial question if any, as I am not very expert in
> >>>>>> Linux ecosystem.
> >>>>>>
> >>>>>> Thanks and regards,
> >>>>>>
> >>>>>> On Sun, 1 May 2022 at 11:53, Jonathan Sweemer <sw...@gm...> wrote:
> >>>>>>> Hi Daniel,
> >>>>>>>
> >>>>>>> When you say that you “install[ed] boost already as provided in the instruction page” do you mean that you ran the following command?
> >>>>>>>
> >>>>>>> sudo apt-get install libboost-all-dev
> >>>>>>>
> >>>>>>> If so then you shouldn’t need to use the —with-boost-include and —with-boost-lib flags when configuring QuantLib. As the install guide mentions, you only need those flags when you install boost in a non-standard location.
> >>>>>>>
> >>>>>>> Jonathan
> >>>>>>>
> >>>>>>>
> >>>>>>> 2022년 5월 1일 (일) 02:25, Daniel Lobo <dan...@gm...>님이 작성:
> >>>>>>>> Hi,
> >>>>>>>>
> >>>>>>>> I am trying to install Quantlib in my Ubuntu VM. I was following the
> >>>>>>>> instructions as provided in
> >>>>>>>> https://www.quantlib.org/install/linux.shtml
> >>>>>>>>
> >>>>>>>> But this installation failed when I executed
> >>>>>>>>
> >>>>>>>> ./configure --with-boost-include=/home/foo/include
> >>>>>>>> --with-boost-lib=/home/foo/lib
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> The error I got is
> >>>>>>>>
> >>>>>>>> $ ./configure --with-boost-include=/home/foo/include
> >>>>>>>> --with-boost-lib=/home/foo/lib
> >>>>>>>> checking for a BSD-compatible install... /usr/bin/install -c
> >>>>>>>> checking whether build environment is sane... yes
> >>>>>>>> checking for a race-free mkdir -p... /usr/bin/mkdir -p
> >>>>>>>> checking for gawk... no
> >>>>>>>> checking for mawk... mawk
> >>>>>>>> checking whether make sets $(MAKE)... no
> >>>>>>>> checking whether make supports nested variables... no
> >>>>>>>> checking whether UID '1000' is supported by ustar format... yes
> >>>>>>>> checking whether GID '1000' is supported by ustar format... yes
> >>>>>>>> checking how to create a ustar tar archive... gnutar
> >>>>>>>> checking for gawk... (cached) mawk
> >>>>>>>> checking for gcc... gcc
> >>>>>>>> checking whether the C compiler works... yes
> >>>>>>>> checking for C compiler default output file name... a.out
> >>>>>>>> checking for suffix of executables...
> >>>>>>>> checking whether we are cross compiling... no
> >>>>>>>> checking for suffix of object files... o
> >>>>>>>> checking whether the compiler supports GNU C... yes
> >>>>>>>> checking whether gcc accepts -g... yes
> >>>>>>>> checking for gcc option to enable C11 features... none needed
> >>>>>>>> checking whether gcc understands -c and -o together... yes
> >>>>>>>> checking whether make supports the include directive... no
> >>>>>>>> checking dependency style of gcc... none
> >>>>>>>> checking for g++... no
> >>>>>>>> checking for c++... no
> >>>>>>>> checking for gpp... no
> >>>>>>>> checking for aCC... no
> >>>>>>>> checking for CC... no
> >>>>>>>> checking for cxx... no
> >>>>>>>> checking for cc++... no
> >>>>>>>> checking for cl.exe... no
> >>>>>>>> checking for FCC... no
> >>>>>>>> checking for KCC... no
> >>>>>>>> checking for RCC... no
> >>>>>>>> checking for xlC_r... no
> >>>>>>>> checking for xlC... no
> >>>>>>>> checking for clang++... no
> >>>>>>>> checking whether the compiler supports GNU C++... no
> >>>>>>>> checking whether g++ accepts -g... no
> >>>>>>>> checking for g++ option to enable C++11 features... none needed
> >>>>>>>> checking dependency style of g++... none
> >>>>>>>> checking how to run the C preprocessor... gcc -E
> >>>>>>>> checking build system type... x86_64-pc-linux-gnu
> >>>>>>>> checking host system type... x86_64-pc-linux-gnu
> >>>>>>>> checking how to print strings... printf
> >>>>>>>> checking for a sed that does not truncate output... /usr/bin/sed
> >>>>>>>> checking for grep that handles long lines and -e... /usr/bin/grep
> >>>>>>>> checking for egrep... /usr/bin/grep -E
> >>>>>>>> checking for fgrep... /usr/bin/grep -F
> >>>>>>>> checking for ld used by gcc... /usr/bin/ld
> >>>>>>>> checking if the linker (/usr/bin/ld) is GNU ld... yes
> >>>>>>>> checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
> >>>>>>>> checking the name lister (/usr/bin/nm -B) interface... BSD nm
> >>>>>>>> checking whether ln -s works... yes
> >>>>>>>> checking the maximum length of command line arguments... 1572864
> >>>>>>>> checking how to convert x86_64-pc-linux-gnu file names to
> >>>>>>>> x86_64-pc-linux-gnu format... func_convert_file_noop
> >>>>>>>> checking how to convert x86_64-pc-linux-gnu file names to toolchain
> >>>>>>>> format... func_convert_file_noop
> >>>>>>>> checking for /usr/bin/ld option to reload object files... -r
> >>>>>>>> checking for objdump... objdump
> >>>>>>>> checking how to recognize dependent libraries... pass_all
> >>>>>>>> checking for dlltool... no
> >>>>>>>> checking how to associate runtime and link libraries... printf %s\n
> >>>>>>>> checking for ar... ar
> >>>>>>>> checking for archiver @FILE support... @
> >>>>>>>> checking for strip... strip
> >>>>>>>> checking for ranlib... ranlib
> >>>>>>>> checking command to parse /usr/bin/nm -B output from gcc object... ok
> >>>>>>>> checking for sysroot... no
> >>>>>>>> checking for a working dd... /usr/bin/dd
> >>>>>>>> checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1
> >>>>>>>> checking for mt... mt
> >>>>>>>> checking if mt is a manifest tool... no
> >>>>>>>> checking for stdio.h... yes
> >>>>>>>> checking for stdlib.h... yes
> >>>>>>>> checking for string.h... yes
> >>>>>>>> checking for inttypes.h... yes
> >>>>>>>> checking for stdint.h... yes
> >>>>>>>> checking for strings.h... yes
> >>>>>>>> checking for sys/stat.h... yes
> >>>>>>>> checking for sys/types.h... yes
> >>>>>>>> checking for unistd.h... yes
> >>>>>>>> checking for dlfcn.h... yes
> >>>>>>>> checking for objdir... .libs
> >>>>>>>> checking if gcc supports -fno-rtti -fno-exceptions... no
> >>>>>>>> checking for gcc option to produce PIC... -fPIC -DPIC
> >>>>>>>> checking if gcc PIC flag -fPIC -DPIC works... yes
> >>>>>>>> checking if gcc static flag -static works... yes
> >>>>>>>> checking if gcc supports -c -o file.o... yes
> >>>>>>>> checking if gcc supports -c -o file.o... (cached) yes
> >>>>>>>> checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports
> >>>>>>>> shared libraries... yes
> >>>>>>>> checking whether -lc should be explicitly linked in... no
> >>>>>>>> checking dynamic linker characteristics... GNU/Linux ld.so
> >>>>>>>> checking how to hardcode library paths into programs... immediate
> >>>>>>>> checking whether stripping libraries is possible... yes
> >>>>>>>> checking if libtool supports shared libraries... yes
> >>>>>>>> checking whether to build shared libraries... yes
> >>>>>>>> checking whether to build static libraries... yes
> >>>>>>>> checking for C++11 support... no: adding -std=c++11 to CXXFLAGS
> >>>>>>>> checking for Boost development files... no
> >>>>>>>> configure: error: Boost development files not found
> >>>>>>>>
> >>>>>>>> Could you please help how to resolve this error. I executed the code
> >>>>>>>> to install boost already as provided in the instruction page.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> _______________________________________________
> >>>>>>>> QuantLib-users mailing list
> >>>>>>>> Qua...@li...
> >>>>>>>> https://lists.sourceforge.net/lists/listinfo/quantlib-users
> >>>>
> >>>> _______________________________________________
> >>>> QuantLib-users mailing list
> >>>> Qua...@li...
> >>>> https://lists.sourceforge.net/lists/listinfo/quantlib-users
> >>>
> >>>
> >>> _______________________________________________
> >>> QuantLib-users mailing list
> >>> Qua...@li...
> >>> https://lists.sourceforge.net/lists/listinfo/quantlib-users
|
|
From: Jonathan S. <sw...@gm...> - 2022-05-03 12:50:07
|
The error message is correct - QuantLib cannot be built as a shared library (DLL) on Windows with vcpkg. Use the following command to install QuantLib as a static library on Windows instead. .\vcpkg install quantlib:x64-windows-static On Tue, May 3, 2022 at 11:58 AM Chirag Desai <chi...@ya...> wrote: > Thank you Jonathan for your kind advice. > > I tried using VC PKG to install quantlib but I believe you cannot install > it on Windows. I got the error message below. > > Error: quantlib[core] is only supported on '!(windows & !static)' > > On the website Compatibility, it indicates Windows supported. Can you > confirm Windows is not supported and if you know when it might be possible ? > Browse public vcpkg packages <https://vcpkg.io/en/packages.html> > > Browse public vcpkg packages > > Explore vcpkg libraries to install > <https://vcpkg.io/en/packages.html> > > > > > [image: Inline image] > > Thank you for your guidance > > > On Monday, May 2, 2022, 08:33:37 PM GMT+8, Jonathan Sweemer < > sw...@gm...> wrote: > > > Hi Chirag, > > Did you follow the instructions in the CMake output and 'Add the > installation prefix of "QuantLib" to CMAKE_PREFIX_PATH or set > "QuantLib_DIR" to a directory containing one of the above files'? > > If C:/local/QuantLib-1.24/cmake-build-debug-visualstudio2017 is your CMake > build directory, then the 'above files' will be found in the cmake > directory under that build directory. > > If that doesn't work then the best I can do is point you to the > documentation on CMake config mode[1] and wish you luck, as I won't be able > to offer much further help remotely. > > By the way, the quantlib-vcpkg-example repo that you found is an example > of how to link your project to QuantLib installed through vcpkg, which you > haven't used. If you'd like to, you can try out vcpkg, and it may make your > life easier in the long run, but be aware that it has a learning curve of > its own to grapple with first. > > [1] > https://cmake.org/cmake/help/latest/command/find_package.html#config-mode-search-procedure > > > |
|
From: Conrad C. <con...@gm...> - 2022-05-03 11:13:24
|
./configure --with-boost-include=usr/include/boost --with-boost-lib=/usr/lib/x86_64-linux-gnu The config.log file should be in whatever directory you ran the configure script. On 5/3/22 06:55, Daniel Lobo wrote: > Also, given that my boost location is /usr/include/boost, how can I > execute ./configure again with the boost lib and include flags using > the proper directories? What will be the right code? > > Thanks, > > On Tue, 3 May 2022 at 15:54, Daniel Lobo <dan...@gm...> wrote: >> Many thanks for your responses. >> >> whereis boost returns below location, >> >> $ whereis boost >> boost: /usr/include/boost >> >> Where can I see the generated config.log file? >> >> Thanks for your time. >> >> >> On Tue, 3 May 2022 at 03:29, Conrad Cole <con...@gm...> wrote: >>> whereis boost is the command to find the location of the installed boost header files. >>> >>> On 5/2/22 17:08, Luigi Ballabio wrote: >>> >>> Can you look inside the generated config.log file and see what compiler error you're getting exactly? >>> >>> Luigi >>> >>> >>> On Mon, May 2, 2022 at 7:49 PM Daniel Lobo <dan...@gm...> wrote: >>>> Many thanks. >>>> >>>> I ran below codes to remove and reinstall boost >>>> >>>> sudo apt-get remove libboost-all-dev >>>> sudo apt-get install libboost-all-dev >>>> >>>> boost installed in /usr/include >>>> >>>> :/usr/include$ ls >>>> aio.h complex.h error.h features-time64.h getopt.h >>>> langinfo.h math.h netdb.h numa.h >>>> python3.10 setjmp.h string.h time.h video >>>> aliases.h cpio.h evdns.h fenv.h glob.h >>>> lastlog.h mcheck.h neteconet numaif.h rdma >>>> sgtty.h strings.h tirpc wait.h >>>> alloca.h crypt.h event2 finclude >>>> gnu-versions.h libgen.h memory.h netinet obstack.h >>>> re_comp.h shadow.h sudo_plugin.h ttyent.h wchar.h >>>> argp.h ctype.h event.h fmtmsg.h grp.h >>>> libintl.h misc netipx openvpn regex.h >>>> signal.h syscall.h uchar.h wctype.h >>>> argz.h dirent.h evhttp.h fnmatch.h gshadow.h >>>> libltdl mntent.h netiucv paths.h regexp.h >>>> sound sysexits.h ucontext.h wordexp.h >>>> ar.h dlfcn.h evrpc.h fstab.h hwloc >>>> libnl3 monetary.h netpacket poll.h resolv.h >>>> spawn.h syslog.h ulimit.h X11 >>>> arpa drm evutil.h fts.h hwloc.h >>>> limits.h mqueue.h netrom printf.h rpc >>>> stab.h tar.h unicode x86_64-linux-gnu >>>> asm-generic elf.h execinfo.h ftw.h iconv.h >>>> link.h mtd netrose proc_service.h rpcsvc >>>> stdc-predef.h termio.h unistd.h xen >>>> assert.h endian.h expat_external.h gcalc-2 ifaddrs.h >>>> linux net nfs protocols sched.h >>>> stdint.h termios.h utime.h xorg >>>> boost >>>> >>>> But still get error when I run ./configure >>>> >>>> Below is the log that I get >>>> >>>> $ ./configure >>>> checking for a BSD-compatible install... /usr/bin/install -c >>>> checking whether build environment is sane... yes >>>> checking for a race-free mkdir -p... /usr/bin/mkdir -p >>>> checking for gawk... no >>>> checking for mawk... mawk >>>> checking whether make sets $(MAKE)... no >>>> checking whether make supports nested variables... no >>>> checking whether UID '1000' is supported by ustar format... yes >>>> checking whether GID '1000' is supported by ustar format... yes >>>> checking how to create a ustar tar archive... gnutar >>>> checking for gawk... (cached) mawk >>>> checking for gcc... gcc >>>> checking whether the C compiler works... yes >>>> checking for C compiler default output file name... a.out >>>> checking for suffix of executables... >>>> checking whether we are cross compiling... no >>>> checking for suffix of object files... o >>>> checking whether the compiler supports GNU C... yes >>>> checking whether gcc accepts -g... yes >>>> checking for gcc option to enable C11 features... none needed >>>> checking whether gcc understands -c and -o together... yes >>>> checking whether make supports the include directive... no >>>> checking dependency style of gcc... none >>>> checking for g++... no >>>> checking for c++... no >>>> checking for gpp... no >>>> checking for aCC... no >>>> checking for CC... no >>>> checking for cxx... no >>>> checking for cc++... no >>>> checking for cl.exe... no >>>> checking for FCC... no >>>> checking for KCC... no >>>> checking for RCC... no >>>> checking for xlC_r... no >>>> checking for xlC... no >>>> checking for clang++... no >>>> checking whether the compiler supports GNU C++... no >>>> checking whether g++ accepts -g... no >>>> checking for g++ option to enable C++11 features... none needed >>>> checking dependency style of g++... none >>>> checking how to run the C preprocessor... gcc -E >>>> checking build system type... x86_64-pc-linux-gnu >>>> checking host system type... x86_64-pc-linux-gnu >>>> checking how to print strings... printf >>>> checking for a sed that does not truncate output... /usr/bin/sed >>>> checking for grep that handles long lines and -e... /usr/bin/grep >>>> checking for egrep... /usr/bin/grep -E >>>> checking for fgrep... /usr/bin/grep -F >>>> checking for ld used by gcc... /usr/bin/ld >>>> checking if the linker (/usr/bin/ld) is GNU ld... yes >>>> checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B >>>> checking the name lister (/usr/bin/nm -B) interface... BSD nm >>>> checking whether ln -s works... yes >>>> checking the maximum length of command line arguments... 1572864 >>>> checking how to convert x86_64-pc-linux-gnu file names to >>>> x86_64-pc-linux-gnu format... func_convert_file_noop >>>> checking how to convert x86_64-pc-linux-gnu file names to toolchain >>>> format... func_convert_file_noop >>>> checking for /usr/bin/ld option to reload object files... -r >>>> checking for objdump... objdump >>>> checking how to recognize dependent libraries... pass_all >>>> checking for dlltool... no >>>> checking how to associate runtime and link libraries... printf %s\n >>>> checking for ar... ar >>>> checking for archiver @FILE support... @ >>>> checking for strip... strip >>>> checking for ranlib... ranlib >>>> checking command to parse /usr/bin/nm -B output from gcc object... ok >>>> checking for sysroot... no >>>> checking for a working dd... /usr/bin/dd >>>> checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1 >>>> checking for mt... mt >>>> checking if mt is a manifest tool... no >>>> checking for stdio.h... yes >>>> checking for stdlib.h... yes >>>> checking for string.h... yes >>>> checking for inttypes.h... yes >>>> checking for stdint.h... yes >>>> checking for strings.h... yes >>>> checking for sys/stat.h... yes >>>> checking for sys/types.h... yes >>>> checking for unistd.h... yes >>>> checking for dlfcn.h... yes >>>> checking for objdir... .libs >>>> checking if gcc supports -fno-rtti -fno-exceptions... no >>>> checking for gcc option to produce PIC... -fPIC -DPIC >>>> checking if gcc PIC flag -fPIC -DPIC works... yes >>>> checking if gcc static flag -static works... yes >>>> checking if gcc supports -c -o file.o... yes >>>> checking if gcc supports -c -o file.o... (cached) yes >>>> checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports >>>> shared libraries... yes >>>> checking whether -lc should be explicitly linked in... no >>>> checking dynamic linker characteristics... GNU/Linux ld.so >>>> checking how to hardcode library paths into programs... immediate >>>> checking whether stripping libraries is possible... yes >>>> checking if libtool supports shared libraries... yes >>>> checking whether to build shared libraries... yes >>>> checking whether to build static libraries... yes >>>> checking for C++11 support... no: adding -std=c++11 to CXXFLAGS >>>> checking for Boost development files... no >>>> configure: error: Boost development files not found >>>> >>>> >>>> Any pointer how to resolve this will be very helpful. >>>> >>>> Thanks >>>> >>>> On Sun, 1 May 2022 at 13:16, Jonathan Sweemer <sw...@gm...> wrote: >>>>> Hi Daniel, >>>>> >>>>> Just to confirm, you’re no longer running ./configure with the —with-boost-include and —with-boost-lib flags right? >>>>> >>>>> If so then I would expect the configure script to find your boost installation. Please check that you see boost headers in /usr/include/boost and if not, try reinstalling boost. >>>>> >>>>> If you’re still unable to get ./configure to find boost then please attach the full output including all the commands that you ran. >>>>> >>>>> Jonathan >>>>> >>>>> >>>>> 2022년 5월 1일 (일) 15:41, Daniel Lobo <dan...@gm...>님이 작성: >>>>>> Hi, >>>>>> >>>>>> Many thanks for your response. >>>>>> >>>>>> Yes I ran 'sudo apt-get install libboost-all-dev' to install boost. >>>>>> However still I get this error. >>>>>> >>>>>> How can I find where the boost is installed and how can I pass that >>>>>> information './configure ' line? >>>>>> >>>>>> Apologies for trivial question if any, as I am not very expert in >>>>>> Linux ecosystem. >>>>>> >>>>>> Thanks and regards, >>>>>> >>>>>> On Sun, 1 May 2022 at 11:53, Jonathan Sweemer <sw...@gm...> wrote: >>>>>>> Hi Daniel, >>>>>>> >>>>>>> When you say that you “install[ed] boost already as provided in the instruction page” do you mean that you ran the following command? >>>>>>> >>>>>>> sudo apt-get install libboost-all-dev >>>>>>> >>>>>>> If so then you shouldn’t need to use the —with-boost-include and —with-boost-lib flags when configuring QuantLib. As the install guide mentions, you only need those flags when you install boost in a non-standard location. >>>>>>> >>>>>>> Jonathan >>>>>>> >>>>>>> >>>>>>> 2022년 5월 1일 (일) 02:25, Daniel Lobo <dan...@gm...>님이 작성: >>>>>>>> Hi, >>>>>>>> >>>>>>>> I am trying to install Quantlib in my Ubuntu VM. I was following the >>>>>>>> instructions as provided in >>>>>>>> https://www.quantlib.org/install/linux.shtml >>>>>>>> >>>>>>>> But this installation failed when I executed >>>>>>>> >>>>>>>> ./configure --with-boost-include=/home/foo/include >>>>>>>> --with-boost-lib=/home/foo/lib >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> The error I got is >>>>>>>> >>>>>>>> $ ./configure --with-boost-include=/home/foo/include >>>>>>>> --with-boost-lib=/home/foo/lib >>>>>>>> checking for a BSD-compatible install... /usr/bin/install -c >>>>>>>> checking whether build environment is sane... yes >>>>>>>> checking for a race-free mkdir -p... /usr/bin/mkdir -p >>>>>>>> checking for gawk... no >>>>>>>> checking for mawk... mawk >>>>>>>> checking whether make sets $(MAKE)... no >>>>>>>> checking whether make supports nested variables... no >>>>>>>> checking whether UID '1000' is supported by ustar format... yes >>>>>>>> checking whether GID '1000' is supported by ustar format... yes >>>>>>>> checking how to create a ustar tar archive... gnutar >>>>>>>> checking for gawk... (cached) mawk >>>>>>>> checking for gcc... gcc >>>>>>>> checking whether the C compiler works... yes >>>>>>>> checking for C compiler default output file name... a.out >>>>>>>> checking for suffix of executables... >>>>>>>> checking whether we are cross compiling... no >>>>>>>> checking for suffix of object files... o >>>>>>>> checking whether the compiler supports GNU C... yes >>>>>>>> checking whether gcc accepts -g... yes >>>>>>>> checking for gcc option to enable C11 features... none needed >>>>>>>> checking whether gcc understands -c and -o together... yes >>>>>>>> checking whether make supports the include directive... no >>>>>>>> checking dependency style of gcc... none >>>>>>>> checking for g++... no >>>>>>>> checking for c++... no >>>>>>>> checking for gpp... no >>>>>>>> checking for aCC... no >>>>>>>> checking for CC... no >>>>>>>> checking for cxx... no >>>>>>>> checking for cc++... no >>>>>>>> checking for cl.exe... no >>>>>>>> checking for FCC... no >>>>>>>> checking for KCC... no >>>>>>>> checking for RCC... no >>>>>>>> checking for xlC_r... no >>>>>>>> checking for xlC... no >>>>>>>> checking for clang++... no >>>>>>>> checking whether the compiler supports GNU C++... no >>>>>>>> checking whether g++ accepts -g... no >>>>>>>> checking for g++ option to enable C++11 features... none needed >>>>>>>> checking dependency style of g++... none >>>>>>>> checking how to run the C preprocessor... gcc -E >>>>>>>> checking build system type... x86_64-pc-linux-gnu >>>>>>>> checking host system type... x86_64-pc-linux-gnu >>>>>>>> checking how to print strings... printf >>>>>>>> checking for a sed that does not truncate output... /usr/bin/sed >>>>>>>> checking for grep that handles long lines and -e... /usr/bin/grep >>>>>>>> checking for egrep... /usr/bin/grep -E >>>>>>>> checking for fgrep... /usr/bin/grep -F >>>>>>>> checking for ld used by gcc... /usr/bin/ld >>>>>>>> checking if the linker (/usr/bin/ld) is GNU ld... yes >>>>>>>> checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B >>>>>>>> checking the name lister (/usr/bin/nm -B) interface... BSD nm >>>>>>>> checking whether ln -s works... yes >>>>>>>> checking the maximum length of command line arguments... 1572864 >>>>>>>> checking how to convert x86_64-pc-linux-gnu file names to >>>>>>>> x86_64-pc-linux-gnu format... func_convert_file_noop >>>>>>>> checking how to convert x86_64-pc-linux-gnu file names to toolchain >>>>>>>> format... func_convert_file_noop >>>>>>>> checking for /usr/bin/ld option to reload object files... -r >>>>>>>> checking for objdump... objdump >>>>>>>> checking how to recognize dependent libraries... pass_all >>>>>>>> checking for dlltool... no >>>>>>>> checking how to associate runtime and link libraries... printf %s\n >>>>>>>> checking for ar... ar >>>>>>>> checking for archiver @FILE support... @ >>>>>>>> checking for strip... strip >>>>>>>> checking for ranlib... ranlib >>>>>>>> checking command to parse /usr/bin/nm -B output from gcc object... ok >>>>>>>> checking for sysroot... no >>>>>>>> checking for a working dd... /usr/bin/dd >>>>>>>> checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1 >>>>>>>> checking for mt... mt >>>>>>>> checking if mt is a manifest tool... no >>>>>>>> checking for stdio.h... yes >>>>>>>> checking for stdlib.h... yes >>>>>>>> checking for string.h... yes >>>>>>>> checking for inttypes.h... yes >>>>>>>> checking for stdint.h... yes >>>>>>>> checking for strings.h... yes >>>>>>>> checking for sys/stat.h... yes >>>>>>>> checking for sys/types.h... yes >>>>>>>> checking for unistd.h... yes >>>>>>>> checking for dlfcn.h... yes >>>>>>>> checking for objdir... .libs >>>>>>>> checking if gcc supports -fno-rtti -fno-exceptions... no >>>>>>>> checking for gcc option to produce PIC... -fPIC -DPIC >>>>>>>> checking if gcc PIC flag -fPIC -DPIC works... yes >>>>>>>> checking if gcc static flag -static works... yes >>>>>>>> checking if gcc supports -c -o file.o... yes >>>>>>>> checking if gcc supports -c -o file.o... (cached) yes >>>>>>>> checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports >>>>>>>> shared libraries... yes >>>>>>>> checking whether -lc should be explicitly linked in... no >>>>>>>> checking dynamic linker characteristics... GNU/Linux ld.so >>>>>>>> checking how to hardcode library paths into programs... immediate >>>>>>>> checking whether stripping libraries is possible... yes >>>>>>>> checking if libtool supports shared libraries... yes >>>>>>>> checking whether to build shared libraries... yes >>>>>>>> checking whether to build static libraries... yes >>>>>>>> checking for C++11 support... no: adding -std=c++11 to CXXFLAGS >>>>>>>> checking for Boost development files... no >>>>>>>> configure: error: Boost development files not found >>>>>>>> >>>>>>>> Could you please help how to resolve this error. I executed the code >>>>>>>> to install boost already as provided in the instruction page. >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> QuantLib-users mailing list >>>>>>>> Qua...@li... >>>>>>>> https://lists.sourceforge.net/lists/listinfo/quantlib-users >>>> >>>> _______________________________________________ >>>> QuantLib-users mailing list >>>> Qua...@li... >>>> https://lists.sourceforge.net/lists/listinfo/quantlib-users >>> >>> >>> _______________________________________________ >>> QuantLib-users mailing list >>> Qua...@li... >>> https://lists.sourceforge.net/lists/listinfo/quantlib-users |
|
From: Daniel L. <dan...@gm...> - 2022-05-03 10:56:25
|
Also, given that my boost location is /usr/include/boost, how can I execute ./configure again with the boost lib and include flags using the proper directories? What will be the right code? Thanks, On Tue, 3 May 2022 at 15:54, Daniel Lobo <dan...@gm...> wrote: > > Many thanks for your responses. > > whereis boost returns below location, > > $ whereis boost > boost: /usr/include/boost > > Where can I see the generated config.log file? > > Thanks for your time. > > > On Tue, 3 May 2022 at 03:29, Conrad Cole <con...@gm...> wrote: > > > > whereis boost is the command to find the location of the installed boost header files. > > > > On 5/2/22 17:08, Luigi Ballabio wrote: > > > > Can you look inside the generated config.log file and see what compiler error you're getting exactly? > > > > Luigi > > > > > > On Mon, May 2, 2022 at 7:49 PM Daniel Lobo <dan...@gm...> wrote: > >> > >> Many thanks. > >> > >> I ran below codes to remove and reinstall boost > >> > >> sudo apt-get remove libboost-all-dev > >> sudo apt-get install libboost-all-dev > >> > >> boost installed in /usr/include > >> > >> :/usr/include$ ls > >> aio.h complex.h error.h features-time64.h getopt.h > >> langinfo.h math.h netdb.h numa.h > >> python3.10 setjmp.h string.h time.h video > >> aliases.h cpio.h evdns.h fenv.h glob.h > >> lastlog.h mcheck.h neteconet numaif.h rdma > >> sgtty.h strings.h tirpc wait.h > >> alloca.h crypt.h event2 finclude > >> gnu-versions.h libgen.h memory.h netinet obstack.h > >> re_comp.h shadow.h sudo_plugin.h ttyent.h wchar.h > >> argp.h ctype.h event.h fmtmsg.h grp.h > >> libintl.h misc netipx openvpn regex.h > >> signal.h syscall.h uchar.h wctype.h > >> argz.h dirent.h evhttp.h fnmatch.h gshadow.h > >> libltdl mntent.h netiucv paths.h regexp.h > >> sound sysexits.h ucontext.h wordexp.h > >> ar.h dlfcn.h evrpc.h fstab.h hwloc > >> libnl3 monetary.h netpacket poll.h resolv.h > >> spawn.h syslog.h ulimit.h X11 > >> arpa drm evutil.h fts.h hwloc.h > >> limits.h mqueue.h netrom printf.h rpc > >> stab.h tar.h unicode x86_64-linux-gnu > >> asm-generic elf.h execinfo.h ftw.h iconv.h > >> link.h mtd netrose proc_service.h rpcsvc > >> stdc-predef.h termio.h unistd.h xen > >> assert.h endian.h expat_external.h gcalc-2 ifaddrs.h > >> linux net nfs protocols sched.h > >> stdint.h termios.h utime.h xorg > >> boost > >> > >> But still get error when I run ./configure > >> > >> Below is the log that I get > >> > >> $ ./configure > >> checking for a BSD-compatible install... /usr/bin/install -c > >> checking whether build environment is sane... yes > >> checking for a race-free mkdir -p... /usr/bin/mkdir -p > >> checking for gawk... no > >> checking for mawk... mawk > >> checking whether make sets $(MAKE)... no > >> checking whether make supports nested variables... no > >> checking whether UID '1000' is supported by ustar format... yes > >> checking whether GID '1000' is supported by ustar format... yes > >> checking how to create a ustar tar archive... gnutar > >> checking for gawk... (cached) mawk > >> checking for gcc... gcc > >> checking whether the C compiler works... yes > >> checking for C compiler default output file name... a.out > >> checking for suffix of executables... > >> checking whether we are cross compiling... no > >> checking for suffix of object files... o > >> checking whether the compiler supports GNU C... yes > >> checking whether gcc accepts -g... yes > >> checking for gcc option to enable C11 features... none needed > >> checking whether gcc understands -c and -o together... yes > >> checking whether make supports the include directive... no > >> checking dependency style of gcc... none > >> checking for g++... no > >> checking for c++... no > >> checking for gpp... no > >> checking for aCC... no > >> checking for CC... no > >> checking for cxx... no > >> checking for cc++... no > >> checking for cl.exe... no > >> checking for FCC... no > >> checking for KCC... no > >> checking for RCC... no > >> checking for xlC_r... no > >> checking for xlC... no > >> checking for clang++... no > >> checking whether the compiler supports GNU C++... no > >> checking whether g++ accepts -g... no > >> checking for g++ option to enable C++11 features... none needed > >> checking dependency style of g++... none > >> checking how to run the C preprocessor... gcc -E > >> checking build system type... x86_64-pc-linux-gnu > >> checking host system type... x86_64-pc-linux-gnu > >> checking how to print strings... printf > >> checking for a sed that does not truncate output... /usr/bin/sed > >> checking for grep that handles long lines and -e... /usr/bin/grep > >> checking for egrep... /usr/bin/grep -E > >> checking for fgrep... /usr/bin/grep -F > >> checking for ld used by gcc... /usr/bin/ld > >> checking if the linker (/usr/bin/ld) is GNU ld... yes > >> checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B > >> checking the name lister (/usr/bin/nm -B) interface... BSD nm > >> checking whether ln -s works... yes > >> checking the maximum length of command line arguments... 1572864 > >> checking how to convert x86_64-pc-linux-gnu file names to > >> x86_64-pc-linux-gnu format... func_convert_file_noop > >> checking how to convert x86_64-pc-linux-gnu file names to toolchain > >> format... func_convert_file_noop > >> checking for /usr/bin/ld option to reload object files... -r > >> checking for objdump... objdump > >> checking how to recognize dependent libraries... pass_all > >> checking for dlltool... no > >> checking how to associate runtime and link libraries... printf %s\n > >> checking for ar... ar > >> checking for archiver @FILE support... @ > >> checking for strip... strip > >> checking for ranlib... ranlib > >> checking command to parse /usr/bin/nm -B output from gcc object... ok > >> checking for sysroot... no > >> checking for a working dd... /usr/bin/dd > >> checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1 > >> checking for mt... mt > >> checking if mt is a manifest tool... no > >> checking for stdio.h... yes > >> checking for stdlib.h... yes > >> checking for string.h... yes > >> checking for inttypes.h... yes > >> checking for stdint.h... yes > >> checking for strings.h... yes > >> checking for sys/stat.h... yes > >> checking for sys/types.h... yes > >> checking for unistd.h... yes > >> checking for dlfcn.h... yes > >> checking for objdir... .libs > >> checking if gcc supports -fno-rtti -fno-exceptions... no > >> checking for gcc option to produce PIC... -fPIC -DPIC > >> checking if gcc PIC flag -fPIC -DPIC works... yes > >> checking if gcc static flag -static works... yes > >> checking if gcc supports -c -o file.o... yes > >> checking if gcc supports -c -o file.o... (cached) yes > >> checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports > >> shared libraries... yes > >> checking whether -lc should be explicitly linked in... no > >> checking dynamic linker characteristics... GNU/Linux ld.so > >> checking how to hardcode library paths into programs... immediate > >> checking whether stripping libraries is possible... yes > >> checking if libtool supports shared libraries... yes > >> checking whether to build shared libraries... yes > >> checking whether to build static libraries... yes > >> checking for C++11 support... no: adding -std=c++11 to CXXFLAGS > >> checking for Boost development files... no > >> configure: error: Boost development files not found > >> > >> > >> Any pointer how to resolve this will be very helpful. > >> > >> Thanks > >> > >> On Sun, 1 May 2022 at 13:16, Jonathan Sweemer <sw...@gm...> wrote: > >> > > >> > Hi Daniel, > >> > > >> > Just to confirm, you’re no longer running ./configure with the —with-boost-include and —with-boost-lib flags right? > >> > > >> > If so then I would expect the configure script to find your boost installation. Please check that you see boost headers in /usr/include/boost and if not, try reinstalling boost. > >> > > >> > If you’re still unable to get ./configure to find boost then please attach the full output including all the commands that you ran. > >> > > >> > Jonathan > >> > > >> > > >> > 2022년 5월 1일 (일) 15:41, Daniel Lobo <dan...@gm...>님이 작성: > >> >> > >> >> Hi, > >> >> > >> >> Many thanks for your response. > >> >> > >> >> Yes I ran 'sudo apt-get install libboost-all-dev' to install boost. > >> >> However still I get this error. > >> >> > >> >> How can I find where the boost is installed and how can I pass that > >> >> information './configure ' line? > >> >> > >> >> Apologies for trivial question if any, as I am not very expert in > >> >> Linux ecosystem. > >> >> > >> >> Thanks and regards, > >> >> > >> >> On Sun, 1 May 2022 at 11:53, Jonathan Sweemer <sw...@gm...> wrote: > >> >> > > >> >> > Hi Daniel, > >> >> > > >> >> > When you say that you “install[ed] boost already as provided in the instruction page” do you mean that you ran the following command? > >> >> > > >> >> > sudo apt-get install libboost-all-dev > >> >> > > >> >> > If so then you shouldn’t need to use the —with-boost-include and —with-boost-lib flags when configuring QuantLib. As the install guide mentions, you only need those flags when you install boost in a non-standard location. > >> >> > > >> >> > Jonathan > >> >> > > >> >> > > >> >> > 2022년 5월 1일 (일) 02:25, Daniel Lobo <dan...@gm...>님이 작성: > >> >> >> > >> >> >> Hi, > >> >> >> > >> >> >> I am trying to install Quantlib in my Ubuntu VM. I was following the > >> >> >> instructions as provided in > >> >> >> https://www.quantlib.org/install/linux.shtml > >> >> >> > >> >> >> But this installation failed when I executed > >> >> >> > >> >> >> ./configure --with-boost-include=/home/foo/include > >> >> >> --with-boost-lib=/home/foo/lib > >> >> >> > >> >> >> > >> >> >> > >> >> >> The error I got is > >> >> >> > >> >> >> $ ./configure --with-boost-include=/home/foo/include > >> >> >> --with-boost-lib=/home/foo/lib > >> >> >> checking for a BSD-compatible install... /usr/bin/install -c > >> >> >> checking whether build environment is sane... yes > >> >> >> checking for a race-free mkdir -p... /usr/bin/mkdir -p > >> >> >> checking for gawk... no > >> >> >> checking for mawk... mawk > >> >> >> checking whether make sets $(MAKE)... no > >> >> >> checking whether make supports nested variables... no > >> >> >> checking whether UID '1000' is supported by ustar format... yes > >> >> >> checking whether GID '1000' is supported by ustar format... yes > >> >> >> checking how to create a ustar tar archive... gnutar > >> >> >> checking for gawk... (cached) mawk > >> >> >> checking for gcc... gcc > >> >> >> checking whether the C compiler works... yes > >> >> >> checking for C compiler default output file name... a.out > >> >> >> checking for suffix of executables... > >> >> >> checking whether we are cross compiling... no > >> >> >> checking for suffix of object files... o > >> >> >> checking whether the compiler supports GNU C... yes > >> >> >> checking whether gcc accepts -g... yes > >> >> >> checking for gcc option to enable C11 features... none needed > >> >> >> checking whether gcc understands -c and -o together... yes > >> >> >> checking whether make supports the include directive... no > >> >> >> checking dependency style of gcc... none > >> >> >> checking for g++... no > >> >> >> checking for c++... no > >> >> >> checking for gpp... no > >> >> >> checking for aCC... no > >> >> >> checking for CC... no > >> >> >> checking for cxx... no > >> >> >> checking for cc++... no > >> >> >> checking for cl.exe... no > >> >> >> checking for FCC... no > >> >> >> checking for KCC... no > >> >> >> checking for RCC... no > >> >> >> checking for xlC_r... no > >> >> >> checking for xlC... no > >> >> >> checking for clang++... no > >> >> >> checking whether the compiler supports GNU C++... no > >> >> >> checking whether g++ accepts -g... no > >> >> >> checking for g++ option to enable C++11 features... none needed > >> >> >> checking dependency style of g++... none > >> >> >> checking how to run the C preprocessor... gcc -E > >> >> >> checking build system type... x86_64-pc-linux-gnu > >> >> >> checking host system type... x86_64-pc-linux-gnu > >> >> >> checking how to print strings... printf > >> >> >> checking for a sed that does not truncate output... /usr/bin/sed > >> >> >> checking for grep that handles long lines and -e... /usr/bin/grep > >> >> >> checking for egrep... /usr/bin/grep -E > >> >> >> checking for fgrep... /usr/bin/grep -F > >> >> >> checking for ld used by gcc... /usr/bin/ld > >> >> >> checking if the linker (/usr/bin/ld) is GNU ld... yes > >> >> >> checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B > >> >> >> checking the name lister (/usr/bin/nm -B) interface... BSD nm > >> >> >> checking whether ln -s works... yes > >> >> >> checking the maximum length of command line arguments... 1572864 > >> >> >> checking how to convert x86_64-pc-linux-gnu file names to > >> >> >> x86_64-pc-linux-gnu format... func_convert_file_noop > >> >> >> checking how to convert x86_64-pc-linux-gnu file names to toolchain > >> >> >> format... func_convert_file_noop > >> >> >> checking for /usr/bin/ld option to reload object files... -r > >> >> >> checking for objdump... objdump > >> >> >> checking how to recognize dependent libraries... pass_all > >> >> >> checking for dlltool... no > >> >> >> checking how to associate runtime and link libraries... printf %s\n > >> >> >> checking for ar... ar > >> >> >> checking for archiver @FILE support... @ > >> >> >> checking for strip... strip > >> >> >> checking for ranlib... ranlib > >> >> >> checking command to parse /usr/bin/nm -B output from gcc object... ok > >> >> >> checking for sysroot... no > >> >> >> checking for a working dd... /usr/bin/dd > >> >> >> checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1 > >> >> >> checking for mt... mt > >> >> >> checking if mt is a manifest tool... no > >> >> >> checking for stdio.h... yes > >> >> >> checking for stdlib.h... yes > >> >> >> checking for string.h... yes > >> >> >> checking for inttypes.h... yes > >> >> >> checking for stdint.h... yes > >> >> >> checking for strings.h... yes > >> >> >> checking for sys/stat.h... yes > >> >> >> checking for sys/types.h... yes > >> >> >> checking for unistd.h... yes > >> >> >> checking for dlfcn.h... yes > >> >> >> checking for objdir... .libs > >> >> >> checking if gcc supports -fno-rtti -fno-exceptions... no > >> >> >> checking for gcc option to produce PIC... -fPIC -DPIC > >> >> >> checking if gcc PIC flag -fPIC -DPIC works... yes > >> >> >> checking if gcc static flag -static works... yes > >> >> >> checking if gcc supports -c -o file.o... yes > >> >> >> checking if gcc supports -c -o file.o... (cached) yes > >> >> >> checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports > >> >> >> shared libraries... yes > >> >> >> checking whether -lc should be explicitly linked in... no > >> >> >> checking dynamic linker characteristics... GNU/Linux ld.so > >> >> >> checking how to hardcode library paths into programs... immediate > >> >> >> checking whether stripping libraries is possible... yes > >> >> >> checking if libtool supports shared libraries... yes > >> >> >> checking whether to build shared libraries... yes > >> >> >> checking whether to build static libraries... yes > >> >> >> checking for C++11 support... no: adding -std=c++11 to CXXFLAGS > >> >> >> checking for Boost development files... no > >> >> >> configure: error: Boost development files not found > >> >> >> > >> >> >> Could you please help how to resolve this error. I executed the code > >> >> >> to install boost already as provided in the instruction page. > >> >> >> > >> >> >> > >> >> >> _______________________________________________ > >> >> >> QuantLib-users mailing list > >> >> >> Qua...@li... > >> >> >> https://lists.sourceforge.net/lists/listinfo/quantlib-users > >> > >> > >> _______________________________________________ > >> QuantLib-users mailing list > >> Qua...@li... > >> https://lists.sourceforge.net/lists/listinfo/quantlib-users > > > > > > > > _______________________________________________ > > QuantLib-users mailing list > > Qua...@li... > > https://lists.sourceforge.net/lists/listinfo/quantlib-users |
|
From: Daniel L. <dan...@gm...> - 2022-05-03 10:25:22
|
Many thanks for your responses. whereis boost returns below location, $ whereis boost boost: /usr/include/boost Where can I see the generated config.log file? Thanks for your time. On Tue, 3 May 2022 at 03:29, Conrad Cole <con...@gm...> wrote: > > whereis boost is the command to find the location of the installed boost header files. > > On 5/2/22 17:08, Luigi Ballabio wrote: > > Can you look inside the generated config.log file and see what compiler error you're getting exactly? > > Luigi > > > On Mon, May 2, 2022 at 7:49 PM Daniel Lobo <dan...@gm...> wrote: >> >> Many thanks. >> >> I ran below codes to remove and reinstall boost >> >> sudo apt-get remove libboost-all-dev >> sudo apt-get install libboost-all-dev >> >> boost installed in /usr/include >> >> :/usr/include$ ls >> aio.h complex.h error.h features-time64.h getopt.h >> langinfo.h math.h netdb.h numa.h >> python3.10 setjmp.h string.h time.h video >> aliases.h cpio.h evdns.h fenv.h glob.h >> lastlog.h mcheck.h neteconet numaif.h rdma >> sgtty.h strings.h tirpc wait.h >> alloca.h crypt.h event2 finclude >> gnu-versions.h libgen.h memory.h netinet obstack.h >> re_comp.h shadow.h sudo_plugin.h ttyent.h wchar.h >> argp.h ctype.h event.h fmtmsg.h grp.h >> libintl.h misc netipx openvpn regex.h >> signal.h syscall.h uchar.h wctype.h >> argz.h dirent.h evhttp.h fnmatch.h gshadow.h >> libltdl mntent.h netiucv paths.h regexp.h >> sound sysexits.h ucontext.h wordexp.h >> ar.h dlfcn.h evrpc.h fstab.h hwloc >> libnl3 monetary.h netpacket poll.h resolv.h >> spawn.h syslog.h ulimit.h X11 >> arpa drm evutil.h fts.h hwloc.h >> limits.h mqueue.h netrom printf.h rpc >> stab.h tar.h unicode x86_64-linux-gnu >> asm-generic elf.h execinfo.h ftw.h iconv.h >> link.h mtd netrose proc_service.h rpcsvc >> stdc-predef.h termio.h unistd.h xen >> assert.h endian.h expat_external.h gcalc-2 ifaddrs.h >> linux net nfs protocols sched.h >> stdint.h termios.h utime.h xorg >> boost >> >> But still get error when I run ./configure >> >> Below is the log that I get >> >> $ ./configure >> checking for a BSD-compatible install... /usr/bin/install -c >> checking whether build environment is sane... yes >> checking for a race-free mkdir -p... /usr/bin/mkdir -p >> checking for gawk... no >> checking for mawk... mawk >> checking whether make sets $(MAKE)... no >> checking whether make supports nested variables... no >> checking whether UID '1000' is supported by ustar format... yes >> checking whether GID '1000' is supported by ustar format... yes >> checking how to create a ustar tar archive... gnutar >> checking for gawk... (cached) mawk >> checking for gcc... gcc >> checking whether the C compiler works... yes >> checking for C compiler default output file name... a.out >> checking for suffix of executables... >> checking whether we are cross compiling... no >> checking for suffix of object files... o >> checking whether the compiler supports GNU C... yes >> checking whether gcc accepts -g... yes >> checking for gcc option to enable C11 features... none needed >> checking whether gcc understands -c and -o together... yes >> checking whether make supports the include directive... no >> checking dependency style of gcc... none >> checking for g++... no >> checking for c++... no >> checking for gpp... no >> checking for aCC... no >> checking for CC... no >> checking for cxx... no >> checking for cc++... no >> checking for cl.exe... no >> checking for FCC... no >> checking for KCC... no >> checking for RCC... no >> checking for xlC_r... no >> checking for xlC... no >> checking for clang++... no >> checking whether the compiler supports GNU C++... no >> checking whether g++ accepts -g... no >> checking for g++ option to enable C++11 features... none needed >> checking dependency style of g++... none >> checking how to run the C preprocessor... gcc -E >> checking build system type... x86_64-pc-linux-gnu >> checking host system type... x86_64-pc-linux-gnu >> checking how to print strings... printf >> checking for a sed that does not truncate output... /usr/bin/sed >> checking for grep that handles long lines and -e... /usr/bin/grep >> checking for egrep... /usr/bin/grep -E >> checking for fgrep... /usr/bin/grep -F >> checking for ld used by gcc... /usr/bin/ld >> checking if the linker (/usr/bin/ld) is GNU ld... yes >> checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B >> checking the name lister (/usr/bin/nm -B) interface... BSD nm >> checking whether ln -s works... yes >> checking the maximum length of command line arguments... 1572864 >> checking how to convert x86_64-pc-linux-gnu file names to >> x86_64-pc-linux-gnu format... func_convert_file_noop >> checking how to convert x86_64-pc-linux-gnu file names to toolchain >> format... func_convert_file_noop >> checking for /usr/bin/ld option to reload object files... -r >> checking for objdump... objdump >> checking how to recognize dependent libraries... pass_all >> checking for dlltool... no >> checking how to associate runtime and link libraries... printf %s\n >> checking for ar... ar >> checking for archiver @FILE support... @ >> checking for strip... strip >> checking for ranlib... ranlib >> checking command to parse /usr/bin/nm -B output from gcc object... ok >> checking for sysroot... no >> checking for a working dd... /usr/bin/dd >> checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1 >> checking for mt... mt >> checking if mt is a manifest tool... no >> checking for stdio.h... yes >> checking for stdlib.h... yes >> checking for string.h... yes >> checking for inttypes.h... yes >> checking for stdint.h... yes >> checking for strings.h... yes >> checking for sys/stat.h... yes >> checking for sys/types.h... yes >> checking for unistd.h... yes >> checking for dlfcn.h... yes >> checking for objdir... .libs >> checking if gcc supports -fno-rtti -fno-exceptions... no >> checking for gcc option to produce PIC... -fPIC -DPIC >> checking if gcc PIC flag -fPIC -DPIC works... yes >> checking if gcc static flag -static works... yes >> checking if gcc supports -c -o file.o... yes >> checking if gcc supports -c -o file.o... (cached) yes >> checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports >> shared libraries... yes >> checking whether -lc should be explicitly linked in... no >> checking dynamic linker characteristics... GNU/Linux ld.so >> checking how to hardcode library paths into programs... immediate >> checking whether stripping libraries is possible... yes >> checking if libtool supports shared libraries... yes >> checking whether to build shared libraries... yes >> checking whether to build static libraries... yes >> checking for C++11 support... no: adding -std=c++11 to CXXFLAGS >> checking for Boost development files... no >> configure: error: Boost development files not found >> >> >> Any pointer how to resolve this will be very helpful. >> >> Thanks >> >> On Sun, 1 May 2022 at 13:16, Jonathan Sweemer <sw...@gm...> wrote: >> > >> > Hi Daniel, >> > >> > Just to confirm, you’re no longer running ./configure with the —with-boost-include and —with-boost-lib flags right? >> > >> > If so then I would expect the configure script to find your boost installation. Please check that you see boost headers in /usr/include/boost and if not, try reinstalling boost. >> > >> > If you’re still unable to get ./configure to find boost then please attach the full output including all the commands that you ran. >> > >> > Jonathan >> > >> > >> > 2022년 5월 1일 (일) 15:41, Daniel Lobo <dan...@gm...>님이 작성: >> >> >> >> Hi, >> >> >> >> Many thanks for your response. >> >> >> >> Yes I ran 'sudo apt-get install libboost-all-dev' to install boost. >> >> However still I get this error. >> >> >> >> How can I find where the boost is installed and how can I pass that >> >> information './configure ' line? >> >> >> >> Apologies for trivial question if any, as I am not very expert in >> >> Linux ecosystem. >> >> >> >> Thanks and regards, >> >> >> >> On Sun, 1 May 2022 at 11:53, Jonathan Sweemer <sw...@gm...> wrote: >> >> > >> >> > Hi Daniel, >> >> > >> >> > When you say that you “install[ed] boost already as provided in the instruction page” do you mean that you ran the following command? >> >> > >> >> > sudo apt-get install libboost-all-dev >> >> > >> >> > If so then you shouldn’t need to use the —with-boost-include and —with-boost-lib flags when configuring QuantLib. As the install guide mentions, you only need those flags when you install boost in a non-standard location. >> >> > >> >> > Jonathan >> >> > >> >> > >> >> > 2022년 5월 1일 (일) 02:25, Daniel Lobo <dan...@gm...>님이 작성: >> >> >> >> >> >> Hi, >> >> >> >> >> >> I am trying to install Quantlib in my Ubuntu VM. I was following the >> >> >> instructions as provided in >> >> >> https://www.quantlib.org/install/linux.shtml >> >> >> >> >> >> But this installation failed when I executed >> >> >> >> >> >> ./configure --with-boost-include=/home/foo/include >> >> >> --with-boost-lib=/home/foo/lib >> >> >> >> >> >> >> >> >> >> >> >> The error I got is >> >> >> >> >> >> $ ./configure --with-boost-include=/home/foo/include >> >> >> --with-boost-lib=/home/foo/lib >> >> >> checking for a BSD-compatible install... /usr/bin/install -c >> >> >> checking whether build environment is sane... yes >> >> >> checking for a race-free mkdir -p... /usr/bin/mkdir -p >> >> >> checking for gawk... no >> >> >> checking for mawk... mawk >> >> >> checking whether make sets $(MAKE)... no >> >> >> checking whether make supports nested variables... no >> >> >> checking whether UID '1000' is supported by ustar format... yes >> >> >> checking whether GID '1000' is supported by ustar format... yes >> >> >> checking how to create a ustar tar archive... gnutar >> >> >> checking for gawk... (cached) mawk >> >> >> checking for gcc... gcc >> >> >> checking whether the C compiler works... yes >> >> >> checking for C compiler default output file name... a.out >> >> >> checking for suffix of executables... >> >> >> checking whether we are cross compiling... no >> >> >> checking for suffix of object files... o >> >> >> checking whether the compiler supports GNU C... yes >> >> >> checking whether gcc accepts -g... yes >> >> >> checking for gcc option to enable C11 features... none needed >> >> >> checking whether gcc understands -c and -o together... yes >> >> >> checking whether make supports the include directive... no >> >> >> checking dependency style of gcc... none >> >> >> checking for g++... no >> >> >> checking for c++... no >> >> >> checking for gpp... no >> >> >> checking for aCC... no >> >> >> checking for CC... no >> >> >> checking for cxx... no >> >> >> checking for cc++... no >> >> >> checking for cl.exe... no >> >> >> checking for FCC... no >> >> >> checking for KCC... no >> >> >> checking for RCC... no >> >> >> checking for xlC_r... no >> >> >> checking for xlC... no >> >> >> checking for clang++... no >> >> >> checking whether the compiler supports GNU C++... no >> >> >> checking whether g++ accepts -g... no >> >> >> checking for g++ option to enable C++11 features... none needed >> >> >> checking dependency style of g++... none >> >> >> checking how to run the C preprocessor... gcc -E >> >> >> checking build system type... x86_64-pc-linux-gnu >> >> >> checking host system type... x86_64-pc-linux-gnu >> >> >> checking how to print strings... printf >> >> >> checking for a sed that does not truncate output... /usr/bin/sed >> >> >> checking for grep that handles long lines and -e... /usr/bin/grep >> >> >> checking for egrep... /usr/bin/grep -E >> >> >> checking for fgrep... /usr/bin/grep -F >> >> >> checking for ld used by gcc... /usr/bin/ld >> >> >> checking if the linker (/usr/bin/ld) is GNU ld... yes >> >> >> checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B >> >> >> checking the name lister (/usr/bin/nm -B) interface... BSD nm >> >> >> checking whether ln -s works... yes >> >> >> checking the maximum length of command line arguments... 1572864 >> >> >> checking how to convert x86_64-pc-linux-gnu file names to >> >> >> x86_64-pc-linux-gnu format... func_convert_file_noop >> >> >> checking how to convert x86_64-pc-linux-gnu file names to toolchain >> >> >> format... func_convert_file_noop >> >> >> checking for /usr/bin/ld option to reload object files... -r >> >> >> checking for objdump... objdump >> >> >> checking how to recognize dependent libraries... pass_all >> >> >> checking for dlltool... no >> >> >> checking how to associate runtime and link libraries... printf %s\n >> >> >> checking for ar... ar >> >> >> checking for archiver @FILE support... @ >> >> >> checking for strip... strip >> >> >> checking for ranlib... ranlib >> >> >> checking command to parse /usr/bin/nm -B output from gcc object... ok >> >> >> checking for sysroot... no >> >> >> checking for a working dd... /usr/bin/dd >> >> >> checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1 >> >> >> checking for mt... mt >> >> >> checking if mt is a manifest tool... no >> >> >> checking for stdio.h... yes >> >> >> checking for stdlib.h... yes >> >> >> checking for string.h... yes >> >> >> checking for inttypes.h... yes >> >> >> checking for stdint.h... yes >> >> >> checking for strings.h... yes >> >> >> checking for sys/stat.h... yes >> >> >> checking for sys/types.h... yes >> >> >> checking for unistd.h... yes >> >> >> checking for dlfcn.h... yes >> >> >> checking for objdir... .libs >> >> >> checking if gcc supports -fno-rtti -fno-exceptions... no >> >> >> checking for gcc option to produce PIC... -fPIC -DPIC >> >> >> checking if gcc PIC flag -fPIC -DPIC works... yes >> >> >> checking if gcc static flag -static works... yes >> >> >> checking if gcc supports -c -o file.o... yes >> >> >> checking if gcc supports -c -o file.o... (cached) yes >> >> >> checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports >> >> >> shared libraries... yes >> >> >> checking whether -lc should be explicitly linked in... no >> >> >> checking dynamic linker characteristics... GNU/Linux ld.so >> >> >> checking how to hardcode library paths into programs... immediate >> >> >> checking whether stripping libraries is possible... yes >> >> >> checking if libtool supports shared libraries... yes >> >> >> checking whether to build shared libraries... yes >> >> >> checking whether to build static libraries... yes >> >> >> checking for C++11 support... no: adding -std=c++11 to CXXFLAGS >> >> >> checking for Boost development files... no >> >> >> configure: error: Boost development files not found >> >> >> >> >> >> Could you please help how to resolve this error. I executed the code >> >> >> to install boost already as provided in the instruction page. >> >> >> >> >> >> >> >> >> _______________________________________________ >> >> >> QuantLib-users mailing list >> >> >> Qua...@li... >> >> >> https://lists.sourceforge.net/lists/listinfo/quantlib-users >> >> >> _______________________________________________ >> QuantLib-users mailing list >> Qua...@li... >> https://lists.sourceforge.net/lists/listinfo/quantlib-users > > > > _______________________________________________ > QuantLib-users mailing list > Qua...@li... > https://lists.sourceforge.net/lists/listinfo/quantlib-users |
|
From: Mr D. P. <dan...@uq...> - 2022-05-03 06:49:09
|
Hi all, I've been attempting to model some JGB bonds in Quantlib to then use its fixed rate bond objects to try build out a discounting curve from it. One thing I like to do is check my prices relative to Bloomberg prior to proceeding and have noticed that while the accrued interest reconciles, the prices (both clean and dirty are far off). The reasoning seems to be that JGBs use a simple interest calculation, differing compounded calcs used by the majority of other bonds out there. I just wanted to check if there is a method within the Quantlib bond object to directly calculate the simple yield quoted in Bloomberg using the respective Bloomberg price? Please let me know if you need any further clarification. Kind regards Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows |
|
From: Chirag D. <chi...@ya...> - 2022-05-03 02:58:22
|
Thank you Jonathan for your kind advice.
I tried using VC PKG to install quantlib but I believe you cannot install it on Windows. I got the error message below.
Error: quantlib[core] is only supported on '!(windows & !static)'
On the website Compatibility, it indicates Windows supported. Can you confirm Windows is not supported and if you know when it might be possible ? Browse public vcpkg packages
|
|
| |
Browse public vcpkg packages
Explore vcpkg libraries to install
|
|
|
Thank you for your guidance
On Monday, May 2, 2022, 08:33:37 PM GMT+8, Jonathan Sweemer <sw...@gm...> wrote:
Hi Chirag,
Did you follow the instructions in the CMake output and 'Add the installation prefix of "QuantLib" to CMAKE_PREFIX_PATH or set "QuantLib_DIR" to a directory containing one of the above files'?
If C:/local/QuantLib-1.24/cmake-build-debug-visualstudio2017 is your CMake build directory, then the 'above files' will be found in the cmake directory under that build directory.
If that doesn't work then the best I can do is point you to the documentation on CMake config mode[1] and wish you luck, as I won't be able to offer much further help remotely.
By the way, the quantlib-vcpkg-example repo that you found is an example of how to link your project to QuantLib installed through vcpkg, which you haven't used. If you'd like to, you can try out vcpkg, and it may make your life easier in the long run, but be aware that it has a learning curve of its own to grapple with first.
[1] https://cmake.org/cmake/help/latest/command/find_package.html#config-mode-search-procedure
|
|
From: Conrad C. <con...@gm...> - 2022-05-02 21:59:16
|
*whereis boost* is the command to find the location of the installed boost header files. On 5/2/22 17:08, Luigi Ballabio wrote: > Can you look inside the generated config.log file and see what > compiler error you're getting exactly? > > Luigi > > > On Mon, May 2, 2022 at 7:49 PM Daniel Lobo <dan...@gm...> > wrote: > > Many thanks. > > I ran below codes to remove and reinstall boost > > sudo apt-get remove libboost-all-dev > sudo apt-get install libboost-all-dev > > boost installed in /usr/include > > :/usr/include$ ls > aio.h complex.h error.h features-time64.h getopt.h > langinfo.h math.h netdb.h numa.h > python3.10 setjmp.h string.h time.h video > aliases.h cpio.h evdns.h fenv.h glob.h > lastlog.h mcheck.h neteconet numaif.h rdma > sgtty.h strings.h tirpc wait.h > alloca.h crypt.h event2 finclude > gnu-versions.h libgen.h memory.h netinet obstack.h > re_comp.h shadow.h sudo_plugin.h ttyent.h wchar.h > argp.h ctype.h event.h fmtmsg.h grp.h > libintl.h misc netipx openvpn regex.h > signal.h syscall.h uchar.h wctype.h > argz.h dirent.h evhttp.h fnmatch.h gshadow.h > libltdl mntent.h netiucv paths.h regexp.h > sound sysexits.h ucontext.h wordexp.h > ar.h dlfcn.h evrpc.h fstab.h hwloc > libnl3 monetary.h netpacket poll.h resolv.h > spawn.h syslog.h ulimit.h X11 > arpa drm evutil.h fts.h hwloc.h > limits.h mqueue.h netrom printf.h rpc > stab.h tar.h unicode x86_64-linux-gnu > asm-generic elf.h execinfo.h ftw.h iconv.h > link.h mtd netrose proc_service.h rpcsvc > stdc-predef.h termio.h unistd.h xen > assert.h endian.h expat_external.h gcalc-2 ifaddrs.h > linux net nfs protocols sched.h > stdint.h termios.h utime.h xorg > boost > > But still get error when I run ./configure > > Below is the log that I get > > $ ./configure > checking for a BSD-compatible install... /usr/bin/install -c > checking whether build environment is sane... yes > checking for a race-free mkdir -p... /usr/bin/mkdir -p > checking for gawk... no > checking for mawk... mawk > checking whether make sets $(MAKE)... no > checking whether make supports nested variables... no > checking whether UID '1000' is supported by ustar format... yes > checking whether GID '1000' is supported by ustar format... yes > checking how to create a ustar tar archive... gnutar > checking for gawk... (cached) mawk > checking for gcc... gcc > checking whether the C compiler works... yes > checking for C compiler default output file name... a.out > checking for suffix of executables... > checking whether we are cross compiling... no > checking for suffix of object files... o > checking whether the compiler supports GNU C... yes > checking whether gcc accepts -g... yes > checking for gcc option to enable C11 features... none needed > checking whether gcc understands -c and -o together... yes > checking whether make supports the include directive... no > checking dependency style of gcc... none > checking for g++... no > checking for c++... no > checking for gpp... no > checking for aCC... no > checking for CC... no > checking for cxx... no > checking for cc++... no > checking for cl.exe... no > checking for FCC... no > checking for KCC... no > checking for RCC... no > checking for xlC_r... no > checking for xlC... no > checking for clang++... no > checking whether the compiler supports GNU C++... no > checking whether g++ accepts -g... no > checking for g++ option to enable C++11 features... none needed > checking dependency style of g++... none > checking how to run the C preprocessor... gcc -E > checking build system type... x86_64-pc-linux-gnu > checking host system type... x86_64-pc-linux-gnu > checking how to print strings... printf > checking for a sed that does not truncate output... /usr/bin/sed > checking for grep that handles long lines and -e... /usr/bin/grep > checking for egrep... /usr/bin/grep -E > checking for fgrep... /usr/bin/grep -F > checking for ld used by gcc... /usr/bin/ld > checking if the linker (/usr/bin/ld) is GNU ld... yes > checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B > checking the name lister (/usr/bin/nm -B) interface... BSD nm > checking whether ln -s works... yes > checking the maximum length of command line arguments... 1572864 > checking how to convert x86_64-pc-linux-gnu file names to > x86_64-pc-linux-gnu format... func_convert_file_noop > checking how to convert x86_64-pc-linux-gnu file names to toolchain > format... func_convert_file_noop > checking for /usr/bin/ld option to reload object files... -r > checking for objdump... objdump > checking how to recognize dependent libraries... pass_all > checking for dlltool... no > checking how to associate runtime and link libraries... printf %s\n > checking for ar... ar > checking for archiver @FILE support... @ > checking for strip... strip > checking for ranlib... ranlib > checking command to parse /usr/bin/nm -B output from gcc object... ok > checking for sysroot... no > checking for a working dd... /usr/bin/dd > checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1 > checking for mt... mt > checking if mt is a manifest tool... no > checking for stdio.h... yes > checking for stdlib.h... yes > checking for string.h... yes > checking for inttypes.h... yes > checking for stdint.h... yes > checking for strings.h... yes > checking for sys/stat.h... yes > checking for sys/types.h... yes > checking for unistd.h... yes > checking for dlfcn.h... yes > checking for objdir... .libs > checking if gcc supports -fno-rtti -fno-exceptions... no > checking for gcc option to produce PIC... -fPIC -DPIC > checking if gcc PIC flag -fPIC -DPIC works... yes > checking if gcc static flag -static works... yes > checking if gcc supports -c -o file.o... yes > checking if gcc supports -c -o file.o... (cached) yes > checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports > shared libraries... yes > checking whether -lc should be explicitly linked in... no > checking dynamic linker characteristics... GNU/Linux ld.so > checking how to hardcode library paths into programs... immediate > checking whether stripping libraries is possible... yes > checking if libtool supports shared libraries... yes > checking whether to build shared libraries... yes > checking whether to build static libraries... yes > checking for C++11 support... no: adding -std=c++11 to CXXFLAGS > checking for Boost development files... no > configure: error: Boost development files not found > > > Any pointer how to resolve this will be very helpful. > > Thanks > > On Sun, 1 May 2022 at 13:16, Jonathan Sweemer <sw...@gm...> > wrote: > > > > Hi Daniel, > > > > Just to confirm, you’re no longer running ./configure with the > —with-boost-include and —with-boost-lib flags right? > > > > If so then I would expect the configure script to find your > boost installation. Please check that you see boost headers in > /usr/include/boost and if not, try reinstalling boost. > > > > If you’re still unable to get ./configure to find boost then > please attach the full output including all the commands that you ran. > > > > Jonathan > > > > > > 2022년 5월 1일 (일) 15:41, Daniel Lobo <dan...@gm...>님이 > 작성: > >> > >> Hi, > >> > >> Many thanks for your response. > >> > >> Yes I ran 'sudo apt-get install libboost-all-dev' to install boost. > >> However still I get this error. > >> > >> How can I find where the boost is installed and how can I pass that > >> information './configure ' line? > >> > >> Apologies for trivial question if any, as I am not very expert in > >> Linux ecosystem. > >> > >> Thanks and regards, > >> > >> On Sun, 1 May 2022 at 11:53, Jonathan Sweemer > <sw...@gm...> wrote: > >> > > >> > Hi Daniel, > >> > > >> > When you say that you “install[ed] boost already as provided > in the instruction page” do you mean that you ran the following > command? > >> > > >> > sudo apt-get install libboost-all-dev > >> > > >> > If so then you shouldn’t need to use the —with-boost-include > and —with-boost-lib flags when configuring QuantLib. As the > install guide mentions, you only need those flags when you install > boost in a non-standard location. > >> > > >> > Jonathan > >> > > >> > > >> > 2022년 5월 1일 (일) 02:25, Daniel Lobo > <dan...@gm...>님이 작성: > >> >> > >> >> Hi, > >> >> > >> >> I am trying to install Quantlib in my Ubuntu VM. I was > following the > >> >> instructions as provided in > >> >> https://www.quantlib.org/install/linux.shtml > >> >> > >> >> But this installation failed when I executed > >> >> > >> >> ./configure --with-boost-include=/home/foo/include > >> >> --with-boost-lib=/home/foo/lib > >> >> > >> >> > >> >> > >> >> The error I got is > >> >> > >> >> $ ./configure --with-boost-include=/home/foo/include > >> >> --with-boost-lib=/home/foo/lib > >> >> checking for a BSD-compatible install... /usr/bin/install -c > >> >> checking whether build environment is sane... yes > >> >> checking for a race-free mkdir -p... /usr/bin/mkdir -p > >> >> checking for gawk... no > >> >> checking for mawk... mawk > >> >> checking whether make sets $(MAKE)... no > >> >> checking whether make supports nested variables... no > >> >> checking whether UID '1000' is supported by ustar format... yes > >> >> checking whether GID '1000' is supported by ustar format... yes > >> >> checking how to create a ustar tar archive... gnutar > >> >> checking for gawk... (cached) mawk > >> >> checking for gcc... gcc > >> >> checking whether the C compiler works... yes > >> >> checking for C compiler default output file name... a.out > >> >> checking for suffix of executables... > >> >> checking whether we are cross compiling... no > >> >> checking for suffix of object files... o > >> >> checking whether the compiler supports GNU C... yes > >> >> checking whether gcc accepts -g... yes > >> >> checking for gcc option to enable C11 features... none needed > >> >> checking whether gcc understands -c and -o together... yes > >> >> checking whether make supports the include directive... no > >> >> checking dependency style of gcc... none > >> >> checking for g++... no > >> >> checking for c++... no > >> >> checking for gpp... no > >> >> checking for aCC... no > >> >> checking for CC... no > >> >> checking for cxx... no > >> >> checking for cc++... no > >> >> checking for cl.exe... no > >> >> checking for FCC... no > >> >> checking for KCC... no > >> >> checking for RCC... no > >> >> checking for xlC_r... no > >> >> checking for xlC... no > >> >> checking for clang++... no > >> >> checking whether the compiler supports GNU C++... no > >> >> checking whether g++ accepts -g... no > >> >> checking for g++ option to enable C++11 features... none needed > >> >> checking dependency style of g++... none > >> >> checking how to run the C preprocessor... gcc -E > >> >> checking build system type... x86_64-pc-linux-gnu > >> >> checking host system type... x86_64-pc-linux-gnu > >> >> checking how to print strings... printf > >> >> checking for a sed that does not truncate output... /usr/bin/sed > >> >> checking for grep that handles long lines and -e... > /usr/bin/grep > >> >> checking for egrep... /usr/bin/grep -E > >> >> checking for fgrep... /usr/bin/grep -F > >> >> checking for ld used by gcc... /usr/bin/ld > >> >> checking if the linker (/usr/bin/ld) is GNU ld... yes > >> >> checking for BSD- or MS-compatible name lister (nm)... > /usr/bin/nm -B > >> >> checking the name lister (/usr/bin/nm -B) interface... BSD nm > >> >> checking whether ln -s works... yes > >> >> checking the maximum length of command line arguments... 1572864 > >> >> checking how to convert x86_64-pc-linux-gnu file names to > >> >> x86_64-pc-linux-gnu format... func_convert_file_noop > >> >> checking how to convert x86_64-pc-linux-gnu file names to > toolchain > >> >> format... func_convert_file_noop > >> >> checking for /usr/bin/ld option to reload object files... -r > >> >> checking for objdump... objdump > >> >> checking how to recognize dependent libraries... pass_all > >> >> checking for dlltool... no > >> >> checking how to associate runtime and link libraries... > printf %s\n > >> >> checking for ar... ar > >> >> checking for archiver @FILE support... @ > >> >> checking for strip... strip > >> >> checking for ranlib... ranlib > >> >> checking command to parse /usr/bin/nm -B output from gcc > object... ok > >> >> checking for sysroot... no > >> >> checking for a working dd... /usr/bin/dd > >> >> checking how to truncate binary pipes... /usr/bin/dd bs=4096 > count=1 > >> >> checking for mt... mt > >> >> checking if mt is a manifest tool... no > >> >> checking for stdio.h... yes > >> >> checking for stdlib.h... yes > >> >> checking for string.h... yes > >> >> checking for inttypes.h... yes > >> >> checking for stdint.h... yes > >> >> checking for strings.h... yes > >> >> checking for sys/stat.h... yes > >> >> checking for sys/types.h... yes > >> >> checking for unistd.h... yes > >> >> checking for dlfcn.h... yes > >> >> checking for objdir... .libs > >> >> checking if gcc supports -fno-rtti -fno-exceptions... no > >> >> checking for gcc option to produce PIC... -fPIC -DPIC > >> >> checking if gcc PIC flag -fPIC -DPIC works... yes > >> >> checking if gcc static flag -static works... yes > >> >> checking if gcc supports -c -o file.o... yes > >> >> checking if gcc supports -c -o file.o... (cached) yes > >> >> checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) > supports > >> >> shared libraries... yes > >> >> checking whether -lc should be explicitly linked in... no > >> >> checking dynamic linker characteristics... GNU/Linux ld.so > >> >> checking how to hardcode library paths into programs... > immediate > >> >> checking whether stripping libraries is possible... yes > >> >> checking if libtool supports shared libraries... yes > >> >> checking whether to build shared libraries... yes > >> >> checking whether to build static libraries... yes > >> >> checking for C++11 support... no: adding -std=c++11 to CXXFLAGS > >> >> checking for Boost development files... no > >> >> configure: error: Boost development files not found > >> >> > >> >> Could you please help how to resolve this error. I executed > the code > >> >> to install boost already as provided in the instruction page. > >> >> > >> >> > >> >> _______________________________________________ > >> >> QuantLib-users mailing list > >> >> Qua...@li... > >> >> https://lists.sourceforge.net/lists/listinfo/quantlib-users > > > _______________________________________________ > QuantLib-users mailing list > Qua...@li... > https://lists.sourceforge.net/lists/listinfo/quantlib-users > > > > _______________________________________________ > QuantLib-users mailing list > Qua...@li... > https://lists.sourceforge.net/lists/listinfo/quantlib-users |
|
From: Conrad C. <con...@gm...> - 2022-05-02 21:13:33
|
Did you also verify that the boost library files are in this directory /usr/lib/x86_64-linux-gnu? *include: /usr/include/boost* *lib: /usr/lib/x86_64-linux-gnu* You should try executing ./configure again with the boost lib and include flags using the proper directories. Are the boost installation directories in your PATH variable? On 5/2/22 13:44, Daniel Lobo wrote: > Many thanks. > > I ran below codes to remove and reinstall boost > > sudo apt-get remove libboost-all-dev > sudo apt-get install libboost-all-dev > > boost installed in /usr/include > > :/usr/include$ ls > aio.h complex.h error.h features-time64.h getopt.h > langinfo.h math.h netdb.h numa.h > python3.10 setjmp.h string.h time.h video > aliases.h cpio.h evdns.h fenv.h glob.h > lastlog.h mcheck.h neteconet numaif.h rdma > sgtty.h strings.h tirpc wait.h > alloca.h crypt.h event2 finclude > gnu-versions.h libgen.h memory.h netinet obstack.h > re_comp.h shadow.h sudo_plugin.h ttyent.h wchar.h > argp.h ctype.h event.h fmtmsg.h grp.h > libintl.h misc netipx openvpn regex.h > signal.h syscall.h uchar.h wctype.h > argz.h dirent.h evhttp.h fnmatch.h gshadow.h > libltdl mntent.h netiucv paths.h regexp.h > sound sysexits.h ucontext.h wordexp.h > ar.h dlfcn.h evrpc.h fstab.h hwloc > libnl3 monetary.h netpacket poll.h resolv.h > spawn.h syslog.h ulimit.h X11 > arpa drm evutil.h fts.h hwloc.h > limits.h mqueue.h netrom printf.h rpc > stab.h tar.h unicode x86_64-linux-gnu > asm-generic elf.h execinfo.h ftw.h iconv.h > link.h mtd netrose proc_service.h rpcsvc > stdc-predef.h termio.h unistd.h xen > assert.h endian.h expat_external.h gcalc-2 ifaddrs.h > linux net nfs protocols sched.h > stdint.h termios.h utime.h xorg > boost > > But still get error when I run ./configure > > Below is the log that I get > > $ ./configure > checking for a BSD-compatible install... /usr/bin/install -c > checking whether build environment is sane... yes > checking for a race-free mkdir -p... /usr/bin/mkdir -p > checking for gawk... no > checking for mawk... mawk > checking whether make sets $(MAKE)... no > checking whether make supports nested variables... no > checking whether UID '1000' is supported by ustar format... yes > checking whether GID '1000' is supported by ustar format... yes > checking how to create a ustar tar archive... gnutar > checking for gawk... (cached) mawk > checking for gcc... gcc > checking whether the C compiler works... yes > checking for C compiler default output file name... a.out > checking for suffix of executables... > checking whether we are cross compiling... no > checking for suffix of object files... o > checking whether the compiler supports GNU C... yes > checking whether gcc accepts -g... yes > checking for gcc option to enable C11 features... none needed > checking whether gcc understands -c and -o together... yes > checking whether make supports the include directive... no > checking dependency style of gcc... none > checking for g++... no > checking for c++... no > checking for gpp... no > checking for aCC... no > checking for CC... no > checking for cxx... no > checking for cc++... no > checking for cl.exe... no > checking for FCC... no > checking for KCC... no > checking for RCC... no > checking for xlC_r... no > checking for xlC... no > checking for clang++... no > checking whether the compiler supports GNU C++... no > checking whether g++ accepts -g... no > checking for g++ option to enable C++11 features... none needed > checking dependency style of g++... none > checking how to run the C preprocessor... gcc -E > checking build system type... x86_64-pc-linux-gnu > checking host system type... x86_64-pc-linux-gnu > checking how to print strings... printf > checking for a sed that does not truncate output... /usr/bin/sed > checking for grep that handles long lines and -e... /usr/bin/grep > checking for egrep... /usr/bin/grep -E > checking for fgrep... /usr/bin/grep -F > checking for ld used by gcc... /usr/bin/ld > checking if the linker (/usr/bin/ld) is GNU ld... yes > checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B > checking the name lister (/usr/bin/nm -B) interface... BSD nm > checking whether ln -s works... yes > checking the maximum length of command line arguments... 1572864 > checking how to convert x86_64-pc-linux-gnu file names to > x86_64-pc-linux-gnu format... func_convert_file_noop > checking how to convert x86_64-pc-linux-gnu file names to toolchain > format... func_convert_file_noop > checking for /usr/bin/ld option to reload object files... -r > checking for objdump... objdump > checking how to recognize dependent libraries... pass_all > checking for dlltool... no > checking how to associate runtime and link libraries... printf %s\n > checking for ar... ar > checking for archiver @FILE support... @ > checking for strip... strip > checking for ranlib... ranlib > checking command to parse /usr/bin/nm -B output from gcc object... ok > checking for sysroot... no > checking for a working dd... /usr/bin/dd > checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1 > checking for mt... mt > checking if mt is a manifest tool... no > checking for stdio.h... yes > checking for stdlib.h... yes > checking for string.h... yes > checking for inttypes.h... yes > checking for stdint.h... yes > checking for strings.h... yes > checking for sys/stat.h... yes > checking for sys/types.h... yes > checking for unistd.h... yes > checking for dlfcn.h... yes > checking for objdir... .libs > checking if gcc supports -fno-rtti -fno-exceptions... no > checking for gcc option to produce PIC... -fPIC -DPIC > checking if gcc PIC flag -fPIC -DPIC works... yes > checking if gcc static flag -static works... yes > checking if gcc supports -c -o file.o... yes > checking if gcc supports -c -o file.o... (cached) yes > checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports > shared libraries... yes > checking whether -lc should be explicitly linked in... no > checking dynamic linker characteristics... GNU/Linux ld.so > checking how to hardcode library paths into programs... immediate > checking whether stripping libraries is possible... yes > checking if libtool supports shared libraries... yes > checking whether to build shared libraries... yes > checking whether to build static libraries... yes > checking for C++11 support... no: adding -std=c++11 to CXXFLAGS > checking for Boost development files... no > configure: error: Boost development files not found > > > Any pointer how to resolve this will be very helpful. > > Thanks > > On Sun, 1 May 2022 at 13:16, Jonathan Sweemer<sw...@gm...> wrote: >> Hi Daniel, >> >> Just to confirm, you’re no longer running ./configure with the —with-boost-include and —with-boost-lib flags right? >> >> If so then I would expect the configure script to find your boost installation. Please check that you see boost headers in /usr/include/boost and if not, try reinstalling boost. >> >> If you’re still unable to get ./configure to find boost then please attach the full output including all the commands that you ran. >> >> Jonathan >> >> >> 2022년 5월 1일 (일) 15:41, Daniel Lobo<dan...@gm...>님이 작성: >>> Hi, >>> >>> Many thanks for your response. >>> >>> Yes I ran 'sudo apt-get install libboost-all-dev' to install boost. >>> However still I get this error. >>> >>> How can I find where the boost is installed and how can I pass that >>> information './configure ' line? >>> >>> Apologies for trivial question if any, as I am not very expert in >>> Linux ecosystem. >>> >>> Thanks and regards, >>> >>> On Sun, 1 May 2022 at 11:53, Jonathan Sweemer<sw...@gm...> wrote: >>>> Hi Daniel, >>>> >>>> When you say that you “install[ed] boost already as provided in the instruction page” do you mean that you ran the following command? >>>> >>>> sudo apt-get install libboost-all-dev >>>> >>>> If so then you shouldn’t need to use the —with-boost-include and —with-boost-lib flags when configuring QuantLib. As the install guide mentions, you only need those flags when you install boost in a non-standard location. >>>> >>>> Jonathan >>>> >>>> >>>> 2022년 5월 1일 (일) 02:25, Daniel Lobo<dan...@gm...>님이 작성: >>>>> Hi, >>>>> >>>>> I am trying to install Quantlib in my Ubuntu VM. I was following the >>>>> instructions as provided in >>>>> https://www.quantlib.org/install/linux.shtml >>>>> >>>>> But this installation failed when I executed >>>>> >>>>> ./configure --with-boost-include=/home/foo/include >>>>> --with-boost-lib=/home/foo/lib >>>>> >>>>> >>>>> >>>>> The error I got is >>>>> >>>>> $ ./configure --with-boost-include=/home/foo/include >>>>> --with-boost-lib=/home/foo/lib >>>>> checking for a BSD-compatible install... /usr/bin/install -c >>>>> checking whether build environment is sane... yes >>>>> checking for a race-free mkdir -p... /usr/bin/mkdir -p >>>>> checking for gawk... no >>>>> checking for mawk... mawk >>>>> checking whether make sets $(MAKE)... no >>>>> checking whether make supports nested variables... no >>>>> checking whether UID '1000' is supported by ustar format... yes >>>>> checking whether GID '1000' is supported by ustar format... yes >>>>> checking how to create a ustar tar archive... gnutar >>>>> checking for gawk... (cached) mawk >>>>> checking for gcc... gcc >>>>> checking whether the C compiler works... yes >>>>> checking for C compiler default output file name... a.out >>>>> checking for suffix of executables... >>>>> checking whether we are cross compiling... no >>>>> checking for suffix of object files... o >>>>> checking whether the compiler supports GNU C... yes >>>>> checking whether gcc accepts -g... yes >>>>> checking for gcc option to enable C11 features... none needed >>>>> checking whether gcc understands -c and -o together... yes >>>>> checking whether make supports the include directive... no >>>>> checking dependency style of gcc... none >>>>> checking for g++... no >>>>> checking for c++... no >>>>> checking for gpp... no >>>>> checking for aCC... no >>>>> checking for CC... no >>>>> checking for cxx... no >>>>> checking for cc++... no >>>>> checking for cl.exe... no >>>>> checking for FCC... no >>>>> checking for KCC... no >>>>> checking for RCC... no >>>>> checking for xlC_r... no >>>>> checking for xlC... no >>>>> checking for clang++... no >>>>> checking whether the compiler supports GNU C++... no >>>>> checking whether g++ accepts -g... no >>>>> checking for g++ option to enable C++11 features... none needed >>>>> checking dependency style of g++... none >>>>> checking how to run the C preprocessor... gcc -E >>>>> checking build system type... x86_64-pc-linux-gnu >>>>> checking host system type... x86_64-pc-linux-gnu >>>>> checking how to print strings... printf >>>>> checking for a sed that does not truncate output... /usr/bin/sed >>>>> checking for grep that handles long lines and -e... /usr/bin/grep >>>>> checking for egrep... /usr/bin/grep -E >>>>> checking for fgrep... /usr/bin/grep -F >>>>> checking for ld used by gcc... /usr/bin/ld >>>>> checking if the linker (/usr/bin/ld) is GNU ld... yes >>>>> checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B >>>>> checking the name lister (/usr/bin/nm -B) interface... BSD nm >>>>> checking whether ln -s works... yes >>>>> checking the maximum length of command line arguments... 1572864 >>>>> checking how to convert x86_64-pc-linux-gnu file names to >>>>> x86_64-pc-linux-gnu format... func_convert_file_noop >>>>> checking how to convert x86_64-pc-linux-gnu file names to toolchain >>>>> format... func_convert_file_noop >>>>> checking for /usr/bin/ld option to reload object files... -r >>>>> checking for objdump... objdump >>>>> checking how to recognize dependent libraries... pass_all >>>>> checking for dlltool... no >>>>> checking how to associate runtime and link libraries... printf %s\n >>>>> checking for ar... ar >>>>> checking for archiver @FILE support... @ >>>>> checking for strip... strip >>>>> checking for ranlib... ranlib >>>>> checking command to parse /usr/bin/nm -B output from gcc object... ok >>>>> checking for sysroot... no >>>>> checking for a working dd... /usr/bin/dd >>>>> checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1 >>>>> checking for mt... mt >>>>> checking if mt is a manifest tool... no >>>>> checking for stdio.h... yes >>>>> checking for stdlib.h... yes >>>>> checking for string.h... yes >>>>> checking for inttypes.h... yes >>>>> checking for stdint.h... yes >>>>> checking for strings.h... yes >>>>> checking for sys/stat.h... yes >>>>> checking for sys/types.h... yes >>>>> checking for unistd.h... yes >>>>> checking for dlfcn.h... yes >>>>> checking for objdir... .libs >>>>> checking if gcc supports -fno-rtti -fno-exceptions... no >>>>> checking for gcc option to produce PIC... -fPIC -DPIC >>>>> checking if gcc PIC flag -fPIC -DPIC works... yes >>>>> checking if gcc static flag -static works... yes >>>>> checking if gcc supports -c -o file.o... yes >>>>> checking if gcc supports -c -o file.o... (cached) yes >>>>> checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports >>>>> shared libraries... yes >>>>> checking whether -lc should be explicitly linked in... no >>>>> checking dynamic linker characteristics... GNU/Linux ld.so >>>>> checking how to hardcode library paths into programs... immediate >>>>> checking whether stripping libraries is possible... yes >>>>> checking if libtool supports shared libraries... yes >>>>> checking whether to build shared libraries... yes >>>>> checking whether to build static libraries... yes >>>>> checking for C++11 support... no: adding -std=c++11 to CXXFLAGS >>>>> checking for Boost development files... no >>>>> configure: error: Boost development files not found >>>>> >>>>> Could you please help how to resolve this error. I executed the code >>>>> to install boost already as provided in the instruction page. >>>>> >>>>> >>>>> _______________________________________________ >>>>> QuantLib-users mailing list >>>>> Qua...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/quantlib-users > > _______________________________________________ > QuantLib-users mailing list > Qua...@li... > https://lists.sourceforge.net/lists/listinfo/quantlib-users |
|
From: Luigi B. <lui...@gm...> - 2022-05-02 21:09:01
|
Can you look inside the generated config.log file and see what compiler error you're getting exactly? Luigi On Mon, May 2, 2022 at 7:49 PM Daniel Lobo <dan...@gm...> wrote: > Many thanks. > > I ran below codes to remove and reinstall boost > > sudo apt-get remove libboost-all-dev > sudo apt-get install libboost-all-dev > > boost installed in /usr/include > > :/usr/include$ ls > aio.h complex.h error.h features-time64.h getopt.h > langinfo.h math.h netdb.h numa.h > python3.10 setjmp.h string.h time.h video > aliases.h cpio.h evdns.h fenv.h glob.h > lastlog.h mcheck.h neteconet numaif.h rdma > sgtty.h strings.h tirpc wait.h > alloca.h crypt.h event2 finclude > gnu-versions.h libgen.h memory.h netinet obstack.h > re_comp.h shadow.h sudo_plugin.h ttyent.h wchar.h > argp.h ctype.h event.h fmtmsg.h grp.h > libintl.h misc netipx openvpn regex.h > signal.h syscall.h uchar.h wctype.h > argz.h dirent.h evhttp.h fnmatch.h gshadow.h > libltdl mntent.h netiucv paths.h regexp.h > sound sysexits.h ucontext.h wordexp.h > ar.h dlfcn.h evrpc.h fstab.h hwloc > libnl3 monetary.h netpacket poll.h resolv.h > spawn.h syslog.h ulimit.h X11 > arpa drm evutil.h fts.h hwloc.h > limits.h mqueue.h netrom printf.h rpc > stab.h tar.h unicode x86_64-linux-gnu > asm-generic elf.h execinfo.h ftw.h iconv.h > link.h mtd netrose proc_service.h rpcsvc > stdc-predef.h termio.h unistd.h xen > assert.h endian.h expat_external.h gcalc-2 ifaddrs.h > linux net nfs protocols sched.h > stdint.h termios.h utime.h xorg > boost > > But still get error when I run ./configure > > Below is the log that I get > > $ ./configure > checking for a BSD-compatible install... /usr/bin/install -c > checking whether build environment is sane... yes > checking for a race-free mkdir -p... /usr/bin/mkdir -p > checking for gawk... no > checking for mawk... mawk > checking whether make sets $(MAKE)... no > checking whether make supports nested variables... no > checking whether UID '1000' is supported by ustar format... yes > checking whether GID '1000' is supported by ustar format... yes > checking how to create a ustar tar archive... gnutar > checking for gawk... (cached) mawk > checking for gcc... gcc > checking whether the C compiler works... yes > checking for C compiler default output file name... a.out > checking for suffix of executables... > checking whether we are cross compiling... no > checking for suffix of object files... o > checking whether the compiler supports GNU C... yes > checking whether gcc accepts -g... yes > checking for gcc option to enable C11 features... none needed > checking whether gcc understands -c and -o together... yes > checking whether make supports the include directive... no > checking dependency style of gcc... none > checking for g++... no > checking for c++... no > checking for gpp... no > checking for aCC... no > checking for CC... no > checking for cxx... no > checking for cc++... no > checking for cl.exe... no > checking for FCC... no > checking for KCC... no > checking for RCC... no > checking for xlC_r... no > checking for xlC... no > checking for clang++... no > checking whether the compiler supports GNU C++... no > checking whether g++ accepts -g... no > checking for g++ option to enable C++11 features... none needed > checking dependency style of g++... none > checking how to run the C preprocessor... gcc -E > checking build system type... x86_64-pc-linux-gnu > checking host system type... x86_64-pc-linux-gnu > checking how to print strings... printf > checking for a sed that does not truncate output... /usr/bin/sed > checking for grep that handles long lines and -e... /usr/bin/grep > checking for egrep... /usr/bin/grep -E > checking for fgrep... /usr/bin/grep -F > checking for ld used by gcc... /usr/bin/ld > checking if the linker (/usr/bin/ld) is GNU ld... yes > checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B > checking the name lister (/usr/bin/nm -B) interface... BSD nm > checking whether ln -s works... yes > checking the maximum length of command line arguments... 1572864 > checking how to convert x86_64-pc-linux-gnu file names to > x86_64-pc-linux-gnu format... func_convert_file_noop > checking how to convert x86_64-pc-linux-gnu file names to toolchain > format... func_convert_file_noop > checking for /usr/bin/ld option to reload object files... -r > checking for objdump... objdump > checking how to recognize dependent libraries... pass_all > checking for dlltool... no > checking how to associate runtime and link libraries... printf %s\n > checking for ar... ar > checking for archiver @FILE support... @ > checking for strip... strip > checking for ranlib... ranlib > checking command to parse /usr/bin/nm -B output from gcc object... ok > checking for sysroot... no > checking for a working dd... /usr/bin/dd > checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1 > checking for mt... mt > checking if mt is a manifest tool... no > checking for stdio.h... yes > checking for stdlib.h... yes > checking for string.h... yes > checking for inttypes.h... yes > checking for stdint.h... yes > checking for strings.h... yes > checking for sys/stat.h... yes > checking for sys/types.h... yes > checking for unistd.h... yes > checking for dlfcn.h... yes > checking for objdir... .libs > checking if gcc supports -fno-rtti -fno-exceptions... no > checking for gcc option to produce PIC... -fPIC -DPIC > checking if gcc PIC flag -fPIC -DPIC works... yes > checking if gcc static flag -static works... yes > checking if gcc supports -c -o file.o... yes > checking if gcc supports -c -o file.o... (cached) yes > checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports > shared libraries... yes > checking whether -lc should be explicitly linked in... no > checking dynamic linker characteristics... GNU/Linux ld.so > checking how to hardcode library paths into programs... immediate > checking whether stripping libraries is possible... yes > checking if libtool supports shared libraries... yes > checking whether to build shared libraries... yes > checking whether to build static libraries... yes > checking for C++11 support... no: adding -std=c++11 to CXXFLAGS > checking for Boost development files... no > configure: error: Boost development files not found > > > Any pointer how to resolve this will be very helpful. > > Thanks > > On Sun, 1 May 2022 at 13:16, Jonathan Sweemer <sw...@gm...> wrote: > > > > Hi Daniel, > > > > Just to confirm, you’re no longer running ./configure with the > —with-boost-include and —with-boost-lib flags right? > > > > If so then I would expect the configure script to find your boost > installation. Please check that you see boost headers in /usr/include/boost > and if not, try reinstalling boost. > > > > If you’re still unable to get ./configure to find boost then please > attach the full output including all the commands that you ran. > > > > Jonathan > > > > > > 2022년 5월 1일 (일) 15:41, Daniel Lobo <dan...@gm...>님이 작성: > >> > >> Hi, > >> > >> Many thanks for your response. > >> > >> Yes I ran 'sudo apt-get install libboost-all-dev' to install boost. > >> However still I get this error. > >> > >> How can I find where the boost is installed and how can I pass that > >> information './configure ' line? > >> > >> Apologies for trivial question if any, as I am not very expert in > >> Linux ecosystem. > >> > >> Thanks and regards, > >> > >> On Sun, 1 May 2022 at 11:53, Jonathan Sweemer <sw...@gm...> > wrote: > >> > > >> > Hi Daniel, > >> > > >> > When you say that you “install[ed] boost already as provided in the > instruction page” do you mean that you ran the following command? > >> > > >> > sudo apt-get install libboost-all-dev > >> > > >> > If so then you shouldn’t need to use the —with-boost-include and > —with-boost-lib flags when configuring QuantLib. As the install guide > mentions, you only need those flags when you install boost in a > non-standard location. > >> > > >> > Jonathan > >> > > >> > > >> > 2022년 5월 1일 (일) 02:25, Daniel Lobo <dan...@gm...>님이 작성: > >> >> > >> >> Hi, > >> >> > >> >> I am trying to install Quantlib in my Ubuntu VM. I was following the > >> >> instructions as provided in > >> >> https://www.quantlib.org/install/linux.shtml > >> >> > >> >> But this installation failed when I executed > >> >> > >> >> ./configure --with-boost-include=/home/foo/include > >> >> --with-boost-lib=/home/foo/lib > >> >> > >> >> > >> >> > >> >> The error I got is > >> >> > >> >> $ ./configure --with-boost-include=/home/foo/include > >> >> --with-boost-lib=/home/foo/lib > >> >> checking for a BSD-compatible install... /usr/bin/install -c > >> >> checking whether build environment is sane... yes > >> >> checking for a race-free mkdir -p... /usr/bin/mkdir -p > >> >> checking for gawk... no > >> >> checking for mawk... mawk > >> >> checking whether make sets $(MAKE)... no > >> >> checking whether make supports nested variables... no > >> >> checking whether UID '1000' is supported by ustar format... yes > >> >> checking whether GID '1000' is supported by ustar format... yes > >> >> checking how to create a ustar tar archive... gnutar > >> >> checking for gawk... (cached) mawk > >> >> checking for gcc... gcc > >> >> checking whether the C compiler works... yes > >> >> checking for C compiler default output file name... a.out > >> >> checking for suffix of executables... > >> >> checking whether we are cross compiling... no > >> >> checking for suffix of object files... o > >> >> checking whether the compiler supports GNU C... yes > >> >> checking whether gcc accepts -g... yes > >> >> checking for gcc option to enable C11 features... none needed > >> >> checking whether gcc understands -c and -o together... yes > >> >> checking whether make supports the include directive... no > >> >> checking dependency style of gcc... none > >> >> checking for g++... no > >> >> checking for c++... no > >> >> checking for gpp... no > >> >> checking for aCC... no > >> >> checking for CC... no > >> >> checking for cxx... no > >> >> checking for cc++... no > >> >> checking for cl.exe... no > >> >> checking for FCC... no > >> >> checking for KCC... no > >> >> checking for RCC... no > >> >> checking for xlC_r... no > >> >> checking for xlC... no > >> >> checking for clang++... no > >> >> checking whether the compiler supports GNU C++... no > >> >> checking whether g++ accepts -g... no > >> >> checking for g++ option to enable C++11 features... none needed > >> >> checking dependency style of g++... none > >> >> checking how to run the C preprocessor... gcc -E > >> >> checking build system type... x86_64-pc-linux-gnu > >> >> checking host system type... x86_64-pc-linux-gnu > >> >> checking how to print strings... printf > >> >> checking for a sed that does not truncate output... /usr/bin/sed > >> >> checking for grep that handles long lines and -e... /usr/bin/grep > >> >> checking for egrep... /usr/bin/grep -E > >> >> checking for fgrep... /usr/bin/grep -F > >> >> checking for ld used by gcc... /usr/bin/ld > >> >> checking if the linker (/usr/bin/ld) is GNU ld... yes > >> >> checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B > >> >> checking the name lister (/usr/bin/nm -B) interface... BSD nm > >> >> checking whether ln -s works... yes > >> >> checking the maximum length of command line arguments... 1572864 > >> >> checking how to convert x86_64-pc-linux-gnu file names to > >> >> x86_64-pc-linux-gnu format... func_convert_file_noop > >> >> checking how to convert x86_64-pc-linux-gnu file names to toolchain > >> >> format... func_convert_file_noop > >> >> checking for /usr/bin/ld option to reload object files... -r > >> >> checking for objdump... objdump > >> >> checking how to recognize dependent libraries... pass_all > >> >> checking for dlltool... no > >> >> checking how to associate runtime and link libraries... printf %s\n > >> >> checking for ar... ar > >> >> checking for archiver @FILE support... @ > >> >> checking for strip... strip > >> >> checking for ranlib... ranlib > >> >> checking command to parse /usr/bin/nm -B output from gcc object... ok > >> >> checking for sysroot... no > >> >> checking for a working dd... /usr/bin/dd > >> >> checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1 > >> >> checking for mt... mt > >> >> checking if mt is a manifest tool... no > >> >> checking for stdio.h... yes > >> >> checking for stdlib.h... yes > >> >> checking for string.h... yes > >> >> checking for inttypes.h... yes > >> >> checking for stdint.h... yes > >> >> checking for strings.h... yes > >> >> checking for sys/stat.h... yes > >> >> checking for sys/types.h... yes > >> >> checking for unistd.h... yes > >> >> checking for dlfcn.h... yes > >> >> checking for objdir... .libs > >> >> checking if gcc supports -fno-rtti -fno-exceptions... no > >> >> checking for gcc option to produce PIC... -fPIC -DPIC > >> >> checking if gcc PIC flag -fPIC -DPIC works... yes > >> >> checking if gcc static flag -static works... yes > >> >> checking if gcc supports -c -o file.o... yes > >> >> checking if gcc supports -c -o file.o... (cached) yes > >> >> checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports > >> >> shared libraries... yes > >> >> checking whether -lc should be explicitly linked in... no > >> >> checking dynamic linker characteristics... GNU/Linux ld.so > >> >> checking how to hardcode library paths into programs... immediate > >> >> checking whether stripping libraries is possible... yes > >> >> checking if libtool supports shared libraries... yes > >> >> checking whether to build shared libraries... yes > >> >> checking whether to build static libraries... yes > >> >> checking for C++11 support... no: adding -std=c++11 to CXXFLAGS > >> >> checking for Boost development files... no > >> >> configure: error: Boost development files not found > >> >> > >> >> Could you please help how to resolve this error. I executed the code > >> >> to install boost already as provided in the instruction page. > >> >> > >> >> > >> >> _______________________________________________ > >> >> QuantLib-users mailing list > >> >> Qua...@li... > >> >> https://lists.sourceforge.net/lists/listinfo/quantlib-users > > > _______________________________________________ > QuantLib-users mailing list > Qua...@li... > https://lists.sourceforge.net/lists/listinfo/quantlib-users > |
|
From: Daniel L. <dan...@gm...> - 2022-05-02 17:45:08
|
Many thanks.
I ran below codes to remove and reinstall boost
sudo apt-get remove libboost-all-dev
sudo apt-get install libboost-all-dev
boost installed in /usr/include
:/usr/include$ ls
aio.h complex.h error.h features-time64.h getopt.h
langinfo.h math.h netdb.h numa.h
python3.10 setjmp.h string.h time.h video
aliases.h cpio.h evdns.h fenv.h glob.h
lastlog.h mcheck.h neteconet numaif.h rdma
sgtty.h strings.h tirpc wait.h
alloca.h crypt.h event2 finclude
gnu-versions.h libgen.h memory.h netinet obstack.h
re_comp.h shadow.h sudo_plugin.h ttyent.h wchar.h
argp.h ctype.h event.h fmtmsg.h grp.h
libintl.h misc netipx openvpn regex.h
signal.h syscall.h uchar.h wctype.h
argz.h dirent.h evhttp.h fnmatch.h gshadow.h
libltdl mntent.h netiucv paths.h regexp.h
sound sysexits.h ucontext.h wordexp.h
ar.h dlfcn.h evrpc.h fstab.h hwloc
libnl3 monetary.h netpacket poll.h resolv.h
spawn.h syslog.h ulimit.h X11
arpa drm evutil.h fts.h hwloc.h
limits.h mqueue.h netrom printf.h rpc
stab.h tar.h unicode x86_64-linux-gnu
asm-generic elf.h execinfo.h ftw.h iconv.h
link.h mtd netrose proc_service.h rpcsvc
stdc-predef.h termio.h unistd.h xen
assert.h endian.h expat_external.h gcalc-2 ifaddrs.h
linux net nfs protocols sched.h
stdint.h termios.h utime.h xorg
boost
But still get error when I run ./configure
Below is the log that I get
$ ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a race-free mkdir -p... /usr/bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... no
checking whether make supports nested variables... no
checking whether UID '1000' is supported by ustar format... yes
checking whether GID '1000' is supported by ustar format... yes
checking how to create a ustar tar archive... gnutar
checking for gawk... (cached) mawk
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether gcc accepts -g... yes
checking for gcc option to enable C11 features... none needed
checking whether gcc understands -c and -o together... yes
checking whether make supports the include directive... no
checking dependency style of gcc... none
checking for g++... no
checking for c++... no
checking for gpp... no
checking for aCC... no
checking for CC... no
checking for cxx... no
checking for cc++... no
checking for cl.exe... no
checking for FCC... no
checking for KCC... no
checking for RCC... no
checking for xlC_r... no
checking for xlC... no
checking for clang++... no
checking whether the compiler supports GNU C++... no
checking whether g++ accepts -g... no
checking for g++ option to enable C++11 features... none needed
checking dependency style of g++... none
checking how to run the C preprocessor... gcc -E
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking how to print strings... printf
checking for a sed that does not truncate output... /usr/bin/sed
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for fgrep... /usr/bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking how to convert x86_64-pc-linux-gnu file names to
x86_64-pc-linux-gnu format... func_convert_file_noop
checking how to convert x86_64-pc-linux-gnu file names to toolchain
format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for a working dd... /usr/bin/dd
checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1
checking for mt... mt
checking if mt is a manifest tool... no
checking for stdio.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports
shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for C++11 support... no: adding -std=c++11 to CXXFLAGS
checking for Boost development files... no
configure: error: Boost development files not found
Any pointer how to resolve this will be very helpful.
Thanks
On Sun, 1 May 2022 at 13:16, Jonathan Sweemer <sw...@gm...> wrote:
>
> Hi Daniel,
>
> Just to confirm, you’re no longer running ./configure with the —with-boost-include and —with-boost-lib flags right?
>
> If so then I would expect the configure script to find your boost installation. Please check that you see boost headers in /usr/include/boost and if not, try reinstalling boost.
>
> If you’re still unable to get ./configure to find boost then please attach the full output including all the commands that you ran.
>
> Jonathan
>
>
> 2022년 5월 1일 (일) 15:41, Daniel Lobo <dan...@gm...>님이 작성:
>>
>> Hi,
>>
>> Many thanks for your response.
>>
>> Yes I ran 'sudo apt-get install libboost-all-dev' to install boost.
>> However still I get this error.
>>
>> How can I find where the boost is installed and how can I pass that
>> information './configure ' line?
>>
>> Apologies for trivial question if any, as I am not very expert in
>> Linux ecosystem.
>>
>> Thanks and regards,
>>
>> On Sun, 1 May 2022 at 11:53, Jonathan Sweemer <sw...@gm...> wrote:
>> >
>> > Hi Daniel,
>> >
>> > When you say that you “install[ed] boost already as provided in the instruction page” do you mean that you ran the following command?
>> >
>> > sudo apt-get install libboost-all-dev
>> >
>> > If so then you shouldn’t need to use the —with-boost-include and —with-boost-lib flags when configuring QuantLib. As the install guide mentions, you only need those flags when you install boost in a non-standard location.
>> >
>> > Jonathan
>> >
>> >
>> > 2022년 5월 1일 (일) 02:25, Daniel Lobo <dan...@gm...>님이 작성:
>> >>
>> >> Hi,
>> >>
>> >> I am trying to install Quantlib in my Ubuntu VM. I was following the
>> >> instructions as provided in
>> >> https://www.quantlib.org/install/linux.shtml
>> >>
>> >> But this installation failed when I executed
>> >>
>> >> ./configure --with-boost-include=/home/foo/include
>> >> --with-boost-lib=/home/foo/lib
>> >>
>> >>
>> >>
>> >> The error I got is
>> >>
>> >> $ ./configure --with-boost-include=/home/foo/include
>> >> --with-boost-lib=/home/foo/lib
>> >> checking for a BSD-compatible install... /usr/bin/install -c
>> >> checking whether build environment is sane... yes
>> >> checking for a race-free mkdir -p... /usr/bin/mkdir -p
>> >> checking for gawk... no
>> >> checking for mawk... mawk
>> >> checking whether make sets $(MAKE)... no
>> >> checking whether make supports nested variables... no
>> >> checking whether UID '1000' is supported by ustar format... yes
>> >> checking whether GID '1000' is supported by ustar format... yes
>> >> checking how to create a ustar tar archive... gnutar
>> >> checking for gawk... (cached) mawk
>> >> checking for gcc... gcc
>> >> checking whether the C compiler works... yes
>> >> checking for C compiler default output file name... a.out
>> >> checking for suffix of executables...
>> >> checking whether we are cross compiling... no
>> >> checking for suffix of object files... o
>> >> checking whether the compiler supports GNU C... yes
>> >> checking whether gcc accepts -g... yes
>> >> checking for gcc option to enable C11 features... none needed
>> >> checking whether gcc understands -c and -o together... yes
>> >> checking whether make supports the include directive... no
>> >> checking dependency style of gcc... none
>> >> checking for g++... no
>> >> checking for c++... no
>> >> checking for gpp... no
>> >> checking for aCC... no
>> >> checking for CC... no
>> >> checking for cxx... no
>> >> checking for cc++... no
>> >> checking for cl.exe... no
>> >> checking for FCC... no
>> >> checking for KCC... no
>> >> checking for RCC... no
>> >> checking for xlC_r... no
>> >> checking for xlC... no
>> >> checking for clang++... no
>> >> checking whether the compiler supports GNU C++... no
>> >> checking whether g++ accepts -g... no
>> >> checking for g++ option to enable C++11 features... none needed
>> >> checking dependency style of g++... none
>> >> checking how to run the C preprocessor... gcc -E
>> >> checking build system type... x86_64-pc-linux-gnu
>> >> checking host system type... x86_64-pc-linux-gnu
>> >> checking how to print strings... printf
>> >> checking for a sed that does not truncate output... /usr/bin/sed
>> >> checking for grep that handles long lines and -e... /usr/bin/grep
>> >> checking for egrep... /usr/bin/grep -E
>> >> checking for fgrep... /usr/bin/grep -F
>> >> checking for ld used by gcc... /usr/bin/ld
>> >> checking if the linker (/usr/bin/ld) is GNU ld... yes
>> >> checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
>> >> checking the name lister (/usr/bin/nm -B) interface... BSD nm
>> >> checking whether ln -s works... yes
>> >> checking the maximum length of command line arguments... 1572864
>> >> checking how to convert x86_64-pc-linux-gnu file names to
>> >> x86_64-pc-linux-gnu format... func_convert_file_noop
>> >> checking how to convert x86_64-pc-linux-gnu file names to toolchain
>> >> format... func_convert_file_noop
>> >> checking for /usr/bin/ld option to reload object files... -r
>> >> checking for objdump... objdump
>> >> checking how to recognize dependent libraries... pass_all
>> >> checking for dlltool... no
>> >> checking how to associate runtime and link libraries... printf %s\n
>> >> checking for ar... ar
>> >> checking for archiver @FILE support... @
>> >> checking for strip... strip
>> >> checking for ranlib... ranlib
>> >> checking command to parse /usr/bin/nm -B output from gcc object... ok
>> >> checking for sysroot... no
>> >> checking for a working dd... /usr/bin/dd
>> >> checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1
>> >> checking for mt... mt
>> >> checking if mt is a manifest tool... no
>> >> checking for stdio.h... yes
>> >> checking for stdlib.h... yes
>> >> checking for string.h... yes
>> >> checking for inttypes.h... yes
>> >> checking for stdint.h... yes
>> >> checking for strings.h... yes
>> >> checking for sys/stat.h... yes
>> >> checking for sys/types.h... yes
>> >> checking for unistd.h... yes
>> >> checking for dlfcn.h... yes
>> >> checking for objdir... .libs
>> >> checking if gcc supports -fno-rtti -fno-exceptions... no
>> >> checking for gcc option to produce PIC... -fPIC -DPIC
>> >> checking if gcc PIC flag -fPIC -DPIC works... yes
>> >> checking if gcc static flag -static works... yes
>> >> checking if gcc supports -c -o file.o... yes
>> >> checking if gcc supports -c -o file.o... (cached) yes
>> >> checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports
>> >> shared libraries... yes
>> >> checking whether -lc should be explicitly linked in... no
>> >> checking dynamic linker characteristics... GNU/Linux ld.so
>> >> checking how to hardcode library paths into programs... immediate
>> >> checking whether stripping libraries is possible... yes
>> >> checking if libtool supports shared libraries... yes
>> >> checking whether to build shared libraries... yes
>> >> checking whether to build static libraries... yes
>> >> checking for C++11 support... no: adding -std=c++11 to CXXFLAGS
>> >> checking for Boost development files... no
>> >> configure: error: Boost development files not found
>> >>
>> >> Could you please help how to resolve this error. I executed the code
>> >> to install boost already as provided in the instruction page.
>> >>
>> >>
>> >> _______________________________________________
>> >> QuantLib-users mailing list
>> >> Qua...@li...
>> >> https://lists.sourceforge.net/lists/listinfo/quantlib-users
|
|
From: Jonathan S. <sw...@gm...> - 2022-05-02 12:33:45
|
Hi Chirag, Did you follow the instructions in the CMake output and 'Add the installation prefix of "QuantLib" to CMAKE_PREFIX_PATH or set "QuantLib_DIR" to a directory containing one of the above files'? If C:/local/QuantLib-1.24/cmake-build-debug-visualstudio2017 is your CMake build directory, then the 'above files' will be found in the cmake directory under that build directory. If that doesn't work then the best I can do is point you to the documentation on CMake config mode[1] and wish you luck, as I won't be able to offer much further help remotely. By the way, the quantlib-vcpkg-example repo that you found is an example of how to link your project to QuantLib installed through vcpkg, which you haven't used. If you'd like to, you can try out vcpkg, and it may make your life easier in the long run, but be aware that it has a learning curve of its own to grapple with first. [1] https://cmake.org/cmake/help/latest/command/find_package.html#config-mode-search-procedure Jonathan On Mon, May 2, 2022 at 1:43 PM <chi...@ya...> wrote: > Hi Jonathan – thank you for your kind advice. I finally managed to build > Quantlib in CLion and the lib file is found as below. All the Examples > folder also works fine. > > > > > > > > 1. I am creating a project outside root Quantlib folder & don’t have a > problem finding the Boost files as I have used several Boost projects > before which work fine. I cannot seem to find and link the Quantlib > library. ( I created a new project called TestQLCLion). Can you please > advise how to modify the CMake file below please ? I tried several times > but keep failing. > > > > > > cmake_minimum_required(VERSION 3.20) > project(TestQLCLion) > set(CMAKE_CXX_STANDARD 14) > set(BOOST_ROOT "C:/local/boost_1_65_0") > set(Boost_INCLUDE_DIR "C:/local/boost_1_65_0" ) > set(Boost_LIBRARY_DIR "C:/local/boost_1_65_0/lib32-msvc-14.1" ) > find_package(Boost 1.65.0 REQUIRED) > > > > *#include_directories(C:/local/QuantLib-1.24/cmake-build-debug-visualstudio2017/ql)* > include_directories(C:/local/QuantLib-1.24/) > find_package(QuantLib CONFIG REQUIRED) > > add_executable(TestQLCLion main.cpp) > target_include_directories(TestQLCLion PRIVATE ${Boost_INCLUDE_DIRS}) > target_link_libraries(TestQLCLion PRIVATE ${Boost_LIBRARIES}) > target_link_libraries(TestQLCLion PRIVATE QuantLib::QuantLib) > > > > > > Thank you for your kind assistance. > > > > > > I also tried another one of your gists to link to the library directly but > fails > > > https://github.com/sweemer/quantlib-vcpkg-example/blob/025760be5befe150274ce7369066d581ffb50cf5/CMakeLists.txt > > > > *From:* Jonathan Sweemer <sw...@gm...> > *Sent:* Thursday, January 20, 2022 8:44 PM > *To:* Chirag Desai <chi...@ya...> > *Cc:* QuantLib users <qua...@li...> > *Subject:* Re: [Quantlib-users] Quantlib in CLion > > > > I took a quick look at your CMakeLists.txt file and fixed it up here: > https://gist.github.com/sweemer/dff4b0294eff698a3d670811549d3c35 > > > > For my gist to work you'll need to download the latest version 1.25 of > QuantLib. The gist may not work perfectly but it should be a good starting > point. > > > > You will want to spend some time to review the CMake documentation[1] for > how to set the include and link properties for your project as there are > many more details that cannot be covered here. > > > > As far as CLion is concerned, I'm not sure how to get it working, but > based on the blog link that you shared, the first step seems to be to tell > CMake to configure your build with the correct compiler[2]. > > > > [1] https://cmake.org/cmake/help/latest/module/FindBoost.html#examples > > [2] https://cmake.org/cmake/help/latest/variable/CMAKE_LANG_COMPILER.html > > > > > > On Thu, Jan 20, 2022 at 1:33 PM <chi...@ya...> wrote: > > Hi Jonathan > > > > Thank you for your kind advice. I already have inserted the macros below. > Based on Luigi’s reply, it seems the Boost headers alone are sufficient (if > I am not building the test-libraries) and that’s works fine for me in CLion > as well. So now my focus is to build Quantlib using mingw in CLion. > > > > Can you please recommend how I can modify the existing CMake file to build > Quantlib using CMake ? > > > > i) Do I modify the existing CMakeLists.txt file that comes > with Quantlib with recommendations from Dimitri’s blog ? Or write a new > CMake file ? > > > > https://blog.jetbrains.com/clion/2015/12/quantlib-clion/ > > > > > > > > Option 2: (since everything works fine in Visual Studio, I thought of > trying my luck) > > > > I switched the compiler itself in CLion from my default mingw to Visual > Studio 2017. I then modified the CMakeLists.txt file(which is attached in > this email) but it doesn’t work > > as in the main.cpp the #include <ql/quantlib.hpp> can’t find it > > > > fatal error C1083: Cannot open include file: 'ql/quantlib.hpp': No such > file or directory > > NMAKE : fatal error U1077: > 'C:\PROGRA~2\MIB055~1\2017\COMMUN~1\VC\Tools\MSVC\1416~1.270\bin\Hostx86\x86\cl.exe' > : return code '0x2' > > Stop. > > NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual > Studio\2017\Community\VC\Tools\MSVC\14.16.27023\bin\HostX86\x86\nmake.exe"' > : return code '0x2' > > Stop > > > > Thank you for your kind help > > > > > > > > *From:* Jonathan Sweemer <sw...@gm...> > *Sent:* Wednesday, January 19, 2022 8:34 PM > *To:* Chirag Desai <chi...@ya...> > *Cc:* qua...@li... > *Subject:* Re: [Quantlib-users] Quantlib in CLion > > > > Hi Chirag, > > > > The first step is to successfully build Boost using a toolchain compatible > with CLion. I have never done this before but the StackOverflow link you > pasted seems to provide reasonable instructions. > > > > Once you have built Boost, then you can use the BOOST_INCLUDEDIR, > BOOST_LIBRARY_DIR, and/or BOOST_ROOT variables to tell CMake where to > find the Boost installation when configuring QuantLib. See [1] for more > details on these variables. > > > > Regarding whether a header-only Boost installation is sufficient, > unfortunately no, QuantLib still depends on some pre-compiled Boost > libraries, but this may change in the future. See [2] for the latest list > of Boost library dependencies. > > > > [1] https://cmake.org/cmake/help/latest/module/FindBoost.html > > [2] https://github.com/lballabio/QuantLib/blob/master/CMakeLists.txt#L118 > > > > > > > > On Wed, Jan 19, 2022 at 8:16 PM Chirag Desai via QuantLib-users < > qua...@li...> wrote: > > Hi Quantlib Users > > > > Hope all is well. I am trying to get more involved in the Quantlib project > with my interest in quantitative finance. > > > > I have been able to get it to work in Windows VS2017 but I am trying to > make it work in CLion using CMake with no success. > > > > 1) I can't even get Boost to compile in CLion using CMake. I am only able > to use the header only Boost files in CLion > > > > https://stackoverflow.com/questions/36519453/setup-boost-in-clion > > > > 2) I tried following this blog by Dimitry but I guess I first need to make > Boost work (or are the header only Boost files sufficient ?). The > instructions are not very clear. > > > > https://blog.jetbrains.com/clion/2015/12/quantlib-clion/ > > > > May I kindly check if this is something somebody can guide me on please ? > > > > Thank you for your guidance > > Chirag > > > > _______________________________________________ > QuantLib-users mailing list > Qua...@li... > https://lists.sourceforge.net/lists/listinfo/quantlib-users > > |
|
From: <chi...@ya...> - 2022-05-02 04:43:17
|
Hi Jonathan – thank you for your kind advice. I finally managed to build Quantlib in CLion and the lib file is found as below. All the Examples folder also works fine.
1. I am creating a project outside root Quantlib folder & don’t have a problem finding the Boost files as I have used several Boost projects before which work fine. I cannot seem to find and link the Quantlib library. ( I created a new project called TestQLCLion). Can you please advise how to modify the CMake file below please ? I tried several times but keep failing.
cmake_minimum_required(VERSION 3.20)
project(TestQLCLion)
set(CMAKE_CXX_STANDARD 14)
set(BOOST_ROOT "C:/local/boost_1_65_0")
set(Boost_INCLUDE_DIR "C:/local/boost_1_65_0" )
set(Boost_LIBRARY_DIR "C:/local/boost_1_65_0/lib32-msvc-14.1" )
find_package(Boost 1.65.0 REQUIRED)
#include_directories(C:/local/QuantLib-1.24/cmake-build-debug-visualstudio2017/ql)
include_directories(C:/local/QuantLib-1.24/)
find_package(QuantLib CONFIG REQUIRED)
add_executable(TestQLCLion main.cpp)
target_include_directories(TestQLCLion PRIVATE ${Boost_INCLUDE_DIRS})
target_link_libraries(TestQLCLion PRIVATE ${Boost_LIBRARIES})
target_link_libraries(TestQLCLion PRIVATE QuantLib::QuantLib)
Thank you for your kind assistance.
I also tried another one of your gists to link to the library directly but fails
https://github.com/sweemer/quantlib-vcpkg-example/blob/025760be5befe150274ce7369066d581ffb50cf5/CMakeLists.txt
From: Jonathan Sweemer <sw...@gm...>
Sent: Thursday, January 20, 2022 8:44 PM
To: Chirag Desai <chi...@ya...>
Cc: QuantLib users <qua...@li...>
Subject: Re: [Quantlib-users] Quantlib in CLion
I took a quick look at your CMakeLists.txt file and fixed it up here: https://gist.github.com/sweemer/dff4b0294eff698a3d670811549d3c35
For my gist to work you'll need to download the latest version 1.25 of QuantLib. The gist may not work perfectly but it should be a good starting point.
You will want to spend some time to review the CMake documentation[1] for how to set the include and link properties for your project as there are many more details that cannot be covered here.
As far as CLion is concerned, I'm not sure how to get it working, but based on the blog link that you shared, the first step seems to be to tell CMake to configure your build with the correct compiler[2].
[1] https://cmake.org/cmake/help/latest/module/FindBoost.html#examples
[2] https://cmake.org/cmake/help/latest/variable/CMAKE_LANG_COMPILER.html
On Thu, Jan 20, 2022 at 1:33 PM <chi...@ya... <mailto:chi...@ya...> > wrote:
Hi Jonathan
Thank you for your kind advice. I already have inserted the macros below. Based on Luigi’s reply, it seems the Boost headers alone are sufficient (if I am not building the test-libraries) and that’s works fine for me in CLion as well. So now my focus is to build Quantlib using mingw in CLion.
Can you please recommend how I can modify the existing CMake file to build Quantlib using CMake ?
i) Do I modify the existing CMakeLists.txt file that comes with Quantlib with recommendations from Dimitri’s blog ? Or write a new CMake file ?
<https://blog.jetbrains.com/clion/2015/12/quantlib-clion/> https://blog.jetbrains.com/clion/2015/12/quantlib-clion/
Option 2: (since everything works fine in Visual Studio, I thought of trying my luck)
I switched the compiler itself in CLion from my default mingw to Visual Studio 2017. I then modified the CMakeLists.txt file(which is attached in this email) but it doesn’t work
as in the main.cpp the #include <ql/quantlib.hpp> can’t find it
fatal error C1083: Cannot open include file: 'ql/quantlib.hpp': No such file or directory
NMAKE : fatal error U1077: 'C:\PROGRA~2\MIB055~1\2017\COMMUN~1\VC\Tools\MSVC\1416~1.270\bin\Hostx86\x86\cl.exe' : return code '0x2'
Stop.
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.16.27023\bin\HostX86\x86\nmake.exe"' : return code '0x2'
Stop
Thank you for your kind help
From: Jonathan Sweemer <sw...@gm... <mailto:sw...@gm...> >
Sent: Wednesday, January 19, 2022 8:34 PM
To: Chirag Desai <chi...@ya... <mailto:chi...@ya...> >
Cc: qua...@li... <mailto:qua...@li...>
Subject: Re: [Quantlib-users] Quantlib in CLion
Hi Chirag,
The first step is to successfully build Boost using a toolchain compatible with CLion. I have never done this before but the StackOverflow link you pasted seems to provide reasonable instructions.
Once you have built Boost, then you can use the BOOST_INCLUDEDIR, BOOST_LIBRARY_DIR, and/or BOOST_ROOT variables to tell CMake where to find the Boost installation when configuring QuantLib. See [1] for more details on these variables.
Regarding whether a header-only Boost installation is sufficient, unfortunately no, QuantLib still depends on some pre-compiled Boost libraries, but this may change in the future. See [2] for the latest list of Boost library dependencies.
[1] https://cmake.org/cmake/help/latest/module/FindBoost.html
[2] https://github.com/lballabio/QuantLib/blob/master/CMakeLists.txt#L118
On Wed, Jan 19, 2022 at 8:16 PM Chirag Desai via QuantLib-users <qua...@li... <mailto:qua...@li...> > wrote:
Hi Quantlib Users
Hope all is well. I am trying to get more involved in the Quantlib project with my interest in quantitative finance.
I have been able to get it to work in Windows VS2017 but I am trying to make it work in CLion using CMake with no success.
1) I can't even get Boost to compile in CLion using CMake. I am only able to use the header only Boost files in CLion
https://stackoverflow.com/questions/36519453/setup-boost-in-clion
2) I tried following this blog by Dimitry but I guess I first need to make Boost work (or are the header only Boost files sufficient ?). The instructions are not very clear.
<https://blog.jetbrains.com/clion/2015/12/quantlib-clion/> https://blog.jetbrains.com/clion/2015/12/quantlib-clion/
May I kindly check if this is something somebody can guide me on please ?
Thank you for your guidance
Chirag
_______________________________________________
QuantLib-users mailing list
Qua...@li... <mailto:Qua...@li...>
https://lists.sourceforge.net/lists/listinfo/quantlib-users
|
|
From: Aleksis A. R. <ale...@go...> - 2022-05-01 12:05:17
|
Thanks Jacek - indeed for the binary case (using AssetOrNothing and adjusting the NPV by spot) appears to work. Less clear if this will also work for touch options but will give it a go. > On Apr 30, 2022, at 2:52 PM, Jacek Bator <jac...@gm...> wrote: > > Hi Aleksis. > Try using AssetOrNothingPayoff class. > > > sob., 30 kwi 2022, 15:32 użytkownik Aleksis Ali Raza via QuantLib-users <qua...@li... <mailto:qua...@li...>> napisał: > Hi, when evaluating a binary payoff (using CashOrNothingPayoff) for a currency pair CCY1/CCY2 (eg. USD/JPY), the payout currency is CCY2 by default (so JPY in the example). Other than inverting the pair (which is very awkward), is there any way to switch the payout to be in CCY1 (i.e. USD) instead, as is conventional? > > Thanks, Aleksis > > _______________________________________________ > QuantLib-users mailing list > Qua...@li... <mailto:Qua...@li...> > https://lists.sourceforge.net/lists/listinfo/quantlib-users <https://lists.sourceforge.net/lists/listinfo/quantlib-users> |
|
From: Jonathan S. <sw...@gm...> - 2022-05-01 07:46:53
|
Hi Daniel, Just to confirm, you’re no longer running ./configure with the —with-boost-include and —with-boost-lib flags right? If so then I would expect the configure script to find your boost installation. Please check that you see boost headers in /usr/include/boost and if not, try reinstalling boost. If you’re still unable to get ./configure to find boost then please attach the full output including all the commands that you ran. Jonathan 2022년 5월 1일 (일) 15:41, Daniel Lobo <dan...@gm...>님이 작성: > Hi, > > Many thanks for your response. > > Yes I ran 'sudo apt-get install libboost-all-dev' to install boost. > However still I get this error. > > How can I find where the boost is installed and how can I pass that > information './configure ' line? > > Apologies for trivial question if any, as I am not very expert in > Linux ecosystem. > > Thanks and regards, > > On Sun, 1 May 2022 at 11:53, Jonathan Sweemer <sw...@gm...> wrote: > > > > Hi Daniel, > > > > When you say that you “install[ed] boost already as provided in the > instruction page” do you mean that you ran the following command? > > > > sudo apt-get install libboost-all-dev > > > > If so then you shouldn’t need to use the —with-boost-include and > —with-boost-lib flags when configuring QuantLib. As the install guide > mentions, you only need those flags when you install boost in a > non-standard location. > > > > Jonathan > > > > > > 2022년 5월 1일 (일) 02:25, Daniel Lobo <dan...@gm...>님이 작성: > >> > >> Hi, > >> > >> I am trying to install Quantlib in my Ubuntu VM. I was following the > >> instructions as provided in > >> https://www.quantlib.org/install/linux.shtml > >> > >> But this installation failed when I executed > >> > >> ./configure --with-boost-include=/home/foo/include > >> --with-boost-lib=/home/foo/lib > >> > >> > >> > >> The error I got is > >> > >> $ ./configure --with-boost-include=/home/foo/include > >> --with-boost-lib=/home/foo/lib > >> checking for a BSD-compatible install... /usr/bin/install -c > >> checking whether build environment is sane... yes > >> checking for a race-free mkdir -p... /usr/bin/mkdir -p > >> checking for gawk... no > >> checking for mawk... mawk > >> checking whether make sets $(MAKE)... no > >> checking whether make supports nested variables... no > >> checking whether UID '1000' is supported by ustar format... yes > >> checking whether GID '1000' is supported by ustar format... yes > >> checking how to create a ustar tar archive... gnutar > >> checking for gawk... (cached) mawk > >> checking for gcc... gcc > >> checking whether the C compiler works... yes > >> checking for C compiler default output file name... a.out > >> checking for suffix of executables... > >> checking whether we are cross compiling... no > >> checking for suffix of object files... o > >> checking whether the compiler supports GNU C... yes > >> checking whether gcc accepts -g... yes > >> checking for gcc option to enable C11 features... none needed > >> checking whether gcc understands -c and -o together... yes > >> checking whether make supports the include directive... no > >> checking dependency style of gcc... none > >> checking for g++... no > >> checking for c++... no > >> checking for gpp... no > >> checking for aCC... no > >> checking for CC... no > >> checking for cxx... no > >> checking for cc++... no > >> checking for cl.exe... no > >> checking for FCC... no > >> checking for KCC... no > >> checking for RCC... no > >> checking for xlC_r... no > >> checking for xlC... no > >> checking for clang++... no > >> checking whether the compiler supports GNU C++... no > >> checking whether g++ accepts -g... no > >> checking for g++ option to enable C++11 features... none needed > >> checking dependency style of g++... none > >> checking how to run the C preprocessor... gcc -E > >> checking build system type... x86_64-pc-linux-gnu > >> checking host system type... x86_64-pc-linux-gnu > >> checking how to print strings... printf > >> checking for a sed that does not truncate output... /usr/bin/sed > >> checking for grep that handles long lines and -e... /usr/bin/grep > >> checking for egrep... /usr/bin/grep -E > >> checking for fgrep... /usr/bin/grep -F > >> checking for ld used by gcc... /usr/bin/ld > >> checking if the linker (/usr/bin/ld) is GNU ld... yes > >> checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B > >> checking the name lister (/usr/bin/nm -B) interface... BSD nm > >> checking whether ln -s works... yes > >> checking the maximum length of command line arguments... 1572864 > >> checking how to convert x86_64-pc-linux-gnu file names to > >> x86_64-pc-linux-gnu format... func_convert_file_noop > >> checking how to convert x86_64-pc-linux-gnu file names to toolchain > >> format... func_convert_file_noop > >> checking for /usr/bin/ld option to reload object files... -r > >> checking for objdump... objdump > >> checking how to recognize dependent libraries... pass_all > >> checking for dlltool... no > >> checking how to associate runtime and link libraries... printf %s\n > >> checking for ar... ar > >> checking for archiver @FILE support... @ > >> checking for strip... strip > >> checking for ranlib... ranlib > >> checking command to parse /usr/bin/nm -B output from gcc object... ok > >> checking for sysroot... no > >> checking for a working dd... /usr/bin/dd > >> checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1 > >> checking for mt... mt > >> checking if mt is a manifest tool... no > >> checking for stdio.h... yes > >> checking for stdlib.h... yes > >> checking for string.h... yes > >> checking for inttypes.h... yes > >> checking for stdint.h... yes > >> checking for strings.h... yes > >> checking for sys/stat.h... yes > >> checking for sys/types.h... yes > >> checking for unistd.h... yes > >> checking for dlfcn.h... yes > >> checking for objdir... .libs > >> checking if gcc supports -fno-rtti -fno-exceptions... no > >> checking for gcc option to produce PIC... -fPIC -DPIC > >> checking if gcc PIC flag -fPIC -DPIC works... yes > >> checking if gcc static flag -static works... yes > >> checking if gcc supports -c -o file.o... yes > >> checking if gcc supports -c -o file.o... (cached) yes > >> checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports > >> shared libraries... yes > >> checking whether -lc should be explicitly linked in... no > >> checking dynamic linker characteristics... GNU/Linux ld.so > >> checking how to hardcode library paths into programs... immediate > >> checking whether stripping libraries is possible... yes > >> checking if libtool supports shared libraries... yes > >> checking whether to build shared libraries... yes > >> checking whether to build static libraries... yes > >> checking for C++11 support... no: adding -std=c++11 to CXXFLAGS > >> checking for Boost development files... no > >> configure: error: Boost development files not found > >> > >> Could you please help how to resolve this error. I executed the code > >> to install boost already as provided in the instruction page. > >> > >> > >> _______________________________________________ > >> QuantLib-users mailing list > >> Qua...@li... > >> https://lists.sourceforge.net/lists/listinfo/quantlib-users > |
|
From: Daniel L. <dan...@gm...> - 2022-05-01 06:41:58
|
Hi, Many thanks for your response. Yes I ran 'sudo apt-get install libboost-all-dev' to install boost. However still I get this error. How can I find where the boost is installed and how can I pass that information './configure ' line? Apologies for trivial question if any, as I am not very expert in Linux ecosystem. Thanks and regards, On Sun, 1 May 2022 at 11:53, Jonathan Sweemer <sw...@gm...> wrote: > > Hi Daniel, > > When you say that you “install[ed] boost already as provided in the instruction page” do you mean that you ran the following command? > > sudo apt-get install libboost-all-dev > > If so then you shouldn’t need to use the —with-boost-include and —with-boost-lib flags when configuring QuantLib. As the install guide mentions, you only need those flags when you install boost in a non-standard location. > > Jonathan > > > 2022년 5월 1일 (일) 02:25, Daniel Lobo <dan...@gm...>님이 작성: >> >> Hi, >> >> I am trying to install Quantlib in my Ubuntu VM. I was following the >> instructions as provided in >> https://www.quantlib.org/install/linux.shtml >> >> But this installation failed when I executed >> >> ./configure --with-boost-include=/home/foo/include >> --with-boost-lib=/home/foo/lib >> >> >> >> The error I got is >> >> $ ./configure --with-boost-include=/home/foo/include >> --with-boost-lib=/home/foo/lib >> checking for a BSD-compatible install... /usr/bin/install -c >> checking whether build environment is sane... yes >> checking for a race-free mkdir -p... /usr/bin/mkdir -p >> checking for gawk... no >> checking for mawk... mawk >> checking whether make sets $(MAKE)... no >> checking whether make supports nested variables... no >> checking whether UID '1000' is supported by ustar format... yes >> checking whether GID '1000' is supported by ustar format... yes >> checking how to create a ustar tar archive... gnutar >> checking for gawk... (cached) mawk >> checking for gcc... gcc >> checking whether the C compiler works... yes >> checking for C compiler default output file name... a.out >> checking for suffix of executables... >> checking whether we are cross compiling... no >> checking for suffix of object files... o >> checking whether the compiler supports GNU C... yes >> checking whether gcc accepts -g... yes >> checking for gcc option to enable C11 features... none needed >> checking whether gcc understands -c and -o together... yes >> checking whether make supports the include directive... no >> checking dependency style of gcc... none >> checking for g++... no >> checking for c++... no >> checking for gpp... no >> checking for aCC... no >> checking for CC... no >> checking for cxx... no >> checking for cc++... no >> checking for cl.exe... no >> checking for FCC... no >> checking for KCC... no >> checking for RCC... no >> checking for xlC_r... no >> checking for xlC... no >> checking for clang++... no >> checking whether the compiler supports GNU C++... no >> checking whether g++ accepts -g... no >> checking for g++ option to enable C++11 features... none needed >> checking dependency style of g++... none >> checking how to run the C preprocessor... gcc -E >> checking build system type... x86_64-pc-linux-gnu >> checking host system type... x86_64-pc-linux-gnu >> checking how to print strings... printf >> checking for a sed that does not truncate output... /usr/bin/sed >> checking for grep that handles long lines and -e... /usr/bin/grep >> checking for egrep... /usr/bin/grep -E >> checking for fgrep... /usr/bin/grep -F >> checking for ld used by gcc... /usr/bin/ld >> checking if the linker (/usr/bin/ld) is GNU ld... yes >> checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B >> checking the name lister (/usr/bin/nm -B) interface... BSD nm >> checking whether ln -s works... yes >> checking the maximum length of command line arguments... 1572864 >> checking how to convert x86_64-pc-linux-gnu file names to >> x86_64-pc-linux-gnu format... func_convert_file_noop >> checking how to convert x86_64-pc-linux-gnu file names to toolchain >> format... func_convert_file_noop >> checking for /usr/bin/ld option to reload object files... -r >> checking for objdump... objdump >> checking how to recognize dependent libraries... pass_all >> checking for dlltool... no >> checking how to associate runtime and link libraries... printf %s\n >> checking for ar... ar >> checking for archiver @FILE support... @ >> checking for strip... strip >> checking for ranlib... ranlib >> checking command to parse /usr/bin/nm -B output from gcc object... ok >> checking for sysroot... no >> checking for a working dd... /usr/bin/dd >> checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1 >> checking for mt... mt >> checking if mt is a manifest tool... no >> checking for stdio.h... yes >> checking for stdlib.h... yes >> checking for string.h... yes >> checking for inttypes.h... yes >> checking for stdint.h... yes >> checking for strings.h... yes >> checking for sys/stat.h... yes >> checking for sys/types.h... yes >> checking for unistd.h... yes >> checking for dlfcn.h... yes >> checking for objdir... .libs >> checking if gcc supports -fno-rtti -fno-exceptions... no >> checking for gcc option to produce PIC... -fPIC -DPIC >> checking if gcc PIC flag -fPIC -DPIC works... yes >> checking if gcc static flag -static works... yes >> checking if gcc supports -c -o file.o... yes >> checking if gcc supports -c -o file.o... (cached) yes >> checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports >> shared libraries... yes >> checking whether -lc should be explicitly linked in... no >> checking dynamic linker characteristics... GNU/Linux ld.so >> checking how to hardcode library paths into programs... immediate >> checking whether stripping libraries is possible... yes >> checking if libtool supports shared libraries... yes >> checking whether to build shared libraries... yes >> checking whether to build static libraries... yes >> checking for C++11 support... no: adding -std=c++11 to CXXFLAGS >> checking for Boost development files... no >> configure: error: Boost development files not found >> >> Could you please help how to resolve this error. I executed the code >> to install boost already as provided in the instruction page. >> >> >> _______________________________________________ >> QuantLib-users mailing list >> Qua...@li... >> https://lists.sourceforge.net/lists/listinfo/quantlib-users |
|
From: Jonathan S. <sw...@gm...> - 2022-05-01 06:23:17
|
Hi Daniel, When you say that you “install[ed] boost already as provided in the instruction page” do you mean that you ran the following command? sudo apt-get install libboost-all-dev If so then you shouldn’t need to use the —with-boost-include and —with-boost-lib flags when configuring QuantLib. As the install guide mentions, you only need those flags when you install boost in a non-standard location. Jonathan 2022년 5월 1일 (일) 02:25, Daniel Lobo <dan...@gm...>님이 작성: > Hi, > > I am trying to install Quantlib in my Ubuntu VM. I was following the > instructions as provided in > https://www.quantlib.org/install/linux.shtml > > But this installation failed when I executed > > ./configure --with-boost-include=/home/foo/include > --with-boost-lib=/home/foo/lib > > > > The error I got is > > $ ./configure --with-boost-include=/home/foo/include > --with-boost-lib=/home/foo/lib > checking for a BSD-compatible install... /usr/bin/install -c > checking whether build environment is sane... yes > checking for a race-free mkdir -p... /usr/bin/mkdir -p > checking for gawk... no > checking for mawk... mawk > checking whether make sets $(MAKE)... no > checking whether make supports nested variables... no > checking whether UID '1000' is supported by ustar format... yes > checking whether GID '1000' is supported by ustar format... yes > checking how to create a ustar tar archive... gnutar > checking for gawk... (cached) mawk > checking for gcc... gcc > checking whether the C compiler works... yes > checking for C compiler default output file name... a.out > checking for suffix of executables... > checking whether we are cross compiling... no > checking for suffix of object files... o > checking whether the compiler supports GNU C... yes > checking whether gcc accepts -g... yes > checking for gcc option to enable C11 features... none needed > checking whether gcc understands -c and -o together... yes > checking whether make supports the include directive... no > checking dependency style of gcc... none > checking for g++... no > checking for c++... no > checking for gpp... no > checking for aCC... no > checking for CC... no > checking for cxx... no > checking for cc++... no > checking for cl.exe... no > checking for FCC... no > checking for KCC... no > checking for RCC... no > checking for xlC_r... no > checking for xlC... no > checking for clang++... no > checking whether the compiler supports GNU C++... no > checking whether g++ accepts -g... no > checking for g++ option to enable C++11 features... none needed > checking dependency style of g++... none > checking how to run the C preprocessor... gcc -E > checking build system type... x86_64-pc-linux-gnu > checking host system type... x86_64-pc-linux-gnu > checking how to print strings... printf > checking for a sed that does not truncate output... /usr/bin/sed > checking for grep that handles long lines and -e... /usr/bin/grep > checking for egrep... /usr/bin/grep -E > checking for fgrep... /usr/bin/grep -F > checking for ld used by gcc... /usr/bin/ld > checking if the linker (/usr/bin/ld) is GNU ld... yes > checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B > checking the name lister (/usr/bin/nm -B) interface... BSD nm > checking whether ln -s works... yes > checking the maximum length of command line arguments... 1572864 > checking how to convert x86_64-pc-linux-gnu file names to > x86_64-pc-linux-gnu format... func_convert_file_noop > checking how to convert x86_64-pc-linux-gnu file names to toolchain > format... func_convert_file_noop > checking for /usr/bin/ld option to reload object files... -r > checking for objdump... objdump > checking how to recognize dependent libraries... pass_all > checking for dlltool... no > checking how to associate runtime and link libraries... printf %s\n > checking for ar... ar > checking for archiver @FILE support... @ > checking for strip... strip > checking for ranlib... ranlib > checking command to parse /usr/bin/nm -B output from gcc object... ok > checking for sysroot... no > checking for a working dd... /usr/bin/dd > checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1 > checking for mt... mt > checking if mt is a manifest tool... no > checking for stdio.h... yes > checking for stdlib.h... yes > checking for string.h... yes > checking for inttypes.h... yes > checking for stdint.h... yes > checking for strings.h... yes > checking for sys/stat.h... yes > checking for sys/types.h... yes > checking for unistd.h... yes > checking for dlfcn.h... yes > checking for objdir... .libs > checking if gcc supports -fno-rtti -fno-exceptions... no > checking for gcc option to produce PIC... -fPIC -DPIC > checking if gcc PIC flag -fPIC -DPIC works... yes > checking if gcc static flag -static works... yes > checking if gcc supports -c -o file.o... yes > checking if gcc supports -c -o file.o... (cached) yes > checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports > shared libraries... yes > checking whether -lc should be explicitly linked in... no > checking dynamic linker characteristics... GNU/Linux ld.so > checking how to hardcode library paths into programs... immediate > checking whether stripping libraries is possible... yes > checking if libtool supports shared libraries... yes > checking whether to build shared libraries... yes > checking whether to build static libraries... yes > checking for C++11 support... no: adding -std=c++11 to CXXFLAGS > checking for Boost development files... no > configure: error: Boost development files not found > > Could you please help how to resolve this error. I executed the code > to install boost already as provided in the instruction page. > > > _______________________________________________ > QuantLib-users mailing list > Qua...@li... > https://lists.sourceforge.net/lists/listinfo/quantlib-users > |
|
From: Daniel L. <dan...@gm...> - 2022-04-30 17:22:00
|
Hi, I am trying to install Quantlib in my Ubuntu VM. I was following the instructions as provided in https://www.quantlib.org/install/linux.shtml But this installation failed when I executed ./configure --with-boost-include=/home/foo/include --with-boost-lib=/home/foo/lib The error I got is $ ./configure --with-boost-include=/home/foo/include --with-boost-lib=/home/foo/lib checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a race-free mkdir -p... /usr/bin/mkdir -p checking for gawk... no checking for mawk... mawk checking whether make sets $(MAKE)... no checking whether make supports nested variables... no checking whether UID '1000' is supported by ustar format... yes checking whether GID '1000' is supported by ustar format... yes checking how to create a ustar tar archive... gnutar checking for gawk... (cached) mawk checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether the compiler supports GNU C... yes checking whether gcc accepts -g... yes checking for gcc option to enable C11 features... none needed checking whether gcc understands -c and -o together... yes checking whether make supports the include directive... no checking dependency style of gcc... none checking for g++... no checking for c++... no checking for gpp... no checking for aCC... no checking for CC... no checking for cxx... no checking for cc++... no checking for cl.exe... no checking for FCC... no checking for KCC... no checking for RCC... no checking for xlC_r... no checking for xlC... no checking for clang++... no checking whether the compiler supports GNU C++... no checking whether g++ accepts -g... no checking for g++ option to enable C++11 features... none needed checking dependency style of g++... none checking how to run the C preprocessor... gcc -E checking build system type... x86_64-pc-linux-gnu checking host system type... x86_64-pc-linux-gnu checking how to print strings... printf checking for a sed that does not truncate output... /usr/bin/sed checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for fgrep... /usr/bin/grep -F checking for ld used by gcc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B checking the name lister (/usr/bin/nm -B) interface... BSD nm checking whether ln -s works... yes checking the maximum length of command line arguments... 1572864 checking how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu format... func_convert_file_noop checking how to convert x86_64-pc-linux-gnu file names to toolchain format... func_convert_file_noop checking for /usr/bin/ld option to reload object files... -r checking for objdump... objdump checking how to recognize dependent libraries... pass_all checking for dlltool... no checking how to associate runtime and link libraries... printf %s\n checking for ar... ar checking for archiver @FILE support... @ checking for strip... strip checking for ranlib... ranlib checking command to parse /usr/bin/nm -B output from gcc object... ok checking for sysroot... no checking for a working dd... /usr/bin/dd checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1 checking for mt... mt checking if mt is a manifest tool... no checking for stdio.h... yes checking for stdlib.h... yes checking for string.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for strings.h... yes checking for sys/stat.h... yes checking for sys/types.h... yes checking for unistd.h... yes checking for dlfcn.h... yes checking for objdir... .libs checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC -DPIC checking if gcc PIC flag -fPIC -DPIC works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.o... (cached) yes checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking for C++11 support... no: adding -std=c++11 to CXXFLAGS checking for Boost development files... no configure: error: Boost development files not found Could you please help how to resolve this error. I executed the code to install boost already as provided in the instruction page. |
|
From: Jacek B. <jac...@gm...> - 2022-04-30 13:53:12
|
Hi Aleksis. Try using AssetOrNothingPayoff class. sob., 30 kwi 2022, 15:32 użytkownik Aleksis Ali Raza via QuantLib-users < qua...@li...> napisał: > Hi, when evaluating a binary payoff (using CashOrNothingPayoff) for a > currency pair CCY1/CCY2 (eg. USD/JPY), the payout currency is CCY2 by > default (so JPY in the example). Other than inverting the pair (which is > very awkward), is there any way to switch the payout to be in CCY1 (i.e. > USD) instead, as is conventional? > > Thanks, Aleksis > > _______________________________________________ > QuantLib-users mailing list > Qua...@li... > https://lists.sourceforge.net/lists/listinfo/quantlib-users > |
|
From: Aleksis A. R. <ale...@go...> - 2022-04-30 13:28:23
|
Hi, when evaluating a binary payoff (using CashOrNothingPayoff) for a currency pair CCY1/CCY2 (eg. USD/JPY), the payout currency is CCY2 by default (so JPY in the example). Other than inverting the pair (which is very awkward), is there any way to switch the payout to be in CCY1 (i.e. USD) instead, as is conventional? Thanks, Aleksis |
|
From: Peter C. <pca...@gm...> - 2022-04-29 18:33:53
|
Hi, you can always move a folder to a different volume and create a symlink in place for it. Thanks, Peter On Fri, 29 Apr 2022 at 14:11, Jonathan Sweemer <sw...@gm...> wrote: > > Hi Brian, > > I'm not sure about Homebrew, but if you're following the instructions from the "Installing from a released version" section, then the key is to pass the external directory to the --prefix argument. > > For example if your external directory is mounted on /mnt/external, then you would run > > ./configure --prefix=/mnt/external ... > > You can also use the --prefix argument when installing boost to put the headers and libs in the directory you want. See the following site for more info: > > https://www.boost.org/doc/libs/1_79_0/tools/build/doc/html/index.html#bbv2.installation > > Jonathan > > > > > On Fri, Apr 29, 2022 at 6:12 PM Brian Smith <bri...@gm...> wrote: >> >> Hi, >> >> I am following the instructions to install QL in my Mac as explained here - >> >> https://www.quantlib.org/install/macosx.shtml >> >> However I want to install everything i.e. boost + QL in some external >> directory as I have very limited space in my internal Mac folder. >> >> I tried to change the installation directory by changing the working >> directory using `cd` command, but still end up installing them in >> /usr/local/Cellar/boost/ >> >> Any instruction how to install boost + QL is a specific folder will be >> very helpful. >> >> >> _______________________________________________ >> QuantLib-users mailing list >> Qua...@li... >> https://lists.sourceforge.net/lists/listinfo/quantlib-users > > _______________________________________________ > QuantLib-users mailing list > Qua...@li... > https://lists.sourceforge.net/lists/listinfo/quantlib-users |
|
From: Jonathan S. <sw...@gm...> - 2022-04-29 12:09:42
|
Hi Brian, I'm not sure about Homebrew, but if you're following the instructions from the "Installing from a released version" section, then the key is to pass the external directory to the --prefix argument. For example if your external directory is mounted on /mnt/external, then you would run ./configure --prefix=/mnt/external ... You can also use the --prefix argument when installing boost to put the headers and libs in the directory you want. See the following site for more info: https://www.boost.org/doc/libs/1_79_0/tools/build/doc/html/index.html#bbv2.installation Jonathan On Fri, Apr 29, 2022 at 6:12 PM Brian Smith <bri...@gm...> wrote: > Hi, > > I am following the instructions to install QL in my Mac as explained here - > > https://www.quantlib.org/install/macosx.shtml > > However I want to install everything i.e. boost + QL in some external > directory as I have very limited space in my internal Mac folder. > > I tried to change the installation directory by changing the working > directory using `cd` command, but still end up installing them in > /usr/local/Cellar/boost/ > > Any instruction how to install boost + QL is a specific folder will be > very helpful. > > > _______________________________________________ > QuantLib-users mailing list > Qua...@li... > https://lists.sourceforge.net/lists/listinfo/quantlib-users > |
|
From: Brian S. <bri...@gm...> - 2022-04-29 09:09:03
|
Hi, I am following the instructions to install QL in my Mac as explained here - https://www.quantlib.org/install/macosx.shtml However I want to install everything i.e. boost + QL in some external directory as I have very limited space in my internal Mac folder. I tried to change the installation directory by changing the working directory using `cd` command, but still end up installing them in /usr/local/Cellar/boost/ Any instruction how to install boost + QL is a specific folder will be very helpful. |
|
From: Jonathan S. <sw...@gm...> - 2022-04-27 12:08:25
|
Hi James, Looks like a typo - you want to pass in tenor instead of tenors to ql.SpreadCdsHelper. Jonathan On Tue, Apr 26, 2022 at 10:03 PM James Donaldson via QuantLib-users < qua...@li...> wrote: > Hello, > > > > I’m new to Quantlib and am trying to set up the market data required to > price CDX (IG) trades. When trying to generate CDS helper instruments for a > hazard curve, I’m receiving the error message “Wrong number or type of > arguments for overloaded function ‘new_SpreadCdsHelper’. Would you be able > to point out my error? I appreciate the help. > > > > Thanks, > > > > James > > > > # Market Data > > todaysDate = ql.Date(21, 4, 2022) > > > > calendar = ql.UnitedStates() > > > > recovery_rate = 0.4 > > > > quoted_spreads_bid = > [0.002492,0.002492,0.00358,0.005262,0.0063985,0.007535,0.008975,0.011255] > > > > tenors = [ql.Period(6, ql.Months), > > ql.Period(1, ql.Years), > > ql.Period(2, ql.Years), > > ql.Period(3, ql.Years), > > ql.Period(4, ql.Years), > > ql.Period(5, ql.Years), > > ql.Period(7, ql.Years), > > ql.Period(10, ql.Years)] > > > > # Generate a spot curve – discCrvObj is comprised of dates and discount > factors > > discCrvObj = ql.DiscountCurve(us_isda['maturity_date_ql'].to_list(), > > us_isda['discount_factor'].to_list(), > > ql.Actual360(), > > ql.UnitedStates()) > > > > discCrv = ql.YieldTermStructureHandle(discCrvObj) > > > > # Generate hazard curve > > cds_curve_instruments = [ > > ql.SpreadCdsHelper( > > ql.QuoteHandle(ql.SimpleQuote(s)), > > tenors, > > 0, > > calendar, > > ql.Quarterly, > > ql.Following, > > ql.DateGeneration.TwentiethIMM, > > ql.Actual365Fixed(), > > recovery_rate, > > discCrv > > ) > > for s, tenor in zip(quoted_spreads_bid, tenors) > > ] > > > > hazard_curve = ql.PiecewiseFlatHazardRate(todaysDate, > cds_curve_instruments, ql.Actual365Fixed()) > _______________________________________________ > QuantLib-users mailing list > Qua...@li... > https://lists.sourceforge.net/lists/listinfo/quantlib-users > |
|
From: James D. <Jam...@gm...> - 2022-04-26 12:57:27
|
Hello,
I'm new to Quantlib and am trying to set up the market data required to price CDX (IG) trades. When trying to generate CDS helper instruments for a hazard curve, I'm receiving the error message "Wrong number or type of arguments for overloaded function 'new_SpreadCdsHelper'. Would you be able to point out my error? I appreciate the help.
Thanks,
James
# Market Data
todaysDate = ql.Date(21, 4, 2022)
calendar = ql.UnitedStates()
recovery_rate = 0.4
quoted_spreads_bid = [0.002492,0.002492,0.00358,0.005262,0.0063985,0.007535,0.008975,0.011255]
tenors = [ql.Period(6, ql.Months),
ql.Period(1, ql.Years),
ql.Period(2, ql.Years),
ql.Period(3, ql.Years),
ql.Period(4, ql.Years),
ql.Period(5, ql.Years),
ql.Period(7, ql.Years),
ql.Period(10, ql.Years)]
# Generate a spot curve - discCrvObj is comprised of dates and discount factors
discCrvObj = ql.DiscountCurve(us_isda['maturity_date_ql'].to_list(),
us_isda['discount_factor'].to_list(),
ql.Actual360(),
ql.UnitedStates())
discCrv = ql.YieldTermStructureHandle(discCrvObj)
# Generate hazard curve
cds_curve_instruments = [
ql.SpreadCdsHelper(
ql.QuoteHandle(ql.SimpleQuote(s)),
tenors,
0,
calendar,
ql.Quarterly,
ql.Following,
ql.DateGeneration.TwentiethIMM,
ql.Actual365Fixed(),
recovery_rate,
discCrv
)
for s, tenor in zip(quoted_spreads_bid, tenors)
]
hazard_curve = ql.PiecewiseFlatHazardRate(todaysDate, cds_curve_instruments, ql.Actual365Fixed())
|