Date: Fri, 27 Mar 2020 21:32:33 +0000 From: bugzilla-noreply@freebsd.org To: vbox@FreeBSD.org Subject: [Bug 244962] emulators/virtualbox-ose-additions mount -t vboxsf Operation not supported by device Message-ID: <bug-244962-26505-6L8wCvsarl@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-244962-26505@https.bugs.freebsd.org/bugzilla/> References: <bug-244962-26505@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D244962 Mateusz Guzik <mjg@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mjg@FreeBSD.org --- Comment #4 from Mateusz Guzik <mjg@FreeBSD.org> --- There is no bcmp symbol on amd64 for almost 2 years now. In sys/systm.h the= re 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 declar= ed, but no macro telling it to use __builtin_memcmp and then it will stick to generating the call. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-244962-26505-6L8wCvsarl>