LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   Problem using Alien Bobs VLC build. (http://www.linuxquestions.org/questions/slackware-14/problem-using-alien-bobs-vlc-build-717320/)

garyg007 04-06-2009 11:24 PM

Problem using Alien Bobs VLC build.
 
Here is what I did:

This is the command I used:
Code:

STATIC_QT4=NO STATIC_FFMPEG=NO USE_PATENTS=NO ./vlc.SlackBuild
Some Installed packages:
Code:

root@abitbox:~# ls /var/log/packages/* | grep -i ffmpeg
/var/log/packages/ffmpeg-20081105-i486-1_SBo
/var/log/packages/ffmpegthumbnailer-1.3.0-i486-1_SBo
root@abitbox:~# ls /var/log/packages/* | grep -i qt4
/var/log/packages/lyx_qt4-1.5.3-i486-1_SBo
/var/log/packages/pyqt4-4.4.4-i486-1_SBo
/var/log/packages/qt4-4.4.3-i486-1_SBo
root@abitbox:~#

This is what happened:
Code:

checking for UpnpInit in -lupnp... no
configure: error: cannot find Intel UPnP SDK (libupnp)
sed: can't read vlc-config: No such file or directory
root@abitbox:/home/gary/Desktop/vlc#

Running slackware 12.2

Any idea what I might have done wrong?

Gary

grunt547 04-07-2009 12:05 AM

Does it work to "slackpkg install libupnp"?

Nille_kungen 04-07-2009 01:03 AM

It looks like it vlc doesn't find libupnp so the configure exits on vlc.
The script should be building libupnp as an static library and the vlc configure should then find and link against the static libupnp.

I would check the "configure-vlc_upnp.log" and "make-vlc_upnp.log" to see if theres something wrong.

garyg007 04-07-2009 04:43 PM

2 Attachment(s)
It looks like the vlc build failed because the libupnp configure failed.
/tmp/build/tmp-vlc/libupnp-1.6.6/config.log is attached.
Nille_kungen suggested I check "configure-vlc_upnp.log" and "make-vlc_upnp.log";
"make-vlc_upnp.log" is also attached --- it has a number of lines in it saying "nothing to be done"

What info would be usefull in helping me get this resolved?


Gary

Nille_kungen 04-07-2009 05:52 PM

Did you post the configure-vlc_upnp.log made by vlc.SlackBuild? or is it another log.
I ask because it differs from mine.

garyg007 04-07-2009 09:52 PM

1 Attachment(s)
The config log I posted was "/tmp/build/tmp-vlc/libupnp-1.6.6/config.log" which is, I believe, the config log for the install of libupnp done by alien bob's vlc.slackbuild script.
configure-vlc_upnp.log looks like the vlc configure log - it shows the error vlc encountered;
"/tmp/build/tmp-vlc/libupnp-1.6.6/config.log" shows what looks like a problem with the configure of libupnp.

Anyway, the attachment here is configure-vlc_upnp.log

Gary

Nille_kungen 04-07-2009 11:44 PM

Now that one looks better :)
Is this an full standard 12.2 install? because when i diff your log against mine some paths differ.

I looked in your logs and they look ok.
Can you post the configure-vlc.log also?

garyg007 04-08-2009 04:21 PM

1 Attachment(s)
Quote:

Originally Posted by Nille_kungen (Post 3501973)
Now that one looks better :)
Is this an full standard 12.2 install? because when i diff your log against mine some paths differ.

I looked in your logs and they look ok.
Can you post the configure-vlc.log also?

Yes, it is a full standrd 12.2.install. However, some stuff has been installed using "configure/make" rather than the slackbuilds or slackpkg
here is configure-vlc.log.

garyg007 04-09-2009 10:48 AM

One of the items included in this build, is libupnp.

I have other software installed that includes libupnp (mediatomb).

Is it possible that this is causing problem is a conflict.?

If so, how do I fix it?

The already-installed upnp is located:
Code:

root@abitbox:~# whereis libupnp
libupnp: /usr/local/lib/libupnp.a /usr/local/lib/libupnp.so /usr/local/lib/libupnp.la
root@abitbox:~#

Gary

Ramurd 04-09-2009 07:46 PM

since libupnp is in /usr/local/lib, is this directory in your /etc/ld.so.conf file? (I think it should be there by default)
if not, add this directory and run ldconfig.

Another thing can be that UpnpInit is a new function (even if it was upnp_init before, this counts as a new function) and as such not in your libraries. You could try to update libupnp.

The error message indicates it cannot find a function in the library. This can mean two things:
- the function is not in your libraries (update)
- or: it cannot find the library (probably a "library path" setting)

If /etc/ld.so.conf edits don't work you could try fiddling with the $LD_LIBRARY_PATH and like variables for header files.

Eternal_Newbie 04-10-2009 03:53 AM

Does this, or similar, happen when you build Alien Bob's (Eric's) VLC slackbuild as standard?

In my experience VLC is incredibly sensitive and/or susceptible to library versions. Which is why Eric's slackbuild is such a blessing. It builds everything needed as static and if necessary downloads the library version that that version of VLC builds with.

If that doesn't work and you can't get hold of Alien Bob by email, you could also try commenting out the stuff referring to libupnp . AFAIK, if you aren't running a media centre pc, VLC doesn't really need it.

Alien Bob 04-10-2009 06:18 AM

Quote:

Originally Posted by Eternal_Newbie (Post 3504377)
Does this, or similar, happen when you build Alien Bob's (Eric's) VLC slackbuild as standard?

In my experience VLC is incredibly sensitive and/or susceptible to library versions. Which is why Eric's slackbuild is such a blessing. It builds everything needed as static and if necessary downloads the library version that that version of VLC builds with.

If that doesn't work and you can't get hold of Alien Bob by email, you could also try commenting out the stuff referring to libupnp . AFAIK, if you aren't running a media centre pc, VLC doesn't really need it.

Of course, for a successful build of VLC that does not pick up unwanted dependencies (like the version of upnp you have present in your /usr/local) you need to build on a clean system. The packages that I make available are all built on such a clean system, and I can guarantee that the SlackBuild script for any of my packages will run successfully.

If you have trouble building your own package for vlc, why not install my ready-made package? I know that this involves a level of trust, but if you install and use Slackware you are implicitly already trusting my work :-)

Eric

garyg007 04-10-2009 11:28 AM

Quote:

Originally Posted by Alien Bob (Post 3504431)
If you have trouble building your own package for vlc, why not install my ready-made package? I know that this involves a level of trust, but if you install and use Slackware you are implicitly already trusting my work :-)

Eric

thank you for the reply. And, Eric, I do trust your work!

The first thing I did was to try the ready-made package. It installed ok, but when I tried to run vlc, it would run for a few seconds then the sound would break up and/or the picture get jumpy, then freeze. I tried both
.mpg files and dvd's. Thats when I tried to build vlc.

Thought just occurred to me - was the ready made package built with
"USE_PATENTS=NO"? The dvd's I have were all made with software that had access to some of the patented packages.


Gary

garyg007 04-10-2009 08:35 PM

Ive done some more digging and found that vlc package handles some files, and some it does not. It also did not handle a commercial dvd (yes, I do have libdvdcss installed).

I used idvid (part of the tovid suite) to show the attributes of three files; two which did not work, and one that did. Here is the results:
Code:

--------        ----  ----------  --------  --------
Filename        Size  Resolution  VBitrate  ABitrate
--------        ----  ----------  --------  --------
TheThinMan.mpg  371M  352x240    1133600  224000 *
The_Birds.mpg    3.7G  720x480    4352000  224000
TheBigSleep.mpg  3.2G  720x480    3916000  224000

This makes me think that Eric's package is golden, and that some runtime parms need to be adjusted. If so can someone help with those.

Gary

* this is the one that played ok.

garyg007 04-13-2009 01:49 PM

VLC package does not work
 
OK, I installed a fresh copy of slackware 12.2. - from the downloaded cd's (the install used the first 3 cd's)

vlc-0.9.9-i486-1alien.tgz was the FIRST thing installed after definiing a regular user.

This is on a 64bit intel 3.06ghz processor running ALL 32 bit software.

VLC does not work. The symptoms are described in a previous post.

Since I trust Eric's work, that would make me think that VLC has some serious issues on some processors

here is the info for my cpu:
Code:

root@abitbox:~# cat /proc/cpuinfo
processor      : 0
vendor_id      : GenuineIntel
cpu family      : 15
model          : 4
model name      : Intel(R) Celeron(R) CPU 3.06GHz
stepping        : 9
cpu MHz        : 3073.610
cache size      : 256 KB
fdiv_bug        : no
hlt_bug        : no
f00f_bug        : no
coma_bug        : no
fpu            : yes
fpu_exception  : yes
cpuid level    : 5
wp              : yes
flags          : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc up pebs bts pni monitor ds_cpl tm2 cid cx16 xtpr lahf_lm
bogomips        : 6147.22
clflush size    : 64
power management:

root@abitbox:~#



All times are GMT -5. The time now is 08:47 PM.