Impossible to compile vlc with current GConf package

Bourdieu · 09-06-2012, 05:48 AM

Hi,

I recently tried to compile the latest vlc version (2.0.3) on my slackware64 current (14.0 RC4) and ran into a compilation error.

Code:

/bin/grep: /usr/lib64/libgconf-2.la: No such file or directory
/bin/sed: can't read /usr/lib64/libgconf-2.la: No such file or directory

After a little research, I found in the slackbuild of the GConf package installed in slackware 14.0 RC4 that the .la file was removed after make install.

Code:

make install DESTDIR=$PKG || exit 1

# Don't ship .la files:
#rm -f $PKG/usr/lib${LIBDIRSUFFIX}/*.la

After commenting this line and rebuilding GConf, the compilation of vlc succeeded.

I thought it was worth mentioning this even if it's not a bug related to a standard package installed in slackware, vlc is still a very popular software for a lot of people.

kikinovak · 09-06-2012, 06:02 AM

VLC probably builds just fine on the VLC developers' PC.

brobr · 09-06-2012, 10:07 AM

The other day I had a compile error because of the absence of a .la file (in this case for libsoup-2.4/queny-plugins) which was not occurring anymore after I removed webkitgtk that was on my system (see slackbuilds-users/2012-August/009117.html). Do you happen to have webkit installed as well?

Maybe of interest: http://blog.flameeyes.eu/2011/05/sur...btool-archives. In response to that blog they mention some packages (like webkit, gstreamer, gst-plugins) that require .la files, but not GConf. It all relates to libtool (http://sourceforge.net/apps/trac/gar/wiki/LibTool) as I just found out.

Maybe someone else can explain this compilation problem better, but understanding that wiki correctly, .la files should not be in packages (except for some that use them internally)

andrew.46 · 09-06-2012, 05:45 PM

Seems odd, I build and run the development version of vlc and cannot see this problem when compiling on rc4. Have to dig a little deeper on my system perhaps...

damgar · 09-06-2012, 10:55 PM

Are you gaining features that you can't get in Eric's self contained VLC package or are you building it yourself for some other reason? I'm just curious if I'm missing out on something I hadn't thought about.

andrew.46 · 09-06-2012, 11:15 PM

Quote:

Originally Posted by damgar

Are you gaining features that you can't get in Eric's self contained VLC package or are you building it yourself for some other reason? I'm just curious if I'm missing out on something I hadn't thought about.

I prefer to build things for myself and vlc is a huge amount of fun to build from source, both the git and the release versions, so I guess I do it myself with my own scripts for the sheer love of tinkering with great software. I still watch Eric's build for tips, some of which have also been absorbed for use in a vlc guide I run for the Ubuntu world. Perhaps I have too much time on my hands

.

damgar · 09-06-2012, 11:22 PM

I do the same with KDE so I totally understand!

dsotm · 09-06-2012, 11:26 PM

Quote:

Originally Posted by damgar

Are you gaining features that you can't get in Eric's self contained VLC package or are you building it yourself for some other reason? I'm just curious if I'm missing out on something I hadn't thought about.

I tried using the package and it also failed to install on -current... Will try again tonight and see if it is for the same reason

damgar · 09-06-2012, 11:29 PM

It's working fine with Gconf and Eric's latest package with the latest packages in current. I don't have many gnome-ish packages installed, just Gconf for google-chrome. I just did a clean install of -current this week.

dsotm · 09-07-2012, 01:26 AM

Well I don't know what went wrong last time I tried but it worked like a charm this time!