[SOLVED] alienBOB's vlc keeps stoping build with this error...

irgunII · 11-18-2013, 09:15 AM

I'm not a programmer, so I can't seem to figure out where or why this is happening. The script for building vlc 2.1.1 from alienBOB seems like it should be foolproof, yet I keep getting the error below. Any ideas?

Code:

make[2]: Entering directory `/tmp/build/tmp-vlc/vlc-2.1.1/bin'
  GEN    ../modules/plugins.dat
Inconsistency detected by ld.so: dl-tls.c: 75: _dl_next_tls_modid: Assertion `result <= _rtld_local._dl_tls_max_dtv_idx + 1' failed!
make[2]: *** [../modules/plugins.dat] Error 127
make[2]: Leaving directory `/tmp/build/tmp-vlc/vlc-2.1.1/bin'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory `/tmp/build/tmp-vlc/vlc-2.1.1'
make: *** [install] Error 2
mv: cannot stat '/tmp/build/package-vlc/usr/share/doc/vlc/*': No such file or directory
cp: cannot stat 'HACKING': No such file or directory
tar: *.diff: Cannot stat: No such file or directory
tar: *.patch: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors

I really, really like vlc over the other movie players and in 14.0 I had it working beautifully, but no matter what I do in 14.1 it keeps 'pausing' every 2 or three seconds while watching movies (DVD, on the hdd, etc...doesn't matter). This means I've built vlc from the 2.0.9 to the 2.1.1 via the non-alienBOB way and even installed his already built vlc...nothing has worked, they all behave exactly the same way with the half-a-second pause every two or three seconds making the movie unwatchable.

Mark Pettit · 11-18-2013, 09:17 AM

Do you have a good reason for building it yourself ? As opposed to just downloading the fully built version(s) from his site.

bartgymnast · 11-18-2013, 09:57 AM

I just used AlienBob's script and ....

Slackware package /tmp/vlc-2.1.1-x86_64-1alien.txz created.

this is on a clean 14.1 install.

so something else is blocking your build.

number22 · 11-18-2013, 03:30 PM

check config.log from tmp/build/tmp-vlc/vlc-2.1.1/

irgunII · 11-18-2013, 05:12 PM

Quote:

Originally Posted by Mark Pettit

Do you have a good reason for building it yourself ? As opposed to just downloading the fully built version(s) from his site.

I build *all* the apps/programs for my system. It's just good policy because what if I find an app/program no one has written/made a blob for yet? And it gives me a chance to keep trying to learn to read the programming. I can figure much of it out, but a lot still is beyond me.

irgunII · 11-18-2013, 05:13 PM

Quote:

Originally Posted by bartgymnast

I just used AlienBob's script and ....

Slackware package /tmp/vlc-2.1.1-x86_64-1alien.txz created.

this is on a clean 14.1 install.

so something else is blocking your build.

That's what I was saying...I also used the 'script', but for some reason it's giving the error message(s) above in my first post.

chrisretusn · 11-18-2013, 06:03 PM

It builds fine here.

You did replicate Alien Bob's build directory for your local build?

irgunII · 11-18-2013, 06:17 PM

Quote:

Originally Posted by number22

check config.log from tmp/build/tmp-vlc/vlc-2.1.1/

That was a lesson in futility, lol. I did mention I'm no programmer, so 99.9% of that 458Kb file was gibberish, heh. The only thing I saw that looked out of place 'to me' was here:

Code:

## ---------------------- ##
## Running config.status. ##
## ---------------------- ##

This file was extended by vlc config.status 2.1.1, which was
generated by GNU Autoconf 2.69.  Invocation command line was

  CONFIG_FILES    = 
  CONFIG_HEADERS  = 
  CONFIG_LINKS    = 
  CONFIG_COMMANDS = 
  $ ./config.status 

on oogah

config.status:2238: creating Makefile
config.status:2238: creating doc/Makefile
config.status:2238: creating modules/Makefile
config.status:2238: creating m4/Makefile
config.status:2238: creating po/Makefile.in
config.status:2238: creating share/Makefile
config.status:2238: creating compat/Makefile
config.status:2238: creating src/Makefile
config.status:2238: creating lib/Makefile
config.status:2238: creating bin/Makefile
config.status:2238: creating test/Makefile
config.status:2238: creating modules/access/Makefile
config.status:2238: creating modules/access/rtp/Makefile
config.status:2238: creating modules/access_output/Makefile
config.status:2238: creating modules/audio_filter/Makefile
config.status:2238: creating modules/audio_mixer/Makefile
config.status:2238: creating modules/audio_output/Makefile
config.status:2238: creating modules/codec/Makefile
config.status:2238: creating modules/control/Makefile
config.status:2238: creating modules/demux/Makefile
config.status:2238: creating modules/gui/Makefile
config.status:2238: creating modules/gui/macosx/Makefile
config.status:2238: creating modules/gui/minimal_macosx/Makefile
config.status:2238: creating modules/gui/macosx_dialog_provider/Makefile
config.status:2238: creating modules/gui/qt4/Makefile
config.status:2238: creating modules/gui/skins2/Makefile
config.status:2238: creating modules/lua/Makefile
config.status:2238: creating modules/meta_engine/Makefile
config.status:2238: creating modules/misc/Makefile
config.status:2238: creating modules/mux/Makefile
config.status:2238: creating modules/notify/Makefile
config.status:2238: creating modules/packetizer/Makefile
config.status:2238: creating modules/services_discovery/Makefile
config.status:2238: creating modules/stream_filter/Makefile
config.status:2238: creating modules/stream_out/Makefile
config.status:2238: creating modules/text_renderer/Makefile
config.status:2238: creating modules/video_chroma/Makefile
config.status:2238: creating modules/video_filter/Makefile
config.status:2238: creating modules/video_output/Makefile
config.status:2238: creating modules/visualization/Makefile
config.status:2238: creating modules/mmx/Makefile
config.status:2238: creating modules/sse2/Makefile
config.status:2238: creating modules/altivec/Makefile
config.status:2238: creating modules/arm_neon/Makefile
config.status:2238: creating config.h
config.status:2467: executing depfiles commands
config.status:2467: executing libtool commands
config.status:2467: executing po-directories commands
configure:53861: WARNING: unrecognized options: --disable-switcher, 
--enable-qt4, --enable-pvr, --enable-dv, --enable-real, --enable-loader

And I still have no idea if that's what caused the errors making the build stop or not and wouldn't know what to do with what I found above anyway.

irgunII · 11-18-2013, 06:20 PM

Quote:

Originally Posted by chrisretusn

It builds fine here.

You did replicate Alien Bob's build directory for your local build?

The script downloaded everything it supposedly needs and builds where I have the vlc tarball and the vlc.slackbuild file at. AlienBOB told me so himself that that's all I should need to do. Is that what you're asking or have I flubbed something up?

irgunII · 11-18-2013, 07:10 PM

I've been looking at the 'make' logs of all those programs that vlc calls for that are also in /tmp.

At the end of the 'vlc make' log, I found this but don't know what it means:

Code:

  GEN    ../modules/plugins.dat
Inconsistency detected by ld.so: dl-tls.c: 75: _dl_next_tls_modid: Assertion `result <= _rtld_local._dl_tls_max_dtv_idx + 1' failed!
make[2]: *** [../modules/plugins.dat] Error 127
make[2]: Leaving directory `/tmp/build/tmp-vlc/vlc-2.1.1/bin'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/build/tmp-vlc/vlc-2.1.1'
make: *** [all] Error 2

And all of the log files that are called 'patch' have nothing but

Code:

Hmm...  I can't seem to find a patch in there anywhere.

but I don't think any of those are contributing to any errors.

number22 · 11-18-2013, 07:16 PM

there are 82 files in alien's vlc build directory,

Code:

lftp -c 'open http://www.slackware.com/~alien/slackbuilds/vlc/;mirror build/'
rename your build to vlc after making sure no other directory with same name first.
cd vlc
find ./ -type f -maxdepth 1 | wc -l
sh ./vlc.SlackBuild

if you using slackbuild scripts make sure you have all its files, switching version of build unless you know what you doing. Stay with main build, looking at version number; for example, if the scripts ask for 1.1.2, you can using slackbuild scripts all 1.1.x without much modification at most time, if the version number jumps to 1.2.x, then you might need file dependency check, if version number jump to 2.x.x then, kernel, libraries dependency checks.

chrisretusn · 11-18-2013, 07:53 PM

I am asking if you downloaded all of the files located in Alien Bob's vlc/build directory?

If not the what files did you download?
I will assumed the tarball, the slack-* files, and of course the SlackBuild script. It sounds like you missed that patch files. (Your error posted in first post has the clue.)

While it is true that the SlackBuild script will download the needed source files, there are several patch files that are needed. Those are not downloaded by the script and this is why your build is failing.

It is usually prudent to download all of the files in the build directory. The script will still download additional files, but for the script to succeed you must have the patch files (*.patch, *.diff).

chrisretusn · 11-18-2013, 08:02 PM

I try to keep it simple. On my system all of my slackbuilds are located in /home/non-slack/slackubilds/. For vlc that would be /home/non-slack/slackbuilds/vlc/. From inside the vlc directory I issue the following: (Actually I use a script.)

Code:

lftp -c "open http://connie.slackware.com/~alien/slackbuilds/vlc/; mirror -e build"

What is does is mirror the vlc/build directory on the server and puts it in /home/non-slack/slackbuild/vlc/build/ directory.

irgunII · 11-18-2013, 10:54 PM

That must be it - not downloading and installing/using the patches and such.

I'll try your suggestion to download it all and see how it goes and let everyone know what happens.

Thank you both for all this help.

By the way, I'm getting the install/download from his http://taper.alienbase.nl/mirrors/ site, but I'll get those other anyway as it won't hurt to have everything in the directory and let the build script use it or not as it needs.

irgunII · 11-19-2013, 12:15 AM

That was the problem - I didn't have the diff and patch files. Once those were in the directory, it built just fine.

Thank you to everyone who helped. I'll mark this as solved now.