LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices



Reply
 
Search this Thread
Old 02-22-2009, 03:11 AM   #1
Daedra
Senior Member
 
Registered: Dec 2005
Location: Springfield, MO
Distribution: Slackware64-14.1
Posts: 1,226

Rep: Reputation: 187Reputation: 187
Alien Bob's VLC Build + Slamd64 Question


After reading the post on 64 bit slackware I decided to give Slamd64 a try since I hadn't used it since 11.0, I am actually quite impressed I have gotten 99% of all my programs and games running fine in the 64 bit environment. The only program giving me grief is VLC, I used Alien Bob's build and it built fine but I get the following error when I try to run it.

[00000001] main libvlc debug: translation test: code is "C"
[00000001] main libvlc error: no memcpy module matched "any"
[00000016] main interface error: no interface module matched "hotkeys,none"
[00000016] main interface error: no suitable interface module
[00000001] main libvlc error: interface "hotkeys,none" initialization failed
[00000017] main interface error: no interface module matched "inhibit,none"
[00000017] main interface error: no suitable interface module
[00000001] main libvlc error: interface "inhibit,none" initialization failed
[00000018] main interface error: no interface module matched "screensaver,none"
[00000018] main interface error: no suitable interface module
[00000001] main libvlc error: interface "screensaver,none" initialization failed
[00000019] main interface error: no interface module matched "signals"
[00000019] main interface error: no suitable interface module
[00000001] main libvlc error: interface "signals" initialization failed
[00000001] main libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface.
[00000020] main interface error: no interface module matched "any"
[00000020] main interface error: no suitable interface module
[00000001] main libvlc error: interface "(null)" initialization failed
*** LibVLC Exception not handled: Interface initialization failed
Set a breakpoint in 'libvlc_exception_not_handled' to debug.


I was reading on the 64 bit slackware post that Arny of Bluewhite64 and Alien Bob both managed to get it working on 64 bit. Can anyone give me any pointers or if your out there Arny or Erik maybe you can point me in the right direction.


Thanks.
 
Old 02-22-2009, 06:45 AM   #2
Slacker Steve
Member
 
Registered: Nov 2008
Posts: 85

Rep: Reputation: 16
I compiled VLC in Slamd64 yesterday (Using alien's slackbuild) and got the same error

Have you tried using Alien Bob's "vlc_old" script?

Last edited by Slacker Steve; 02-22-2009 at 07:58 AM.
 
Old 02-22-2009, 07:09 AM   #3
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,393

Rep: Reputation: Disabled
When VLC 0.9.9 is released (coming week) I will also release a package for use on 64bit Slamd64.

Eric
 
Old 02-22-2009, 07:23 AM   #4
arny
Bluewhite64
 
Registered: Jun 2006
Location: Baia Mare, Maramures, Romania
Distribution: Bluewhite
Posts: 87

Rep: Reputation: 17
Daedra: You can download a vlc package from here: http://data.linux64packages.net:8080...op/vlc/0.9.8a/

Should work on Slamd64 too .
 
Old 02-22-2009, 07:58 AM   #5
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,393

Rep: Reputation: Disabled
Quote:
Originally Posted by arny View Post
Daedra: You can download a vlc package from here: http://data.linux64packages.net:8080...op/vlc/0.9.8a/

Should work on Slamd64 too .
FYI this package was built using my (slightly modified) SlackBuild which you can find inside the directory /usr/doc/vlc-0.9.8a/

Eric
 
Old 02-22-2009, 08:48 AM   #6
piratesmack
Member
 
Registered: Feb 2009
Distribution: Slackware, Arch
Posts: 518

Rep: Reputation: 133Reputation: 133
From http://data.linux64packages.net:8080...-PACKAGES.TXT:
Quote:
5. After the build is done, test your packages and check that there is no /lib64 and /usr/lib64 directory inside the package.
But that VLC package uses lib64


I also notice a lot of --build=$ARCH-slackware-linux in the script, but you say:
Quote:
Also, if in the configure options there is "$ARCH-slackware-linux" option then you have to change it to "$ARCH-pc-linux".

Last edited by piratesmack; 02-22-2009 at 08:56 AM.
 
Old 02-22-2009, 09:28 AM   #7
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,393

Rep: Reputation: Disabled
Quote:
Originally Posted by piratesmack View Post
From http://data.linux64packages.net:8080...-PACKAGES.TXT:
Quote:
5. After the build is done, test your packages and check that there is no /lib64 and /usr/lib64 directory inside the package.
But that VLC package uses lib64

I also notice a lot of --build=$ARCH-slackware-linux in the script, but you say:
Quote:
Also, if in the configure options there is "$ARCH-slackware-linux" option then you have to change it to "$ARCH-pc-linux".
This is because the SlackBuild which was used to create the package was not modified specifically with Bluewhite64 in mind. As a result, it contains lib64 directories which makes it fine for Slamd64, and since Bluewhite64 uses symlinks that point lib64 to lib, the package will work there as well. But it is not a clean package!

Note that packages at http://data.linux64packages.net:8080 are uploaded by Bluewhite64 community members. No apparent quality check is done, which makes it questionable if you should use them at all (like many of the packages found at http://linuxpackages.net/).
Also, you will find only packages there, not the source code, patches and scripts used to create them. Several of the packages were created from scripts available at http://slackbuilds.org or grabbed from my repository and that is when you will find at least the SlackBuild script inside the /usr/doc/ directory of the package.

Eric
 
Old 02-22-2009, 09:49 AM   #8
piratesmack
Member
 
Registered: Feb 2009
Distribution: Slackware, Arch
Posts: 518

Rep: Reputation: 133Reputation: 133
Quote:
Originally Posted by Alien Bob View Post
No apparent quality check is done, which makes it questionable if you should use them at all (like many of the packages found at http://linuxpackages.net/).
Also, you will find only packages there, not the source code, patches and scripts used to create them.
Yeah, I think I'm just going to build it myself then
 
Old 02-22-2009, 10:01 AM   #9
H_TeXMeX_H
Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269
Well, I just successfully compiled it on slamd64 12.1 with this:
Code:
./configure --with-pic --enable-dvdread --enable-flac --enable-faad --enable-theora --disable-qt4 --disable-skins2
Now, even tho I have qt4 installed, it won't find it, so I just disabled it.
 
Old 02-22-2009, 10:10 AM   #10
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,393

Rep: Reputation: Disabled
Quote:
Originally Posted by H_TeXMeX_H View Post
Well, I just successfully compiled it on slamd64 12.1 with this:
Code:
./configure --with-pic --enable-dvdread --enable-flac --enable-faad --enable-theora --disable-qt4 --disable-skins2
Now, even tho I have qt4 installed, it won't find it, so I just disabled it.
Without Qt4 you will not get a GUI... only the commandline version.
Note that my vlc.SlackBuild will add a version of Qt4 as a static library (unless you specifically prohibit that) to the vlc package which makes it independent of any Qt4 you may have installed on your system.

Eric
 
Old 02-22-2009, 04:40 PM   #11
Daedra
Senior Member
 
Registered: Dec 2005
Location: Springfield, MO
Distribution: Slackware64-14.1
Posts: 1,226

Original Poster
Rep: Reputation: 187Reputation: 187
Quote:
Originally Posted by Alien Bob View Post
This is because the SlackBuild which was used to create the package was not modified specifically with Bluewhite64 in mind. As a result, it contains lib64 directories which makes it fine for Slamd64, and since Bluewhite64 uses symlinks that point lib64 to lib, the package will work there as well. But it is not a clean package!

Note that packages at http://data.linux64packages.net:8080 are uploaded by Bluewhite64 community members. No apparent quality check is done, which makes it questionable if you should use them at all (like many of the packages found at http://linuxpackages.net/).
Also, you will find only packages there, not the source code, patches and scripts used to create them. Several of the packages were created from scripts available at http://slackbuilds.org or grabbed from my repository and that is when you will find at least the SlackBuild script inside the /usr/doc/ directory of the package.

Eric
Yeah I just noticed that this is your package modified by someone else. Not surprising since your VLC package is the best there is. I will probably try out the modified one, but I look forward to your new one when VLC 0.9.9 comes out.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
slamd64 libcompizconifg build demolition ninja master Linux - Software 1 01-16-2009 01:30 PM
VLC error: VLC could not open the file "/usr/share/vlc/skins2/text.bmp". brjoon1021 Ubuntu 1 01-14-2009 11:48 PM
Slackware 12 Bob's Firewall modules needed or not in installation? bapigoo9 Slackware 5 12-02-2008 08:15 AM
Question about .rar, VLC, totem-xine and xvid NoTiG Linux - Software 1 05-15-2005 02:50 PM
Alien converting Slackware 10 Question? maximalred Debian 3 10-23-2004 02:08 PM


All times are GMT -5. The time now is 10:04 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration