|
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 |