LinuxQuestions.org - NVIDIA + Bumblebee: Failed to build the binaries

- Linux - Hardware (https://www.linuxquestions.org/questions/linux-hardware-18/)

- - NVIDIA + Bumblebee: Failed to build the binaries (https://www.linuxquestions.org/questions/linux-hardware-18/nvidia-bumblebee-failed-to-build-the-binaries-4175490184/)

NVIDIA + Bumblebee: Failed to build the binaries

I tried to install bumblebee from source following these instructions but failed to build the binaries
https://github.com/Bumblebee-Project...tall-and-usage

This is what I did...

Code:

# ./configure CONF_DRIVER=nvidia CONF_DRIVER_MODULE_NVIDIA=nvidia CONF_LDPATH_NVIDIA=/usr/lib64:/usr/lib CONF_MODPATH_NVIDIA=/usr/lib64/xorg/modules

checking for a BSD-compatible install... /usr/bin/install -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 how to create a pax tar archive... gnutar

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 for style of include used by make... GNU

checking dependency style of gcc... gcc3

checking whether gcc and cc understand -c and -o together... yes

checking for help2man... no

configure: WARNING: cannot find help2man, you will not be able to generate manpages

checking for pkg-config... /usr/bin/pkg-config

checking pkg-config is at least version 0.9.0... yes

checking for x11... yes

checking for glib... yes

checking for libbsd... yes

configure: creating ./config.status

config.status: creating Makefile

config.status: executing depfiles commands

Code:

# make

depbase=`echo src/bbsocket.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`;\

gcc -DPACKAGE_NAME=\"bumblebee\" -DPACKAGE_TARNAME=\"bumblebee\" -DPACKAGE_VERSION=\"3.2.1\" -DPACKAGE_STRING=\"bumblebee\ 3.2.1\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DCONF_XDISP=\":8\" -DCONF_SOCKPATH=\"/var/run/bumblebee.socket\" -DCONF_GID=\"bumblebee\" -DCONF_KEEPONEXIT=\"false\" -DCONF_FALLBACKSTART=\"false\" -DCONF_VGLCOMPRESS=\"proxy\" -DCONF_TURNOFFATEXIT=\"false\" -DCONF_BRIDGE=\"auto\" -DCONF_PRIMUS_LD_PATH=\"/usr/lib/primus:/usr/lib32/primus\" -DCONF_PIDFILE=\"/var/run/bumblebeed.pid\" -DCONF_PM_METHOD=\"auto\" -DCONF_DRIVER=\"nvidia\" -DCONF_DRIVER_MODULE_NVIDIA=\"nvidia\" -DCONF_LDPATH_NVIDIA=\"/usr/lib64:/usr/lib\" -DCONF_MODPATH_NVIDIA=\"/usr/lib64/xorg/modules\" -DDAEMON_NAME=\"bumblebeed\" -DPACKAGE=\"bumblebee\" -DVERSION=\"3.2.1\" -DWITH_PIDFILE=1 -I. -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DCONFIG_FILE='"/usr/local/etc/bumblebee/bumblebee.conf"' -DCONF_XORG='"/usr/local/etc/bumblebee/xorg.conf.DRIVER"' -DCONF_XORG_DIR='"/usr/local/etc/bumblebee/xorg.conf.d"' -Wall -Waggregate-return -Wmissing-declarations -Wmissing-prototypes -Wredundant-decls -Wshadow -Wstrict-prototypes -Winline -Wformat=2 -pipe -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -Wextra -funsigned-char -DGITVERSION='"3.2.1"' -g -O2 -MT src/bbsocket.o -MD -MP -MF $depbase.Tpo -c -o src/bbsocket.o src/bbsocket.c &&\

mv -f $depbase.Tpo $depbase.Po

src/bbsocket.c: In function ‘socketConnect’:

src/bbsocket.c:51: error: ‘SOCK_CLOEXEC’ undeclared (first use in this function)

src/bbsocket.c:51: error: (Each undeclared identifier is reported only once

src/bbsocket.c:51: error: for each function it appears in.)

src/bbsocket.c: In function ‘socketServer’:

src/bbsocket.c:175: error: ‘SOCK_CLOEXEC’ undeclared (first use in this function)

make: *** [src/bbsocket.o] Error 1

Code:

some additional info...

Distro: CentOS 5.9

Kernel: 2.6.18-348.el5 x86_64

Manufacturer and model: ThinkPad Edge E330 3354CTO

Bumblebee version: bumblebee-3.2.1

Graphic Cards:

# lspci -vnn | grep '\''[030[02]\]'

00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])

01:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:1058] (rev a1) (prog-if 00 [VGA controller])

Please help to resolve the error. Thanks.

still the same problem ?
4 weeks ago you posted this
http://www.linuxforums.org/forum/har...os5-rhel5.html
and this here
http://www.unix.com/hardware/241684-...os5-rhel5.html

and on Dec. 2 2013 you posted this
http://www.linuxquestions.org/questi...-a-4175486612/

you need a newer kernel than is in the rather old RHEL/CentOS/SL 5.9 ( by the way 5.10 is the current in the old 5 series )

but CentOS , even the curent 6.5 is not a good option on a laptop

rhel/cent/sl was never meant to be ran on a laptop.Now some laptops will run it mostly well
but some will never be able to install it ( with a gui) .

if you MUST use a redhat based distro on a laptop have a look at fedora
or maybe even CentOS 6.5
( but there are no guarantees that cent6 will even fully work or even install on a laptop

Not the same problem... I managed to configure with correct path but now the build error is different!
Then again, cannot use newer kernels because the software tools I use are based on older stable kernels, although the tools are the latest. And btw centOS 6.x runs just fine on most laptops!

Things change with time... if you don't adapt the time will change you. This is true for Linux on laptops and the truth, Intel is losing more than 50% market share fast which they are not ready to admit!

No one knows the solution?
Is the error only because of the old kernel?

what version of glibc do you have?

glibc-2.5-107.x86_64
glibc-common-2.5-107.x86_64
glibc-devel-2.5-107.x86_64
glibc-headers-2.5-107.x86_64

glib2-2.12.3
glib2-devel-2.12.3

i think your glibc are too old, SOCK_CLOEXEC is defined in /usr/include/bits/socket_type.h, present in glibc-2.18

with a fast find, first version is 2.9 with /usr/include/bits/socket.h, this is the minimal upgrade

Ok thanks, then the next dumb question how can I upgrade my glibc keeping the same kernel. If I can download glibc-2.9 rpm can I simply install it?

i don't know how centos packaging works, but i won't upgrade glibc, it's better to install a new version, waiting all things to work good, then delete old libraries; if you have some noise (binaries with shared lib dependencies broken), you can step back easliy.

normally, glibc libraries have symlinks that don't bump it's version, like libm.so.6 -> libm-2.18.so; if in your system, the symlink to libm-2.5.so is libm.so.6, you don't have any problem in upgrading this libraries, as programs will load it using the symlink name. this library is in /lib(64) directory