Arch Linux

Check the mplayer PKGBUILD, IIRC it may have parameters for video driver versions.

I haven't found video driver versions parameters anywhere. The problem is still unsolved :(

And now nvidia-180.22 is in extra :/

I have a feeling it might be one of the parameters in ./configure. I don't have a machine to test with at the moment, but see if there is anything that helps in there.

Same problem here, with nvidia-180.22 too.

I did a little bit of debugging in the ./configure script of mplayer. I added a call to sh after running each test program so I can do whatever I want in the same environment as the script... and I found out that it was somehow related to libGL. For example, when running the PNG test compiled with -lGL, it crashed (segfault) ; the same test compiled it without -lGL worked fine. I have no idea of the reason for this, and I couldn't find any relevant information with gdb.

Only workaround I found for now: replace --enable-gl by --disable-gl in the PKGBUILD. This way it compiles fine, but without GL support.

Interesting! I guess, by process of elimination, your problem has to be with an OpenGL library or some related dependency. Glad you're getting somewhere though! I'm afraid I don't have much more to add at this point.

What libGL library is linked in? Do you have some local installation residing in /usr/local/lib or some lib/tls directory on your system?

# LANG=C pacman -Qo /usr/lib/libGL.so
/usr/lib/libGL.so is owned by nvidia-utils 180.22-1

Nothing in /usr/local/lib, no lib/tls. It is really related to nvidia-180.22 (which breaks other things like Suspend to RAM on my laptop).

nvidia-180.22 breaks also deluge for me ...deluge failed to start. I know that I'm not very helpful but I'm not a linux expert, so if you want some logs or other info please tell me.

I'm not sure with deluge so please ignore my previous comment for now. But you should look at this http://bugs.archlinux.org/task/12897 (comments). So where is the problem? In fakeroot, nvidia or maybe somewhere else?

It happens here, i hadnt noticed before but i was suprpised when namcap reported no dependency on any image related packages. Just for the record I dont use ass.

Checking for PNG support ... ./configure: line 94: 18838 Segmentation fault "$TMPEXE" >> "$TMPLOG" 2>&1
no (mismatch of library and header versions)
Checking for MNG support ... no
Checking for JPEG support ... ./configure: line 94: 18853 Segmentation fault "$TMPEXE" >> "$TMPLOG" 2>&1
no
Checking for PNM support ... yes
Checking for GIF support ... ./configure: line 94: 18862 Segmentation fault "$TMPEXE" >> "$TMPLOG" 2>&1
./configure: line 94: 18870 Segmentation fault "$TMPEXE" >> "$TMPLOG" 2>&1
no

Did anyone make a report on mplayer upstream?
I am attaching the PKGBUILD i use, it doesnt contain all the dependencies, just the ones reported by namcap, when building with the segfaults. Its pretty simple and minimal featured.

That's the very same problem indeed.
Do you have a nVidia card with the 180.22 driver?

As far as I know, this bug hasn't been reported upstream yet.

I just downgraded to nvidia 177.82-2 and nvidia-utils 177.82-1 and now mplayer compiles fine again (with --enable-gl enabled). I didn't change anything else on my system. So it is definitely related to the nvidia driver.

Many people are complaining about it anyway (on http://www.nvnews.net/vbulletin/forumdisplay.php?f=14 for example). This driver is really unstable and crappy; maybe the packages maintainers should consider downgrading both packages.

please try 180.25: http://www.nvnews.net/vbulletin/showthread.php?p=1914053

I've tested 180.25 and unfortunately the problem still exists :/

Checking for PNG support ... ./configure: line 94: 5262 Segmentation fault "$TMPEXE" >> "$TMPLOG" 2>&1
no (mismatch of library and header versions)
Checking for JPEG support ... ./configure: line 94: 5279 Segmentation fault "$TMPEXE" >> "$TMPLOG" 2>&1
no
Checking for freetype >= 2.0.9 ... ./configure: line 94: 5674 Segmentation fault "$TMPEXE" >> "$TMPLOG" 2>&1
no

Anyone tried 180.27 ?

I've tried 180.27 and result is the same.

I just noticed this too:
Checking for libmp3lame ... ./configure: line 94: 29936 Segmentation fault "$TMPEXE" >> "$TMPLOG" 2>&1
no (in libavcodec: no)
with the latest mplayer export snapshot.
I dont see how nvidia would brake lame.

Its not an mplayer issue at all. It is related to fakeroot just like in http://bugs.archlinux.org/task/12592#comment39686

Building with --asroot works great.

I meant its not nvidia related.