[Bug 244962] emulators/virtualbox-ose-additions mount -t vboxsf Operation not supported by device
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244962 --- Comment #3 from groenv...@acm.org --- The kernel does not offer bcmp: $ nm /boot/kernel/kernel|grep -i bcmp 80cb4610 T timingsafe_bcmp The port links vboxvfs.ko with a library that references bcmp $ cat /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-5.2.34/out/freebsd.amd64/release/obj/vboxvfs/vboxvfs.dep define vboxvfs_CMDS_PREV_ @kmk_builtin_rm -f -- /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-5.2.34/out/freebsd.amd64/release/obj/vboxvfs/vboxvfs.dep /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-5.2.34/out/freebsd.amd64/release/obj/vboxvfs/vboxvfs.ko /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-5.2.34/out/freebsd.amd64/release/obj/vboxvfs/vboxvfs.map ld -d --warn-common -m elf_x86_64_fbsd -r -o /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-5.2.34/out/freebsd.amd64/release/obj/vboxvfs/vboxvfs.ko /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-5.2.34/out/freebsd.amd64/release/obj/vboxvfs/vboxvfs_vfsops.o /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-5.2.34/out/freebsd.amd64/release/obj/vboxvfs/vboxvfs_vnops.o /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-5.2.34/out/freebsd.amd64/release/obj/vboxvfs/vboxvfs_prov.o /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-5.2.34/out/freebsd.amd64/release/lib/additions/VBoxGuestR0Lib.a /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-5.2.34/out/freebsd.amd64/release/lib/additions/RuntimeGuestR0.a awk -f /usr/src/sys/conf/kmod_syms.awk /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-5.2.34/out/freebsd.amd64/release/obj/vboxvfs/vboxvfs.ko /dev/null | xargs -J% objcopy % /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-5.2.34/out/freebsd.amd64/release/obj/vboxvfs/vboxvfs.ko endef $ nm /usr/ports/emulators/virtualbox-ose-additions/work/VirtualBox-5.2.34/out/freebsd.amd64/release/lib/additions/RuntimeGuestR0.a | grep -B13 bcmp strformatrt.o: U VBoxGuest_RTStrFormat U VBoxGuest_RTStrFormatNumber r _ZL13g_szHexDigits 2060 t _ZL15rtstrFormatIPv6PFmPvPKcmES_PK10RTUINT128U r _ZZ13rtstrFormatRtE12s_wszBigNull 0280 r _ZZ13rtstrFormatRtE8s_aTypes 0870 r _ZZ13rtstrFormatRtE8s_aTypes_0 0850 r _ZZ13rtstrFormatRtE8s_szNull 0857 r _ZZ13rtstrFormatRtE8s_szTrue 085d r _ZZ13rtstrFormatRtE9s_szFalse U __start_set_pcpu U __stop_set_pcpu U bcmp Someone with an understanding of FreeBSD kernel modules will have to explain where things went sideways. John groenv...@acm.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"
Zoom and linuxolator
Hi, emulation@ ! I'm trying to start Linux version of Zoom client [1] on my FreeBSD (latest head) and I have two questions: 1. Why I need to copy all libraries from Zoom binary folder to /compat/linux/lib64 because they are not found when application starts. 2. After all shared libraries are copied application starts and crashed with following error: zoom started. Client: Breakpad is using Single Client Mode! client fd = -1 [CZPClientLogMgr::LogClientEnvironment] [MacAddr: ][client: Linux][OS: CentOS Linux 7 (Core)][Hardware: CPU Core:8 Frenquency:2.2 G Memory size:16227MB CPU Brand:Intel(R) Core(TM) i7-4702MQ CPU @ 2.20GHz GPU Brand:][Req ID: ] Linux Client Version is 3.5.361976.0301 QSG_RENDER_LOOP is XDG_CURRENT_DESKTOP = KDE; GDMSESSION = Graphics Card Info:: Zoom package arch is 64bit, runing OS arch is x86_64 AppIconMgr::systemDesktopName log Desktop Name: /usr/local/share/xsessions/plasma qt.svg: link image0 hasn't been detected! qt.svg: :/images/wechat.svg:10:6: Could not resolve property: pattern0 setsockopt(SOL_SOCKET, SO_PASSCRED): Протокол недоступен Assertion 'pthread_mutex_unlock(&m->mutex) == 0' failed at pulsecore/mutex-posix.c:108, function pa_mutex_unlock(). Aborting. ExceptionHandler::SendContinueSignalToChild sys_write failed:Обрыв канала ExceptionHandler::GenerateDump waitpid failed:Неправильный дескриптор файла ExceptionHandler::WaitForContinueSignal sys_read failed:Неправильный дескриптор файла Abort (core dumped) ___ 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"
Re: Zoom and linuxolator
Quoting Alexandr Krivulya (from Fri, 27 Mar 2020 15:21:49 +0200): Hi, emulation@ ! I'm trying to start Linux version of Zoom client [1] on my FreeBSD (latest head) and I have two questions: 1. Why I need to copy all libraries from Zoom binary folder to /compat/linux/lib64 because they are not found when application starts. Libraries (no matter if for FreeBSD or Linux) are searched in fixed locations (if they are linked into a binary the normal way). You can add other locations either globally by adding it to the ldconfig path (for linux it is a different setting than for FreeBSD binaries), or you can set the LD_LIBRARY_PATH variable to add the new location per program. For FreeBSD see "man ldconfig" (for LD_LIBRARY_PATH, will be picked up by linux and FreeBSD, so don't set it globally but only for specific programs) and "man rc.conf" (for ldconfig_* variables which denote the global search path for FreeBSD). For Linux I don't find the right global variable right now. We used to have one. 2. After all shared libraries are copied application starts and crashed with following error: Assertion 'pthread_mutex_unlock(&m->mutex) == 0' failed at pulsecore/mutex-posix.c:108, function pa_mutex_unlock(). Aborting. Unfortunately this doesn't give enough info about what's wrong. Someone would have to investigate with ktrace and/or DTrace. Bye, Alexander. -- http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.orgnetch...@freebsd.org : PGP 0x8F31830F9F2772BF pgpb6tfwXfQyS.pgp Description: Digitale PGP-Signatur
Re: Zoom and linuxolator
27.03.20 19:29, Alexander Leidinger пишет: Quoting Alexandr Krivulya (from Fri, 27 Mar 2020 15:21:49 +0200): Hi, emulation@ ! I'm trying to start Linux version of Zoom client [1] on my FreeBSD (latest head) and I have two questions: 1. Why I need to copy all libraries from Zoom binary folder to /compat/linux/lib64 because they are not found when application starts. Libraries (no matter if for FreeBSD or Linux) are searched in fixed locations (if they are linked into a binary the normal way). You can add other locations either globally by adding it to the ldconfig path (for linux it is a different setting than for FreeBSD binaries), or you can set the LD_LIBRARY_PATH variable to add the new location per program. Is it true even when executable and needed libraries are in the same directory? In my case it is a same directory. ___ 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"
Re: Zoom and linuxolator
Quoting Alexandr Krivulya (from Fri, 27 Mar 2020 20:27:21 +0200): 27.03.20 19:29, Alexander Leidinger пишет: Quoting Alexandr Krivulya (from Fri, 27 Mar 2020 15:21:49 +0200): Hi, emulation@ ! I'm trying to start Linux version of Zoom client [1] on my FreeBSD (latest head) and I have two questions: 1. Why I need to copy all libraries from Zoom binary folder to /compat/linux/lib64 because they are not found when application starts. Libraries (no matter if for FreeBSD or Linux) are searched in fixed locations (if they are linked into a binary the normal way). You can add other locations either globally by adding it to the ldconfig path (for linux it is a different setting than for FreeBSD binaries), or you can set the LD_LIBRARY_PATH variable to add the new location per program. Is it true even when executable and needed libraries are in the same directory? In my case it is a same directory. Yes, "." is not in ldconfig_path, you can check yourself via grep ldconfig_path /etc/defaults/rc.conf /etc/rc.conf Bye, Alexander. -- http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.orgnetch...@freebsd.org : PGP 0x8F31830F9F2772BF pgpN8kisAC0S8.pgp Description: Digitale PGP-Signatur
Re: Zoom and linuxolator
On 2020-03-27 14:27, Alexandr Krivulya wrote: Is it true even when executable and needed libraries are in the same directory? In my case it is a same directory. What are the executable's elf RPATH / RUNPATH ? IIRC this can be configured to allow searching in ".". Theron ___ 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 244962] emulators/virtualbox-ose-additions mount -t vboxsf Operation not supported by device
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244962 Mateusz Guzik changed: What|Removed |Added CC||m...@freebsd.org --- Comment #4 from Mateusz Guzik --- There is no bcmp symbol on amd64 for almost 2 years now. In sys/systm.h there is: int bcmp(const void *b1, const void *b2, size_t len); [..] #define bcmp(b1, b2, len) __builtin_memcmp((b1), (b2), (len)) The first line should probably get removed, but it should not be affecting vbox. vbox likes to *disable* several warnings. Thus what most likely happens is that some place using bcmp *fails* to include the systm.h header, due to warns disabled nobody is even told and the compiler ends up generating a call to bcmp (instead of memcmp, or no call in the first place). Thus someone(tm) should make sure the header is included in files which end up doing bcmp. Also will not hurt to make sure the build environment is clean and up to date -- if thep ort pulls in *OLD* files it will only see bcmp declared, but no macro telling it to use __builtin_memcmp and then it will stick to generating the call. -- 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"
