Date: Tue, 29 May 2018 05:45:32 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 228531] graphics/blender: fails to link with CYCLES Message-ID: <bug-228531-7788-LVpWOWgEJ3@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-228531-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-228531-7788@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=3D228531 --- Comment #3 from Shane <FreeBSD@ShaneWare.Biz> --- Created attachment 193808 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D193808&action= =3Dedit build fix workaround for graphics/blender Adding LLD_UNSAFE=3Dyes does not fix this. The quick workaround is to add WITH_CYCLES_LOGGING to CMAKE_OFF. When enabled this allows blender to be started with extra debugging output while rendering, unless gathering info = for a bug report disabling this makes no difference to the user. For a proper fix I'm not sure why this is happening. The conflict only happ= ens if devel/gflags is installed when building blender, which includes its own = copy of gflags source in extern/gflags. devel/gflags is now being installed via graphics/opencv. Both the port installed and blender included files have SetCommandLineOption(const char* name, const char* value) but lld is giving an error looking for=20 gflags::SetCommandLineOption(char const*, char const*) Both sources use "const char*" but lld is looking for "char const*" - but o= nly when gflags is installed from ports. Matching code to use SetCommandLineOption is also used in blenders intern/l= ibmv which doesn't get this error - libmv logging is always enabled and builds if CYCLES_LOGGING is disabled per the patch. The two blender sources using SetCommandLineOption are intern/libmv/intern/logging.cc -- this builds intern/cycles/util/util_logging.cpp -- this fails if gflags port is instal= led --=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-228531-7788-LVpWOWgEJ3>