Re: glxinfo works, /compat/linux/usr/bin/glxinfo - does not
On 17.06.20 13:42, Tijl Coosemans wrote: On Wed, 17 Jun 2020 12:26:25 -0400 "Mikhail T." wrote: On 17.06.20 11:58, Tijl Coosemans wrote: Does "glxinfo | grep glvnd" print anything? Yes, both of them print the same thing now: root@macropod:/green/home/mi # glxinfo | grep glvnd GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_libglvnd, root@macropod:/green/home/mi # /compat/linux/usr/bin/glxinfo | grep glvnd GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_libglvnd, Does everything still work if you install linux-c7-dri but remove /compat/linux/usr/lib/libGLX_system.so.0 and /compat/linux/usr/lib64/libGLX_system.so.0? I just installed linux-c7-dri, and things continue to work even without removing GLX_system... I do not understand, why: % env LANG=C ls -l /compat/linux/usr/lib*/libGLX* lrwxr-xr-x 1 root wheel 15 Jun 16 13:52 /compat/linux/usr/lib/libGLX.so.0 -> libGLX.so.0.0.0 -rwxr-xr-x 1 root wheel 70016 Oct 30 2018 /compat/linux/usr/lib/libGLX.so.0.0.0 lrwxr-xr-x 1 root wheel 24 Jun 16 20:39 /compat/linux/usr/lib/libGLX_indirect.so.0 -> libGLX_nvidia.so.390.132 lrwxr-xr-x 1 root wheel 20 May 12 12:39 /compat/linux/usr/lib/libGLX_mesa.so.0 -> libGLX_mesa.so.0.0.0 -rwxr-xr-x 1 root wheel 583660 May 12 12:40 /compat/linux/usr/lib/libGLX_mesa.so.0.0.0 lrwxr-xr-x 1 root wheel 24 Jun 17 13:56 /compat/linux/usr/lib/libGLX_nvidia.so.0 -> libGLX_nvidia.so.390.132 -rw-r--r-- 1 root wheel 1129756 Jun 16 20:39 /compat/linux/usr/lib/libGLX_nvidia.so.390.132 lrwxr-xr-x 1 root wheel 16 Jun 17 13:56 /compat/linux/usr/lib/libGLX_system.so.0 -> libGLX_mesa.so.0 lrwxr-xr-x 1 root wheel 15 Jun 16 13:52 /compat/linux/usr/lib64/libGLX.so.0 -> libGLX.so.0.0.0 -rwxr-xr-x 1 root wheel 75040 Oct 30 2018 /compat/linux/usr/lib64/libGLX.so.0.0.0 lrwxr-xr-x 1 root wheel 24 Jun 16 20:39 /compat/linux/usr/lib64/libGLX_indirect.so.0 -> libGLX_nvidia.so.390.132 lrwxr-xr-x 1 root wheel 20 May 12 12:30 /compat/linux/usr/lib64/libGLX_mesa.so.0 -> libGLX_mesa.so.0.0.0 -rwxr-xr-x 1 root wheel 502120 May 12 12:32 /compat/linux/usr/lib64/libGLX_mesa.so.0.0.0 lrwxr-xr-x 1 root wheel 24 Jun 17 13:56 /compat/linux/usr/lib64/libGLX_nvidia.so.0 -> libGLX_nvidia.so.390.132 -rw-r--r-- 1 root wheel 1268120 Jun 16 20:39 /compat/linux/usr/lib64/libGLX_nvidia.so.390.132 lrwxr-xr-x 1 root wheel 16 Jun 17 13:56 /compat/linux/usr/lib64/libGLX_system.so.0 -> libGLX_mesa.so.0 % /compat/linux/usr/bin/glxinfo | grep glvnd GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_libglvnd, Yours, -mi ___ freebsd-emulation@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
[Bug 247020] [panic][lixux]: kernel panic in linux_thread_detach at /usr/src/sys/compat/linux/linux_fork.c:462
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247020 --- Comment #9 from commit-h...@freebsd.org --- A commit references this bug: Author: kib Date: Thu Jun 18 20:49:57 UTC 2020 New revision: 362342 URL: https://svnweb.freebsd.org/changeset/base/362342 Log: Fix execution of linux binary from multithreaded non-Linux process. If multithreaded non-Linux process execs Linux binary, then non-Linux threads different from the one that execing are cleared by single-threading at boundary, and then terminating them in post_execve(). Since at that time the process is already switched to linux ABI, linuxolator is involved in the thread clearing on boundary, but cannot find the emul data. Handle it by pre-creating emuldata for all threads in the execing process. Also remove a code in linux_proc_exec() handler that cleared emul data for other threads when execing from multithreaded Linux process. It is excessive. PR: 247020 Reported by: Martin FIlla Reported by: Henrique L. Amorim, Independent Security Researcher Reported by: Rodrigo Rubira Branco (BSDaemon), Amazon Web Services Reviewed by: markj Tested by:trasz Sponsored by: The FreeBSD Foundation MFC after:1 week Differential revision:https://reviews.freebsd.org/D25293 Changes: head/sys/compat/linux/linux_emul.c -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-emulation@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
[Bug 247020] [panic][lixux]: kernel panic in linux_thread_detach at /usr/src/sys/compat/linux/linux_fork.c:462
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247020 Ed Maste changed: What|Removed |Added Status|New |In Progress Assignee|emulat...@freebsd.org |k...@freebsd.org -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-emulation@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
How to properly install a Linux desktop app?
Hello!
I'm preparing a port of a Linux application (Zoom conferencing client).
The vendor (zoom.us) offers RPMs for both x86_64 and i686, which makes
it tempting to just USE_LINUX_RPM. However, that knob unconditionally
turns on the USE_LINUX_PREFIX, which bsd.port.mk says /not/ to use "for
leaf ports (e.g. a game or program)".
Not using the USE_LINUX_PREFIX, poses another challenge. Zoom comes with
quite a few Linux libraries of its own, which are all dumped into a
non-standard location. My port is installing a
/compat/linux/etc/ld.so.conf.d/zoom.conf listing that location, but that
will be ignored unless ldconfig -- a Linux one -- is invoked, wouldn't
it be?
Finally, if I do rely USE_LINUX_PREFIX and the bulk of the port gets
installed under /compat/linux/opt/zoom, there is a problem with the
DESKTOP_ENTRIES -- because they would be under /compat/linux too,
instead of under ${LOCALBASE}.
usr/share/applications/Zoom.desktop
usr/share/mime/packages/zoom.xml
usr/share/pixmaps/Zoom.png
usr/share/pixmaps/application-x-zoom.png
(I think, the current setting of DESKTOPDIR based on PREFIX is incorrect
-- it should be under LOCALBASE instead. But that's a separate story.)
What are my options with this new port?
1. Follow the examples of existing ports (like citrix_ica):
1. Do not use the USE_LINUX_RPM.
2. Do not bother with Linux' ldconfig.
3. Instead of ${LINUXBASE}/etc/ld.so.conf.d/zoom.conf, create the
${PREFIX}/bin/zoom script with LD_LIBRARY_PATH setting. (This
will keep the libraries bundled with Zoom unavailable to other
Linux programs.)
2. An alternative method:
1. Do declare the USE_LINUX_RPM (and set the SRC_DISTFILES to empty).
2. Install the ${LINUXBASE}/etc/ld.so.conf.d/zoom.conf and declare
the USE_LDCONFIG. (This will make the Zoom-libraries available
to other Linux apps.)
3. Explicitly set DESKTOPDIR based on LOCALBASE.
Opinions? Thank you! Yours,
-mi
___
freebsd-emulation@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscr...@freebsd.org"
