Bug 519848 – media-gfx/blender-2.69 - .../work/blender-2.69/extern/libmv/libmv-capi.cc:92:2: error: ‘SetCommandLineOption’ is not a member of ‘google’

• Status: RESOLVED OBSOLETE
• Product: Gentoo Linux

[Description Sebastian Sledz 2014-08-13 20:39:39 UTC]

Compilation of Blender in version 0.69 fail with:
>=dev-cpp/gfags-2.1
>=dev-cpp/glog-0.3.3

Problem resolution is masking both libraries for this version.

Also alredy builded version of Blender will won't run anymore after updating this libraries to latest versions.

[Comment 1 Ben Kohler 2014-08-13 20:43:59 UTC]

This looks like bug #517134, try rebuilding glog after the gflags update.

[Comment 2 Jeroen Roovers (RETIRED) 2014-08-13 23:03:13 UTC]

1) Please post your `emerge --info' output in a comment.
2) Please attach the entire build log to this bug report.

[Comment 3 Sebastian Sledz 2014-08-14 16:26:47 UTC]

Created attachment 382896 [details]
emerge info

[Comment 4 Sebastian Sledz 2014-08-14 16:53:21 UTC]

Created attachment 382898 [details]
blender-2.69-r1  build.log.lzma

Build log for failed Blender-2.69-r1 compilation.

[Comment 5 Sebastian Sledz 2014-08-14 17:07:13 UTC]

@Ben Kohler, rebuilding glog in latest version doesn't resolve problem. New version breaks API compatibility with older versions. Alos, yes this bug looks similary because is caused by breaked API compability. Also resolution linked bug is just doing deep updates instead updating single packages.

I write about two libraries because glog also require older version of gflags. In short:
- media-gfx/blender-0.69 require older version of dev-cpp/glog than 0.3.3 (tested works with 0.3.2)
- dev-cpp/glog require older version of dev-cpp/gflags than 2.1 (tested, works with 2.0-r1) - glog-0.3.2 compilation fails with >=gflags-2.1

[Comment 6 Sebastian Sledz 2014-08-14 17:21:07 UTC]

Created attachment 382900 [details]
=dev-cpp/glog-0.3.2 build.log.lzma

[Comment 7 Julian Ospald 2014-08-15 10:44:14 UTC]

0.69?

[Comment 8 Sebastian Sledz 2014-08-15 11:05:14 UTC]

0.70

[Comment 9 Sebastian Sledz 2014-08-15 11:07:22 UTC]

My bad. 2.69. Also 2.70 has this same problem. I was not test 2.71 (require python-3.4).

[Comment 10 Julian Ospald 2014-08-15 11:37:31 UTC]

well, we broke it

glog is bundled in blender. One thing I could do is provide a "system-deps" or "bundled-deps" use flags so that users can at least get it working somehow.

[Comment 11 Nick Bowler 2014-12-11 17:04:18 UTC]

gflags-2.0 has been gone from the tree for over a month now and affected versions have been completely unbuildable for just as long.

They should be fixed or punted.

Unfortunately python 3.4 is still not enabled by default which leaves blender-2.69-r1 the only version that is straightforward to install.

[Comment 12 Julian Ospald 2014-12-16 15:59:18 UTC]

+  16 Dec 2014; Julian Ospald <[e-mail]> -blender-2.69-r1.ebuild,
+  -blender-2.71-r2.ebuild, -blender-2.72-r1.ebuild,
+  -files/07-blender-2.68-sse2.patch,
+  -files/02-blender-2.68-unbundle-colamd.patch,
+  -files/05-blender-2.68-unbundle-eigen3.patch,
+  -files/04-blender-2.68-unbundle-glog.patch,
+  -files/04-blender-2.71-r2-unbundle-glog.patch,
+  -files/09-blender-2.72-unbundle-minilzo.patch:
+  rm old