Date: Mon, 20 Jun 2016 00:25:54 -0500 From: Jeremy <jeremy.m.cox@gmail.com> To: freebsd-x11@freebsd.org Subject: x11/nvidia-driver 367.27 issues with supplied library blob Message-ID: <CAPH9q1qU3h%2BPWEDuf_5A6g8R%2B72GiXRrS%2BhB2mu8HN0C9-eCuw@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
I recently updated the nvidia-driver obtained from the updated patch at https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201340 to test if it was working. It compiles and works fine with syscons (I haven't tried to use it with VT), and with xserver 1.18.3 and KDE 4.14.3. I am running FreeBSD 10.3 stable r302020 However, while recompiling virtualbox-ose 4.3.38_1, I encountered an error related to the nvidia-driver. From my limited understanding, the trouble is with the supplied libnvidia-glcore.so.1 blob from Nvidia, so it is nothing FreeBSD can do at its end. Virtualbox failed to compile and stopped at checking for mesa / GLU. When I checked the configure.log I found this issue at the end of it... ***** Checking Mesa / GLU ***** compiling the following source file: #include <cstdio> #include <X11/Xlib.h> #include <GL/glx.h> #include <GL/glu.h> ...bla bla bla clipped... } printf("found (inactive), OK.\n"); return 0; } using the following command line: clang++37 -g -O -Wall -o /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.38/.tmp_out /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.38/.tmp_src.cc "-L/usr/X11R6/lib -L/usr/X11R6/lib64 -L/usr/local/lib -lXext -lX11 -lGL -I/usr/local/include" //usr/local/lib/libnvidia-glcore.so.1: undefined reference to `nv_vasprintf_alloc' //usr/local/lib/libnvidia-glcore.so.1: undefined reference to `nv_vasprintf_free' //usr/local/lib/libnvidia-glcore.so.1: undefined reference to `nv_vasprintf_vsnprintf' clang-3.7: error: linker command failed with exit code 1 (use -v to see invocation) So my understanding is that it is an undefined reference issue with the supplied libnvidia-glcore.so.1 blob from the driver itself. If so, who should I contact from nvidia to report the issue? I looked at their FreeBSD developer board and it hasn't been active for 11 months. I know the community is trying to get the driver updated so they can finally land xserver 1.18 in the ports tree. This looks like an issue that needs to be fixed by nvidia now. Thank you all for your time. Jeremy Cox
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPH9q1qU3h%2BPWEDuf_5A6g8R%2B72GiXRrS%2BhB2mu8HN0C9-eCuw>