Boxee-source compilation "checking for main in -ldl... no"

Question

Hello Guys and Girls,
I'm trying to get Boxee to run on my laptop so that I can setup up on a small homebuild HTPC running a naked Arch Linux Installation in the future.
I have tried the versions that are in the AUR and got them to install after linking some header files, downgrading glew etc. but they are very old and
are teaming with bugs. The repo found in the Wiki https://wiki.archlinux.org/index.php/Boxee-source is outdated as well. The current Version is 1.5
and it is downloading 0.9.8.something from the repo.
There are 32 and 64 bit *.deb's for Ubuntu available on boxee.tv/download, but Ubuntu is way to bloated and I don't know how to work with it
when it comes to more advanced configuration (booting straight into X11 and starting boxee trough .xinitrc which worked fine with xbmc).
Made me realize what a great learning tool Arch Linux is.
So I downloaded the Sorce Code and extracted it and opened the README.ubuntu to find some building instructions.
TOC
1. Introduction
2. Installing the required Ubuntu packages
3. How to compile
4. Create Installer
1. Introduction
We currently recommend Ubuntu 11.10.
NOTE TO NEW LINUX USERS: All lines that are prefixed with the '#'
character are commands that need to be typed into a terminal window /
console (similar to the command prompt for Windows). Note that the '#'
character itself should NOT be typed as part of the command.
2. Installing the required Ubuntu packages
# sudo apt-get install make g++ gcc gawk pmount nasm automake cmake bison libsdl1.2-dev libsdl-image1.2-dev libfribidi-dev liblzo2-dev libfreetype6-dev libsqlite3-dev libogg-dev libasound2-dev python-sqlite libglew1.5-dev libcurl4-openssl-dev libmad0-dev libogg-dev libvorbis-dev libsmbclient-dev libmysqlclient-dev libpcre3-dev libdbus-1-dev libjasper-dev libfontconfig1-dev libbz2-dev libboost-dev libfaac-dev libenca-dev libpng12-dev libjpeg62-dev libcdio-dev libsamplerate0-dev libmms-dev libmpeg3-dev libfaad-dev libflac-dev doxygen php5 swig libssl-dev libgdbm-dev libvdpau-dev libxmu-dev libxtst-dev libxinerama-dev libhal-dev libhal-storage-dev gperf libtool
3. How to compile
# ./bootstrap
# ./configure --enable-optimizations --disable-debug
# make -j4
# make -C tools/TexturePacker -f Makefile.host
# rm skin/boxee/media/Textures.xbt
# make -C skin/boxee/media
4. Create installer
# cd debian
# sudo ./make_debian.sh
./bootstrap wored fine.
With ./configure I ran into problems a few times but managed to fix them on my own ( installed libmms, lz02, mysql-clients etc. when check failed)
but now I'm stuck at: "checking for main in -ldl... no" and I have no clue how to fix it. What am I missing?
Once I get this to compile and run I want to contribute my first package to the AUR. Would be a good opportunity to get familiar with ABS, PKGBUILDs and all
that.
Regards,
blackout23
Last edited by blackout23 (2011-12-30 22:42:21)

Answer 1

Looks like a linking issue?
http://phaseit.net/claird/comp.unix.programmer/linking-unix.html wrote:
Linux's dl library
There are at least two distinct problem symptoms with dynamic-linking that Linux users frequently report: that
    the configure for Tcl and/or derivatives think that dynamic linking is not possible; and
    a makefile which attempts dynamic linking fails for not resolving "... -ldl ..." adequately.
To the best of my knowledge, all instances of the former problem have been traced back to an inconsistency between configure and other sources, typically the result of incomplete application of a patch, mis-installation of a compiler and its ancillary libraries, or some sort of cross-OS contamination. As far as I know, correcting any compiler problems and doing a "make distclean" to sanitize the Tcl source directory has always been enough to cure the situation.
Some installations (Slackware 2.1? 3.1? others? Red Hat before 4.0?) are reputed to have a missing symbolic link between /lib/libdl.so.1 and /lib/libdl.so. Any application which employs dynamic linking, and which therefore links with "... -ldl ..." under Linux, apparently will fail until one completes the installation by commanding
           ln -s /lib/libdl.so.1 /lib/libdl.so
That's the whole story that I know. However, those unfamiliar with Unix deserve a warning: the previous paragraph used "link" in three distinct senses. If these matters are new to you, you might feel more comfortable substituting
           cp /lib/libdl.so.1 /lib/libdl.so
for the "ln ..." command above. When I'm able to make time, I'll return to explain these matters more fully.
Why isn't there a /lib/libdl.a? That's an involved topic, one that I aim to document later in spring '97.
ldconfig is sometimes an issue for Linux. I'll document it once I understand it better.