That seems to have worked Natalie. The compile went through. Here is my full Makefile.config.incl in case anyone else needs it:
## for perl PERL_LIB_CORE=/usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE ## for Boost BOOST_INCL=-I/opt/boost_1_37_0 BOOST_LIBDIR=/opt/boost_1_37_0/lib BOOST_LIBSPEC=-gcc41-mt LINK=shared LIBEXT=so thanks! On Jan 13, 1:04 pm, "Natalie Tasman" <[email protected]> wrote: > Ok, in this case, make sure that /opt/boost/lib is in your LD_LIBRARY_PATH > (or add them to ldconfig) and make sure your Makefile.config.incl contains > lines like this: > > BOOST_INCL= -I<fix this> > BOOST_LIBSPEC=-gcc41-mt > BOOST_LIBDIR=/opt/boost/lib > LINK=shared # optional > LIBEXT=so # optional > > Let me know how this goes. These days we routinely build under centos 5 > 64-bit, so I'm confidident that your system should be able to work. > > Natalie > > On Tue, Jan 13, 2009 at 7:54 AM, GATTACA <[email protected]> wrote: > > > Hello. > > > Here are the boost lib. names in the /opt/boost/lib directory: > > libboost_serialization-gcc41-mt-1_37.a > > libboost_serialization-gcc41-mt-1_37.so > > libboost_serialization-gcc41-mt-1_37.so.1.37.0 > > libboost_serialization-gcc41-mt.a > > libboost_serialization-gcc41-mt.so > > libboost_wserialization-gcc41-mt-1_37.a > > libboost_wserialization-gcc41-mt-1_37.so > > libboost_wserialization-gcc41-mt-1_37.so.1.37.0 > > libboost_wserialization-gcc41-mt.a > > libboost_wserialization-gcc41-mt.so > > > The lib folder also contains: > > graph, iostream, date_time, math, prg_exec_monitor, program_options, > > python, regex, system, signals, thread, test_exec_monitor, unit_test, > > and wave libboost_* files. > > > As for the error message during compile here is the first few: > > > ----------------------------------------------------------------------------------------------------------------------------------- > > /home/dfermin/tmp/tpp.compile/trans_proteomic_pipeline_v411/src/../ > > build/linux/ChromatogramList_Thermo.o: In function > > `__static_initialization_and_destruction_0(int, int)': > > ChromatogramList_Thermo.cpp:(.text+0x51): undefined reference to > > `boost::system::get_system_category()' > > ChromatogramList_Thermo.cpp:(.text+0x5d): undefined reference to > > `boost::system::get_generic_category()' > > ChromatogramList_Thermo.cpp:(.text+0x69): undefined reference to > > `boost::system::get_generic_category()' > > ChromatogramList_Thermo.cpp:(.text+0x75): undefined reference to > > `boost::system::get_generic_category()' > > ChromatogramList_Thermo.cpp:(.text+0x81): undefined reference to > > `boost::system::get_system_category()' > > /home/dfermin/tmp/tpp.compile/trans_proteomic_pipeline_v411/src/../ > > build/linux/DefaultReaderList.o: In function > > `__static_initialization_and_destruction_0(int, int)': > > DefaultReaderList.cpp:(.text+0xc1): undefined reference to > > `boost::system::get_system_category()' > > DefaultReaderList.cpp:(.text+0xcd): undefined reference to > > `boost::system::get_generic_category()' > > DefaultReaderList.cpp:(.text+0xd9): undefined reference to > > `boost::system::get_generic_category()' > > DefaultReaderList.cpp:(.text+0xe5): undefined reference to > > `boost::system::get_generic_category()' > > DefaultReaderList.cpp:(.text+0xf1): undefined reference to > > `boost::system::get_system_category()' > > /home/dfermin/tmp/tpp.compile/trans_proteomic_pipeline_v411/src/../ > > build/linux/DefaultReaderList.o: In function > > `boost::filesystem::basic_path<std::basic_string<char, std::char > > _traits<char>, std::allocator<char> >, boost::filesystem::path_traits> > > > boost::filesystem::current_path<boost::filesystem::basic_path<std::basic_string<char, > > std::char_traits<ch > > ar>, std::allocator<char> >, boost::filesystem::path_traits> >()': > > DefaultReaderList.cpp: > > > (.text._ZN5boost10filesystem12current_pathINS0_10basic_pathISsNS0_11path_traitsEEEEET_v > > [boost::filesystem::basic_path<std::basic_string<char, std::char_tr > > aits<char>, std::allocator<char> >, boost::filesystem::path_traits> > > > boost::filesystem::current_path<boost::filesystem::basic_path<std::basic_string<char, > > std::char_traits<char> > > , std::allocator<char> >, boost::filesystem::path_traits> >()]+0x38): > > undefined reference to `boost::filesystem::detail::get_current_path_api > > (std::basic_string<char, std::char_ > > traits<char>, std::allocator<char> >&)' > > /home/dfermin/tmp/tpp.compile/trans_proteomic_pipeline_v411/src/../ > > build/linux/FrequencyEstimatorPhysicalModel.o: In function > > `__static_initialization_and_destruction_0(int, in > > t)': > > FrequencyEstimatorPhysicalModel.cpp:(.text+0x3a): undefined reference > > to `boost::system::get_system_category()' > > FrequencyEstimatorPhysicalModel.cpp:(.text+0x46): undefined reference > > to `boost::system::get_generic_category()' > > FrequencyEstimatorPhysicalModel.cpp:(.text+0x52): undefined reference > > to `boost::system::get_generic_category()' > > FrequencyEstimatorPhysicalModel.cpp:(.text+0x5e): undefined reference > > to `boost::system::get_generic_category()' > > FrequencyEstimatorPhysicalModel.cpp:(.text+0x6a): undefined reference > > to `boost::system::get_system_category()' > > > ... > > > ----------------------------------------------------------------------------------------------------------------------------------- > > > I noticed that the libboost files seem to indicate g++ 4.1 was used, > > so I tried recompiling with that compiler version and still got the > > same errors. > > > Thanks again for any and all help. > > > On Jan 12, 3:58 pm, "Natalie Tasman" <[email protected]> > > wrote: > > > And, what are the actual boost lib. names in that directory? For > > example, > > > libboost-serialization* ? > > > > On Mon, Jan 12, 2009 at 8:02 AM, Brian Pratt <[email protected] > > >wrote: > > > > > What kind of errors are you getting with these settings? > > > > > -----Original Message----- > > > > From: [email protected] > > > > [mailto:[email protected]] On Behalf Of GATTACA > > > > Sent: Monday, January 12, 2009 6:42 AM > > > > To: spctools-discuss > > > > Subject: [spctools-discuss] Re: TPP 4.1.1 fails to compile on Fedora 7 > > > > 64bit > > > > > So I've tried different options in the Makefile.config.incl file with > > > > no results. The compile continues to falter because of BOOST. > > > > > Here is the contents of my Makefile.config.incl: > > > > > BOOST_LIBDIR=/opt/boost_1_37_0/lib > > > > BOOST=/opt/boost_1_37_0 > > > > BOOST_INCL=-I /opt/boost_1_37_0 > > > > > Anything else I'm missing? > > > > > I'm using g++ 3.4 if that makes a difference. > > > > > Thanks. > > > > > On Dec 17 2008, 11:08 pm, Paulo Nuin <[email protected]> wrote: > > > > > Change the BOOST_INCLUDE variable. You'll find some other errors > > along > > > > > the way. > > > > > Cheers > > > > > Paulo > > > > > > GATTACA wrote: > > > > > > Hello. > > > > > > > I've just downloaded the latest and greatest source code for TPP > > off > > > > > > SVN. > > > > > > When I try to compile it fails. The error suggests that the boost > > > > > > libraries are out of date. > > > > > > > Specifically, TPP seems to be looking for the "foreach.hpp" file > > from > > > > > > the boost library. This isn't available until version 1_34_0 as far > > as > > > > > > I know. And 1_34_0 isn't available as an RPM forFedora7. > > > > > > > I currently don't want to overwrite my existing boost files with a > > > > > > fresh compile of 1_37_0 (the latest version) since it will break > > some > > > > > > of my dependencies for other programs I have. > > > > > > > Instead I've downloaded boost 1_37_0 and installed it to /opt/ > > > > > > boost_1_37_0 > > > > > > > Is there a way to specify in the Makefile.config.incl where TPP > > should > > > > > > look for ALL of the boost code? I'd like to point TPP to /opt/ > > > > > > boost_1_37_0 instead of the default /usr/lib > > > > > > > Thanks in advance. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "spctools-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/spctools-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
