Bug 385363 – media-video/mkvtoolnix-4.9.1 fails to build

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Nick White 2011-10-02 11:02:57 UTC]

Created attachment 288533 [details]
Build output

When I try to build the newest x86 stable mkvtoolnix, 4.9.1, it reliably fails when linking mkvmerge. There are several undefined references to various parts of boost.

Attached is build output and the output of 'cave info mkvtoolnix boost'

[Comment 1 Nick White 2011-10-02 11:03:41 UTC]

Created attachment 288535 [details]
cave info mkvtoolnix boost

[Comment 2 Tim Harder 2011-10-02 22:05:50 UTC]

Since you have 4 different versions of boost installed, which version of boost do you have selected as the default via eselect?

[Comment 3 Tim Harder 2011-10-02 22:09:28 UTC]

(In reply to comment #2)
> Since you have 4 different versions of boost installed, which version of boost
> do you have selected as the default via eselect?

The point being mkvtoolnix-4.9.1 requires >=dev-libs/boost-1.36.0, but it looks like you have boost-1.35.0 still installed and it may be trying to build against that if its set as the default.

[Comment 4 Nick White 2011-10-03 07:12:32 UTC]

(In reply to comment #2)
> Since you have 4 different versions of boost installed, which version of boost
> do you have selected as the default via eselect?

I thought that may be the issue, too. However it looks like it's boost 1.46, as it's mentioned throughout the src_compile section of the build log. That said, though, I'll uninstall boost-1.35 tonight anyway, in case it helps.

[Comment 5 Tim Harder 2011-10-04 01:45:03 UTC]

(In reply to comment #4)
> I thought that may be the issue, too. However it looks like it's boost 1.46, as
> it's mentioned throughout the src_compile section of the build log.

Sure, the header includes are pulled in fine, but that's not the issue since you are running into link errors so it may be trying to link against the wrong version.

[Comment 6 Nick White 2011-10-04 17:46:12 UTC]

(In reply to comment #5)
> Sure, the header includes are pulled in fine, but that's not the issue since
> you are running into link errors so it may be trying to link against the wrong
> version.

OK, thanks for the tip, the build succeeded this time.

Setting a high enough version of boost using eselect did the trick just fine. I didn't realise boost usage was configured with eselect; I presumed the package would just select an appropriate one.

Thanks for the help radhermit.