Date: Sun, 25 Oct 2020 12:31:23 +0100 From: Guido Falsi <mad@madpilot.net> To: Ronald Klop <ronald-lists@klop.ws>, vbox@freebsd.org Cc: "freebsd-x11@freebsd.org" <freebsd-x11@freebsd.org> Subject: Re: Undefined symbol "glXBindTexImageEXT" Message-ID: <e140360b-20a6-2f23-44c2-4eceaf830e4c@madpilot.net> In-Reply-To: <op.0s1b7ak0kndu52@joepie> References: <op.0s1b7ak0kndu52@joepie>
next in thread | previous in thread | raw e-mail | index | archive | help
On 25/10/20 09:51, Ronald Klop wrote: > Hi maintainer of virtualbox-ose-additions, > > After I saw > https://svnweb.freebsd.org/ports?view=revision&revision=553175 to fix > compiling with OpenGL support I tried it. > > 'Simple' X11 application like urxvt work, but more advanced like > xfce4-terminal or firefox crash very early with: > > ld-elf.so.1: /usr/local/lib/VBoxOGL.so: Undefined symbol > "glXBindTexImageEXT" > Explicitly disabling extensions was reported as making it build with the option enabled: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250315 Unluckily it is causing problems, so the option is now broken at runtime as you reported. Not sure if there is an easy fix or if fixing it (apart from updating to a newer virtualbox release) is at all possible at this point. An idea I'm going to try is manually aligning the broken includes to the new dri provided ones. Please give me a little time to cook up a patch for you to test. > What can I help to debug this? Not much to debug, that symbol is actually absent. But enabling the code to include that symbol causes the build to fail. > > BTW: does it matter if I use vboxvideo from drm-devel-kmod or not? With > and without it gives the same error. > Don't think it's related. -- Guido Falsi <mad@madpilot.net>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e140360b-20a6-2f23-44c2-4eceaf830e4c>