LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   bumblebee slackbuilds from jbegoski are failing (http://www.linuxquestions.org/questions/slackware-14/bumblebee-slackbuilds-from-jbegoski-are-failing-4175480427/)

flokofcgulls 10-11-2013 09:52 AM

bumblebee slackbuilds from jbegoski are failing
 
I'm fighting with my laptop GPU yet again. I recently removed bumblebee to get the hdmi port working, but after doing so my battery life was reduced by over 50%, which isn't going to work for me. So now I'm trying to rebuild all the bumblebee packages from github, but some of them are failing.

VirtualGL was the first to fail, and I noticed that his github documentation was building them in a different order from the slackware wiki, so I decided to do it his way, but then mesa failed, so I'm thinking the problem might be on my end.

So my question is, has anyone successfully built all of these packages in their most recent versions? Looks like his last update was October 5th, so in the last week maybe?

WhiteWolf1776 10-11-2013 12:08 PM

First, are you on -current or 14.0?

I keep a fork of the repo specifically for -current... and no, it doesn't include the VirtualGL anymore... primus is the new standard.

Take a look here and post back if you still have issues:

https://github.com/WhiteWolf1776/Bumblebee-SlackBuilds


Yea, a third set of instructions, but I have rebuilt them this week on -current. Oh, and if you are on -current, no need to rebuild mesa anymore.

TommyC7 10-11-2013 01:19 PM

Quote:

flockofcgulls:
VirtualGL was the first to fail, and I noticed that his github documentation was building them in a different order from the slackware wiki, so I decided to do it his way, but then mesa failed, so I'm thinking the problem might be on my end.
Whether you choose to use primus or VirtualGL, I'm a bit concerned about whether you have a full installation or not.

I recently rebuilt mesa on both 14.0, 13.37 and -current to assist someone to get "Glamor" working on their Slackware installation, and it built fine.

What are the error messages you get when building mesa, or libjpeg-turbo and VirtualGL?

Also, regardless of order, both ask you to build and install libjpeg-turbo before you do VirtualGL since libjpeg-turbo is a dependency for it.

Quote:

So my question is, has anyone successfully built all of these packages in their most recent versions? Looks like his last update was October 5th, so in the last week maybe?
To answer this question, Yes. I just re-built VirtualGL-2.3.2 to see if the latest was still building fine and it was.

Also, that update was to update the nvidia drivers, VirtualGL was untouched.

flokofcgulls 10-11-2013 04:21 PM

Thank you both for the info!

Quote:

First, are you on -current or 14.0?
I'm on Slackware64 14.0, with multilib.

Quote:

Whether you choose to use primus or VirtualGL, I'm a bit concerned about whether you have a full installation or not.
Yes, I am running a full installation.

Quote:

What are the error messages you get when building mesa, or libjpeg-turbo and VirtualGL?

Also, regardless of order, both ask you to build and install libjpeg-turbo before you do VirtualGL since libjpeg-turbo is a dependency for it.
libjpeg-turbo builds and installs just fine. I just reinstalled it to reproduce these error messages.

Here's what I get when building VirtualGL:
Code:

CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
Please set them or make sure they are set and tested correctly in the CMake files:
-z now OPENGL_gl_LIBRARY
    linked by target "fakerut" in directory /tmp/bbsb/VirtualGL-2.3.2/server
OPENGL_gl_LIBRARY (ADVANCED)
    linked by target "glreadtest" in directory /tmp/bbsb/VirtualGL-2.3.2/util
    linked by target "rrfaker" in directory /tmp/bbsb/VirtualGL-2.3.2/server
    linked by target "rrglframe" in directory /tmp/bbsb/VirtualGL-2.3.2/client
    linked by target "glthreads" in directory /tmp/bbsb/VirtualGL-2.3.2/glxdemos
    linked by target "glthreadsint" in directory /tmp/bbsb/VirtualGL-2.3.2/glxdemos
    linked by target "glxcontexts" in directory /tmp/bbsb/VirtualGL-2.3.2/glxdemos
    linked by target "glxdemo" in directory /tmp/bbsb/VirtualGL-2.3.2/glxdemos
    linked by target "glxgears" in directory /tmp/bbsb/VirtualGL-2.3.2/glxdemos
    linked by target "glxgears_pixmap" in directory /tmp/bbsb/VirtualGL-2.3.2/glxdemos
    linked by target "glxheads" in directory /tmp/bbsb/VirtualGL-2.3.2/glxdemos
    linked by target "glxinfo" in directory /tmp/bbsb/VirtualGL-2.3.2/glxdemos
    linked by target "glxpbdemo" in directory /tmp/bbsb/VirtualGL-2.3.2/glxdemos
    linked by target "glxpixmap" in directory /tmp/bbsb/VirtualGL-2.3.2/glxdemos
    linked by target "glxspheres" in directory /tmp/bbsb/VirtualGL-2.3.2/glxdemos
    linked by target "manywin" in directory /tmp/bbsb/VirtualGL-2.3.2/glxdemos
    linked by target "offset" in directory /tmp/bbsb/VirtualGL-2.3.2/glxdemos
    linked by target "overlay" in directory /tmp/bbsb/VirtualGL-2.3.2/glxdemos
    linked by target "pbdemo" in directory /tmp/bbsb/VirtualGL-2.3.2/glxdemos
    linked by target "pbinfo" in directory /tmp/bbsb/VirtualGL-2.3.2/glxdemos
    linked by target "shape" in directory /tmp/bbsb/VirtualGL-2.3.2/glxdemos
    linked by target "sharedtex" in directory /tmp/bbsb/VirtualGL-2.3.2/glxdemos
    linked by target "sharedtex_mt" in directory /tmp/bbsb/VirtualGL-2.3.2/glxdemos
    linked by target "testgl5" in directory /tmp/bbsb/VirtualGL-2.3.2/glxdemos
    linked by target "wincopy" in directory /tmp/bbsb/VirtualGL-2.3.2/glxdemos
    linked by target "xfont" in directory /tmp/bbsb/VirtualGL-2.3.2/glxdemos
    linked by target "xrotfontdemo" in directory /tmp/bbsb/VirtualGL-2.3.2/glxdemos

-- Configuring incomplete, errors occurred!

And here is the error I get when building mesa:
Code:

make: Entering directory `/tmp/bbsb/mesa-demos-8.0.1/src/demos'
  CC    gears.o
  CCLD  gears
/usr/lib64/gcc/x86_64-slackware-linux/4.7.1/../../../../x86_64-slackware-linux/bin/ld: cannot find -lGL
collect2: error: ld returned 1 exit status
make: *** [gears] Error 1
make: Leaving directory `/tmp/bbsb/mesa-demos-8.0.1/src/demos'

I didn't attempt to build mesa-compat32 or any of the remaining packages after these two failed, but all the ones prior to these seemed to work just fine.

I'm going to try WhiteWolf's repo and I'll report back with an update.

flokofcgulls 10-11-2013 05:04 PM

I just started over from scratch using WhiteWolf's repo. Since VirtualGL and mesa were not in there, I didn't build those, and everything else built and installed fine.

If I try to run glxgears using primus, it just hangs at the command line with no error or output of any kind, and I have to Ctrl-C to stop it. Running glxgears by itself works fine.

So I'm guessing mesa is the last obstacle to cross. I considered installing the one from -current, but there's no compat32 package to go with it, so I need to build it from a slackbuild.

What are my options?

WhiteWolf1776 10-11-2013 06:56 PM

I think your best option would be building mesa from here:
https://github.com/jgeboski/Bumblebe...ee/master/mesa

But... that doesn't seem to be working for you... Can you try again, post additional info on the error? It's looking like mesa built fine above, and the demo's bombed for some reason I don't see.

Best guess, your env for some reason got hosed.

flokofcgulls 10-11-2013 07:24 PM

OK, I tried rebuilding mesa again using jbegoski's SlackBuild scripts. Instead of running the download.sh script, I manually downloaded both the Mesa 8.0.4 and Mesa Demos 8.0.1 packages. When I tried to build, it stopped at the same spot, with the same error.

Here's a larger section of the last stages of the build before it fails:

Code:

/bin/ginstall -c -d /tmp/bbsb/package-mesa/usr/lib64
/bin/ginstall -c -d /tmp/bbsb/package-mesa/usr/lib64/pkgconfig
/bin/sh ../../bin/minstall ../../lib64/libGLU.*so* /tmp/bbsb/package-mesa/usr/lib64
/bin/ginstall -c -m 644 glu.pc /tmp/bbsb/package-mesa/usr/lib64/pkgconfig
gmake[2]: Leaving directory `/tmp/bbsb/Mesa-8.0.4/src/glu'
gmake[2]: Entering directory `/tmp/bbsb/Mesa-8.0.4/src/gallium'
gmake[3]: Entering directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/auxiliary'
gmake[3]: Leaving directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/auxiliary'
gmake[3]: Entering directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/drivers'
gmake[4]: Entering directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/drivers/galahad'
gmake[4]: Leaving directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/drivers/galahad'
gmake[4]: Entering directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/drivers/identity'
gmake[4]: Leaving directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/drivers/identity'
gmake[4]: Entering directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/drivers/llvmpipe'
gmake[4]: Leaving directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/drivers/llvmpipe'
gmake[4]: Entering directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/drivers/noop'
gmake[4]: Leaving directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/drivers/noop'
gmake[4]: Entering directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/drivers/nouveau'
gmake[4]: Leaving directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/drivers/nouveau'
gmake[4]: Entering directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/drivers/nv50'
gmake[4]: Leaving directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/drivers/nv50'
gmake[4]: Entering directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/drivers/nvc0'
gmake[4]: Leaving directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/drivers/nvc0'
gmake[4]: Entering directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/drivers/nvfx'
gmake[4]: Leaving directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/drivers/nvfx'
gmake[4]: Entering directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/drivers/r300'
gmake[4]: Leaving directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/drivers/r300'
gmake[4]: Entering directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/drivers/r600'
gmake[4]: Leaving directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/drivers/r600'
gmake[4]: Entering directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/drivers/rbug'
gmake[4]: Leaving directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/drivers/rbug'
gmake[4]: Entering directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/drivers/softpipe'
gmake[4]: Leaving directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/drivers/softpipe'
gmake[4]: Entering directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/drivers/trace'
gmake[4]: Leaving directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/drivers/trace'
gmake[3]: Leaving directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/drivers'
gmake[3]: Entering directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/state_trackers'
gmake[4]: Entering directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/state_trackers/dri'
gmake[5]: Entering directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/state_trackers/dri/drm'
gmake[5]: Leaving directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/state_trackers/dri/drm'
gmake[5]: Entering directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/state_trackers/dri/sw'
gmake[5]: Leaving directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/state_trackers/dri/sw'
gmake[4]: Leaving directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/state_trackers/dri'
gmake[3]: Leaving directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/state_trackers'
gmake[2]: Leaving directory `/tmp/bbsb/Mesa-8.0.4/src/gallium'
gmake[2]: Entering directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/winsys'
gmake[3]: Entering directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/winsys/nouveau/drm'
gmake[3]: Leaving directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/winsys/nouveau/drm'
gmake[3]: Entering directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/winsys/radeon/drm'
gmake[3]: Leaving directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/winsys/radeon/drm'
gmake[3]: Entering directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/winsys/sw'
gmake[4]: Entering directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/winsys/sw/null'
gmake[4]: Leaving directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/winsys/sw/null'
gmake[4]: Entering directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/winsys/sw/wrapper'
gmake[4]: Leaving directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/winsys/sw/wrapper'
gmake[4]: Entering directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/winsys/sw/xlib'
gmake[4]: Leaving directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/winsys/sw/xlib'
gmake[3]: Leaving directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/winsys/sw'
gmake[3]: Entering directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/winsys/sw/dri'
gmake[3]: Leaving directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/winsys/sw/dri'
gmake[2]: Leaving directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/winsys'
gmake[2]: Entering directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/targets'
gmake[3]: Entering directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/targets/dri-nouveau'
/bin/ginstall -c -d /tmp/bbsb/package-mesa/usr/lib64/xorg/modules/dri
/bin/sh ../../../../bin/minstall -m 755 nouveau_dri.so /tmp/bbsb/package-mesa/usr/lib64/xorg/modules/dri
gmake[3]: Leaving directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/targets/dri-nouveau'
gmake[3]: Entering directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/targets/dri-r300'
/bin/ginstall -c -d /tmp/bbsb/package-mesa/usr/lib64/xorg/modules/dri
/bin/sh ../../../../bin/minstall -m 755 r300_dri.so /tmp/bbsb/package-mesa/usr/lib64/xorg/modules/dri
gmake[3]: Leaving directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/targets/dri-r300'
gmake[3]: Entering directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/targets/dri-r600'
/bin/ginstall -c -d /tmp/bbsb/package-mesa/usr/lib64/xorg/modules/dri
/bin/sh ../../../../bin/minstall -m 755 r600_dri.so /tmp/bbsb/package-mesa/usr/lib64/xorg/modules/dri
gmake[3]: Leaving directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/targets/dri-r600'
gmake[3]: Entering directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/targets/dri-swrast'
/bin/ginstall -c -d /tmp/bbsb/package-mesa/usr/lib64/xorg/modules/dri
/bin/sh ../../../../bin/minstall -m 755 swrast_dri.so /tmp/bbsb/package-mesa/usr/lib64/xorg/modules/dri
gmake[3]: Leaving directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/targets/dri-swrast'
gmake[2]: Leaving directory `/tmp/bbsb/Mesa-8.0.4/src/gallium/targets'
make[1]: Leaving directory `/tmp/bbsb/Mesa-8.0.4/src'
checking build system type... x86_64-slackware-linux-gnu
checking host system type... x86_64-slackware-linux-gnu
checking for a BSD-compatible install... /bin/ginstall -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking dependency style of gcc... (cached) gcc3
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/x86_64-slackware-linux/bin/ld
checking if the linker (/usr/x86_64-slackware-linux/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking for /usr/x86_64-slackware-linux/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for ar... ar
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking whether we are using the GNU C++ compiler... (cached) yes
checking whether g++ accepts -g... (cached) yes
checking dependency style of g++... (cached) gcc3
checking how to run the C++ preprocessor... g++ -E
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/x86_64-slackware-linux/bin/ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for ld used by g++... /usr/x86_64-slackware-linux/bin/ld -m elf_x86_64
checking if the linker (/usr/x86_64-slackware-linux/bin/ld -m elf_x86_64) is GNU ld... yes
checking whether the g++ linker (/usr/x86_64-slackware-linux/bin/ld -m elf_x86_64) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking if g++ supports -c -o file.o... (cached) yes
checking whether the g++ linker (/usr/x86_64-slackware-linux/bin/ld -m elf_x86_64) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether gcc and cc understand -c and -o together... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for GL... yes
checking GL/glut.h usability... yes
checking GL/glut.h presence... yes
checking for GL/glut.h... yes
checking for glutInit in -lglut... yes
checking for GLEW... yes
checking for GLU... yes
checking for EGL... yes
checking for GLESV1... no
checking for GLESV2... no
checking for VG... no
checking for OSMESA... no
checking for X11... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating src/demos/Makefile
config.status: creating src/egl/Makefile
config.status: creating src/egl/eglut/Makefile
config.status: creating src/egl/opengl/Makefile
config.status: creating src/egl/opengles1/Makefile
config.status: creating src/egl/opengles2/Makefile
config.status: creating src/egl/openvg/Makefile
config.status: creating src/egl/openvg/trivial/Makefile
config.status: creating src/fp/Makefile
config.status: creating src/fpglsl/Makefile
config.status: creating src/glsl/Makefile
config.status: creating src/gs/Makefile
config.status: creating src/images/Makefile
config.status: creating src/objviewer/Makefile
config.status: creating src/osdemos/Makefile
config.status: creating src/perf/Makefile
config.status: creating src/rbug/Makefile
config.status: creating src/redbook/Makefile
config.status: creating src/samples/Makefile
config.status: creating src/slang/Makefile
config.status: creating src/tests/Makefile
config.status: creating src/tools/Makefile
config.status: creating src/tools/trace/Makefile
config.status: creating src/trivial/Makefile
config.status: creating src/util/Makefile
config.status: creating src/vp/Makefile
config.status: creating src/vpglsl/Makefile
config.status: creating src/wgl/Makefile
config.status: creating src/xdemos/Makefile
config.status: executing depfiles commands
config.status: executing libtool commands
make: Entering directory `/tmp/bbsb/mesa-demos-8.0.1/src/demos'
  CC    gears.o
  CCLD  gears
/usr/lib64/gcc/x86_64-slackware-linux/4.7.1/../../../../x86_64-slackware-linux/bin/ld: cannot find -lGL
collect2: error: ld returned 1 exit status
make: *** [gears] Error 1
make: Leaving directory `/tmp/bbsb/mesa-demos-8.0.1/src/demos'

When you say "hosed", do you mean like, reformat "hosed"?

WhiteWolf1776 10-11-2013 07:30 PM

no no.. hosed as in wrong path somewhere. let me look this over and I'll see what I can find.

WhiteWolf1776 10-11-2013 07:59 PM

Ok, I just pulled everything down to my stock slack 14.0 VM and did the mesa build. The download referenced in the info isn't there anymore, so I pulled the Mesa tarball down from here:
ftp://ftp.slackware.com/pub/slackwar...source/x/mesa/

You will need to rename it from a .xz to .bz2 but just to make the slackbuild script work (tar doesn't really care as long as the filename is right)

For me, this built in about 8 mins, and completed clean.

If it still won't build for you, maybe back out all of the bbsb packages and build mesa first. My first thought on seeing your log here is that mesa failed somewhere so the demo's also failed.. but that's really just a shot in the dark.

flokofcgulls 10-11-2013 09:21 PM

I just tried your first suggestion, and got the same error.

So then I tried your second suggestion, and got the same error. =(

Sounds like that's all my options then, so I guess I'll have to reformat whenever time permits.

Greatly appreciate you taking the time to look into this.

WhiteWolf1776 10-11-2013 09:32 PM

Hmmm... Well, there is always updating to -current. Its in beta and pretty stable, plus, no need to mess with mesa then. Wish I could figure this one out... Seems you are really close, just some extra package is hosing you.

Stupid question time. You are running these SlackBuilds as root 'su -' right?

flokofcgulls 10-11-2013 10:10 PM

I was actually debating whether to go with -current next time or not. I saw a thread here in the past where Pat mentioned that -current is a testing area, and that it should be expected that things will break from time to time, but I've noticed that most people seem to run it instead of the stable release. Although this would be my first upgrade to a new release, so for me it will be as much research and time as a reformat (I'm very meticulous about things.)

No such thing as a stupid question. =) Yes I am running the SlackBuild scripts as root, my regular account doesn't have the write access needed in /tmp so it will fail pretty quickly otherwise.

WhiteWolf1776 10-11-2013 10:16 PM

-current is th testing, and yep, things break every now and then. Once it hits beta, fairly stable tho. I've had it on my laptop for some time as it needed newer kernels and libs than 14 had.

If you wish, slackpkg can update you (although I usually will recommend using alienbobs mirror current script to get a local copy just in case the update isn't smooth)

The reason I asked if you used 'su -' instead of just 'su' is the end and paths. For several SlackBuilds, you need to be sure you so with a full login shell, etc.

flokofcgulls 10-12-2013 09:40 AM

I'll give the upgrade to -current some thought, not sure if that's the best way to go since I hear that 14.1 isn't too far off, and then I assume the new -current will be back to a pre-beta stage.

I didn't realize that 'su -' and 'su' were different, I thought you just meant if I was building as root. I went and read up on the '-' option a little bit this morning in the GNU documentation, think I get the general idea. So to re-answer your question....no, I was not doing that.

So I just tried it again, using 'su -' instead of just 'su', and it still fails at the same spot, same error.


All times are GMT -5. The time now is 03:16 AM.