We're working with command line tools first
./autogen.sh
glibtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `m4'.
glibtoolize: linking file `m4/ltmain.sh'
glibtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.
glibtoolize: linking file `m4/libtool.m4'
glibtoolize: linking file `m4/ltoptions.m4'
glibtoolize: linking file `m4/ltsugar.m4'
glibtoolize: linking file `m4/ltversion.m4'
glibtoolize: linking file `m4/lt~obsolete.m4'
configure.ac:21: installing 'm4/compile'
configure.ac:24: installing 'm4/config.guess'
configure.ac:24: installing 'm4/config.sub'
configure.ac:15: installing 'm4/install-sh'
configure.ac:15: installing 'm4/missing'
services/Makefile.am: installing 'm4/depcomp'
parallel-tests: installing 'm4/test-driver'
./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... m4/install-sh -c -d
checking for gawk... no
checking for mawk... no
checking for nawk... no
checking for awk... awk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether make supports nested variables... (cached) yes
checking for style of include used by make... GNU
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 we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking whether gcc and cc understand -c and -o together... yes
checking build system type... x86_64-apple-darwin11.4.2
checking host system type... x86_64-apple-darwin11.4.2
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/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin11/4.2.1/ld
checking if the linker (/usr/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin11/4.2.1/ld) is GNU ld... no
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm
checking the name lister (/usr/bin/nm) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 196608
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking how to convert x86_64-apple-darwin11.4.2 file names to x86_64-apple-darwin11.4.2 format... func_convert_file_noop
checking how to convert x86_64-apple-darwin11.4.2 file names to toolchain format... func_convert_file_noop
checking for /usr/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin11/4.2.1/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... dlltool
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... no
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm output from gcc object... ok
checking for sysroot... no
checking for mt... no
checking if : is a manifest tool... no
checking for dsymutil... dsymutil
checking for nmedit... nmedit
checking for lipo... lipo
checking for otool... otool
checking for otool64... no
checking for -single_module linker flag... yes
checking for -exported_symbols_list linker flag... yes
checking for -force_load linker flag... yes
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.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... -fno-common -DPIC
checking if gcc PIC flag -fno-common -DPIC works... yes
checking if gcc static flag -static works... no
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/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin11/4.2.1/ld) supports shared libraries... yes
checking dynamic linker characteristics... darwin11.4.2 dyld
checking how to hardcode library paths into programs... immediate
checking for dlopen in -ldl... yes
checking whether a program can dlopen itself... yes
checking whether a statically linked program can dlopen itself... yes
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 doxygen... no
configure: WARNING: doxygen not found - will not generate any doxygen documentation
checking for perl... /usr/bin/perl
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking for ld used by g++... /usr/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin11/4.2.1/ld
checking if the linker (/usr/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin11/4.2.1/ld) is GNU ld... no
checking whether the g++ linker (/usr/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin11/4.2.1/ld) supports shared libraries... yes
checking for g++ option to produce PIC... -fno-common -DPIC
checking if g++ PIC flag -fno-common -DPIC works... yes
checking if g++ static flag -static works... no
checking if g++ supports -c -o file.o... yes
checking if g++ supports -c -o file.o... (cached) yes
checking whether the g++ linker (/usr/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin11/4.2.1/ld) supports shared libraries... yes
checking dynamic linker characteristics... darwin11.4.2 dyld
checking how to hardcode library paths into programs... immediate
checking for C++ compiler vendor... gnu
checking for OSX binary architectures... no
checking for specific CPU architecture... no
checking for debugging... no
checking for plug-ins directory... /usr/local/share/pion/plugins
checking for boostlib >= 1.35... configure: error: We could not detect the boost libraries (version 1.35 or higher). If you have a staged boost library (still not installed) please specify $BOOST_ROOT in your environment and do not give a PATH to --with-boost option. If you are sure you have boost installed, then check your version number looking in . See http://randspringer.de/boost for more documentation.
tried locate boost.hpp - because I know headers labelled like that
tried locate *.hpp - found instance of location
https://sites.google.com/site/alexeyvakimov/mini-tutorials/programming-boost-python-c
See How to get started
export BOOST_ROOT=/opt/local/include/boost
No dice
checking for boostlib >= 1.35... configure: error: We could not detect the boost libraries (version 1.35 or higher). If you have a staged boost library (still not installed) please specify $BOOST_ROOT in your environment and do not give a PATH to --with-boost option. If you are sure you have boost installed, then check your version number looking in . See http://randspringer.de/boost for more documentation.
http://randspringer.de/boost
Looked up
http://www.randspringer.de/boost/upt.html
Decided to try the config flag.
./configure --with-boost=/opt/local/include/boost
No dice
Checking my version of boost for my sanity
grep BOOST_LIB_VERSION /opt/local/include/boost/version.hpp
// BOOST_LIB_VERSION must be defined to be the same as BOOST_VERSION
#define BOOST_LIB_VERSION "1_52"
Screw it, let's try macports
sudo port selfupdate
sudo port upgrade outdated
Many package updates later.....
Having a lot of trouble getting configure to pay attention to the BOOST_HOME variable and --with-boost, so I am taking the path of least resistance here; which I think is probably Xcode. It is likely on a linux box or vm the libraries would be in the right place.
Now I went to try this in Xcode which is Version 4.5.2 (4G2008a)
After attempting to fix the command line version with --boost-lib= to no avail, I brought it into Xcode using Header Search Paths under the Build Settings tab in the main window when you click on the project. This is located under the heading "Search Paths", but if you got overwhelmed with these settings there is a wonderful little search in the top right corner that I use to pick out the right settings.
You hit the plus ,but, don't worry about specifying a specific architecture or sdk, just type in the path.
You can use the command line tool "locate" to help.
However, after doing this Xcode complains about not finding a log4cpp header. What happens often enough is that some tools are so common and documentation is so scattered that it becomes hard to tell whether we left directives to help guide people.
This probably is easily enough remedied: we can port install log4cpp (and since the compiler is looking for a header, we shouldn't look for a binary version but a development version. If you are using CPP under *nix (Linux,Unix,Mac) variants, this should become something you get familiar with).
port search log4cpp
log4cpp @1.1 (devel)
configurable logging for C++
log4shib @1.0.8 (sysutils, shibboleth, devel)
configurable logging for C++, fork of log4cpp
Found 2 ports.
So here we clearly want log4cpp (devel).
sudo port install log4cpp
Now we'll get, after authenticated
---> Fetching archive for log4cpp
---> Attempting to fetch log4cpp-1.1_0.darwin_11.x86_64.tbz2 from http://packages.macports.org/log4cpp
---> Attempting to fetch log4cpp-1.1_0.darwin_11.x86_64.tbz2.rmd160 from http://packages.macports.org/log4cpp
---> Installing log4cpp @1.1_0
---> Activating log4cpp @1.1_0
---> Cleaning log4cpp
---> Updating database of binaries: 100.0%
---> Scanning binaries for linking errors: 100.0%
---> No broken files found.
Now because I am lazy I'll try just running it, perhaps the search paths are already good enough. If not, we'll edit them.
I tried
locate logger.hpp
But locate hasn't been updated so it won't find it. I look for the log4cplus in the same include area and I find it.
Oops, looks like I installed the wrong library! It should be log4cpluss, but I installed log4cpp.
sudo port install log4cplus
Password:
---> Computing dependencies for log4cplus
---> Fetching archive for log4cplus
---> Attempting to fetch log4cplus-1.0.4.1_0.darwin_11.x86_64.tbz2 from http://packages.macports.org/log4cplus
---> Attempting to fetch log4cplus-1.0.4.1_0.darwin_11.x86_64.tbz2 from http://lil.fr.packages.macports.org/log4cplus
---> Attempting to fetch log4cplus-1.0.4.1_0.darwin_11.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/log4cplus
---> Fetching distfiles for log4cplus
---> Attempting to fetch log4cplus-1.0.4.1.tar.xz from http://superb-dca2.dl.sourceforge.net/log4cplus
---> Verifying checksum(s) for log4cplus
---> Extracting log4cplus
---> Configuring log4cplus
---> Building log4cplus
Ok, now we should be good!
But hark, yet another error (and a couple of places that weren't cast yield warnings).
ld: file not found: ~/.cloudmeter/openssl-1.0.1c/lib/libssl-pic.a
clang: error: linker command failed with exit code 1 (use -v to see invocation)
Ok looks like we probably need a link to an ssl library from openssl. We probably need to change a reference in our build.
So we should research this, after looking around I don't have a stock version of this library.
hmm, http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=246928
So perhaps we need a pic version?
Searching around I found this page in the docs
Wiki for Pion
This page indicates that we don't need openssl, let alone a pic version. I'd rather have the SSL library
At this point there are variables in this that point to my home directory .cloudmeter/library, were I to continue, I'd probably have to dig into modifying these, but the destination for such a server ins't going to be on a Mac, it would likely be a linux box. So I think I will abandon this and pick it up some other time.
Pion appears to offer cheap Boost library web services. Reviewing the source may be worthwhile in the future.