more on compiling issues

Well I went at it for another few hours yesterday attempting to get a compile going. I’ve yet to bring my issues up to any of the folks on IRC, but I will still talk about what is going on here. As I said yesterday I trudged through my problems with compiling/configuring libtprl. As for compiling tpserver-cpp I have run into many more issues. More on those after the jump.

Now my compilation of tpserver-cpp on Mac OS X has been nothing but problematic. I’ve thus far encountered the following.
The first warning I get happens during autogen.sh, but things finish as per normal:

automake…
tpserver/Makefile.am:5: GNUTLS does not appear in AM_CONDITIONAL
tpserver/Makefile.am:14: AVAHI does not appear in AM_CONDITIONAL
autoconf…
removing config.cache…
ready to configure

This concerns me a little bit, but I have ensured I have the two packages through Macports (which I will have an interesting word about at the end of the post)
I encounter my first real show stopper when I run this rather lengthy command

PKG_CONFIG_PATH=/opt/tpserver-cpp/lib/pkgconfig ./configure –prefix=/opt/tpserver-cpp/ –with-guile=/sw/share/guile/1.8/scripts/binoverride

Yeah, its all one line. This follows from mithro’s instructions on compiling tpserver-cpp, with the added guile path indicating the location of my fink installed guile. This mess of a command returns leads me to two seperate errors. The first of which is this:

./configure: line 20021: syntax error near unexpected token `libtprl,’
./configure: line 20021: `PKG_CHECK_MODULES(libtprl, libtprl >= 0.1.2,’

Now this is really weird, having a syntax error in a script I otherwise know works on Linux. xdotx let me now that my bash version (GNU bash, version 3.2.17(1)-release (i386-apple-darwin9.0)) may be causing this specific problem. I tried removing the check, as libtprl IS there, and it IS the correct version. Doing so only gives me an identical syntax error for avahi-client. Well I didn’t have this package before, so I got it, and still no dice. I checked versions manually and removed the version check in question.
Now I run into another error. This time it isn’t a syntax error. I get the following error related to boostlibs:

checking for boostlib >= 1.32.1… yes
checking whether the Boost::Signals library is available… yes
configure: error: Could not link against !

Now I didn’t cut that section between “against” and “!” out, there is just nothing there. I don’t have any idea what to do about this one. While I can skip a version check I can’t really skip linking. Now if mithro, llnz or anyone for that matter reading this one knows what I can do, please let me know. I wouldn’t mind your commentary on the “PKG_CHECK_MODULES”/Syntax error as well.

On Macports oddities
Macports is probably the single most odd pseudo-package manager I have ever had to deal with. I am frequently encountering multiple errors for almost every package I go to install. The strange things about these errors is that they seem to disappear, and things continue as normal.
I’ve developed a sure-fire process for fixing any problems I encounter installing Macports packages. Upon receiving an error during package install do the following:

  • First, run the install command again. This generally fixes everything
  • If that doesn’t work just run sudo port clean package-name . This fixes everything else. Thats it, if it didn’t fix here, you probably are encountering a known bug.

  • Organization: Thousand Parsec Original: Source