Slackware 13.0/KDE4/mjpegtools-1.9.0 compile problem

et1swret · 07-24-2010, 12:08 PM

Perhaps someone can explain this to me. I have seen that several people are having similar issues, and several others have no problem compiling mjpegtools on Slackware. Files are from SlackBuilds. See code for error:

Code:

creating yuvinactive
gcc -DHAVE_CONFIG_H -I. -I..  -I.. -I/usr/include -I../utils  -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12   -DG_LOG_DOMAIN=\"lavtools\"   -O2 -march=i486 -mtune=i686 -pthread -Wall -Wunused -MT glav-glav.o -MD -MP -MF .deps/glav-glav.Tpo -c -o glav-glav.o `test -f 'glav.c' || echo './'`glav.c
mv -f .deps/glav-glav.Tpo .deps/glav-glav.Po
gcc -DHAVE_CONFIG_H -I. -I..  -I.. -I/usr/include -I../utils  -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12   -DG_LOG_DOMAIN=\"lavtools\"   -O2 -march=i486 -mtune=i686 -pthread -Wall -Wunused -MT glav-glav_main.o -MD -MP -MF .deps/glav-glav_main.Tpo -c -o glav-glav_main.o `test -f 'glav_main.c' || echo './'`glav_main.c
mv -f .deps/glav-glav_main.Tpo .deps/glav-glav_main.Po
/bin/sh ../libtool --tag=CC   --mode=link gcc  -O2 -march=i486 -mtune=i686 -pthread -Wall -Wunused   -o glav glav-glav.o glav-glav_main.o ../utils/libmjpegutils.la  -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lgdk_pixbuf-2.0 -lpangocairo-1.0 -lcairo -lpango-1.0 -lfreetype -lfontconfig -lgobject-2.0 -lgmodule-2.0 -lglib-2.0   -lm 
gcc -O2 -march=i486 -mtune=i686 -pthread -Wall -Wunused -o .libs/glav glav-glav.o glav-glav_main.o  ../utils/.libs/libmjpegutils.so /usr/lib/libgtk-x11-2.0.so /usr/lib/libgdk-x11-2.0.so /usr/lib/libatk-1.0.so /usr/lib/libgdk_pixbuf-2.0.so /usr/lib/libgio-2.0.so /usr/lib/libpangocairo-1.0.so /usr/lib/libpangoft2-1.0.so /usr/lib/libcairo.so /usr/lib/libpixman-1.so -lpng12 /usr/lib/libXrender.so /usr/lib/libX11.so /usr/lib/libxcb.so /usr/lib/libXau.so /usr/lib/libXdmcp.so /usr/lib/libpango-1.0.so /usr/lib/libfontconfig.so /usr/lib/libfreetype.so -lz /usr/lib/libexpat.so /usr/lib/libgobject-2.0.so /usr/lib/libgmodule-2.0.so -ldl /usr/lib/libglib-2.0.so -lm 
/usr/lib/gcc/i486-slackware-linux/4.3.3/../../../../i486-slackware-linux/bin/ld: errno: TLS definition in /lib/libc.so.6 section .tbss mismatches non-TLS reference in /usr/lib/gcc/i486-slackware-linux/4.3.3/../../../libz.so
/lib/libc.so.6: could not read symbols: Bad value
collect2: ld returned 1 exit status
make[2]: *** [glav] Error 1
make[2]: Leaving directory `/tmp/SBo/mjpegtools-1.9.0/lavtools'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/SBo/mjpegtools-1.9.0'
make: *** [all] Error 2

Is this a linker problem, a problem with libz.so, a problem with libc.so.6, or an errno problem, or a problem with the mjpeg toolset source? How do we fix this?

Regards,

ET1

damgar · 07-24-2010, 01:07 PM

I had a problem way back when. This thread covers it, but I think Ponce might have moved some of his links?

et1swret · 07-24-2010, 01:18 PM

Thanks, damgar, but ponce has moved the links... they are inaccessible and do me no good. I have already read that thread

. Thus, my new thread.... maybe ponce can update?

Damgar, do you have any more suggestions? maybe an exerpt or other advice?

Regards,

ET1

damgar · 07-24-2010, 01:26 PM

I would try a private message to ponce as I don't remember exactly what was needed. ponce is very good about working out patches and fixes for version changes and he usually posts them around. You also might look at Alien BOB's blog for the fixes.

You might want to look at the 13.1 slackbuild also. It has a couple of patch files that may be of use to you. My problems were with building on then current. Are you using a stock 13.0?

et1swret · 07-24-2010, 01:38 PM

Stock 13.0, but has been in production for a while...

Will check Alien Bob's blog, and will check the 13.1 SlackBuild. Thanks for your help, damgar. I usually don't have issues with compilation on Slackware, but this one has really been a bugger.

I need to compile k9copy with dvd authoring, this is what sparked this thread. All other dependencies have compiled and installed perfectly, until mjpegtools.

Thanks again for your suggestions.

Regards,

ET1

damgar · 07-24-2010, 01:51 PM

There is a precompliled package in the Salix repositories for 13.0. I've never had a problem with Salix packages. http://download.salixos.org/i486/13.0/salix/xap/

et1swret · 07-24-2010, 01:52 PM

damgar,

same issues with the SlackBuild for 13.0. This is really puzzling...

Regards,

ET1

et1swret · 07-24-2010, 01:53 PM

Will try the Salix build...

et1swret · 07-24-2010, 02:03 PM

I still think that the root cause of failure lies here:

Code:

/usr/lib/gcc/i486-slackware-linux/4.3.3/../../../../i486-slackware-linux/bin/ld: errno: TLS definition in /lib/libc.so.6 section .tbss mismatches non-TLS reference in /usr/lib/gcc/i486-slackware-linux/4.3.3/../../../libz.so
/lib/libc.so.6: could not read symbols: Bad value
collect2: ld returned 1 exit status

It seems threadding is enabled in libc.so.6 and not in libz.so but this is just speculation. Would have to recompile both to see if that fixes the issue, but that is not an option at this time.

If recompiling the libraries does not fix the issue, then I would suspect the mjpegtools source, but regardless of where the problem is, it needs to be fixed.

I downloaded the Salix package, and am continuing with the k9copy build. Will advise of the outcome.

Thanks again, damgar.

Regards,

ET1

et1swret · 07-24-2010, 03:45 PM

After installing the Salix package for mjpegtools, and finishing the k9copy compile and install, I was able to accomplish the task I needed to do. Thanks, damgar, for all your help.

I still think that someone needs to look at the compile issues with mjpegtools and help determine exactly what the root cause is for the failure. This was a stock 13.0 install, and failure of compilation should not have happened. What is the conflict with TLS and non-TLS in the libraries?

Regards,

ET1