Summary: | media-gfx/exiv2-0.23[contrib] fails to build with dev-libs/boost-1.51 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Chris Smith <chris> |
Component: | Current packages | Assignee: | Stefan Briesenick (RETIRED) <sbriesen> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | chris+gentoo-bugzilla, dev, help, renatogallo, transacid, yamadharma, zeekec |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 425188 | ||
Attachments: |
build log
exiv2-0.23-r2.ebuild exiv2-0.23-boost-fs-contrib.patch |
Description
Chris Smith
2012-11-01 21:08:17 UTC
Created attachment 327996 [details]
build log
build log
Created attachment 328058 [details] exiv2-0.23-r2.ebuild Please test it with this ebuild and corresponding patch. This blocks bug #437432. Created attachment 328060 [details, diff]
exiv2-0.23-boost-fs-contrib.patch
For the records: original causing this bug #357605. The fix was setting a macro to stick to FS version 2. does this patch also works with boost < 1.51? There're some packages broken now woth boost-1.51. app-text/sigil and media-gfx/sfftobmp were the first I recognized by myself. furthermore: is there a quick overview, what has changed in 1.51 from a programmers point of view? I only tested it with the new boost 1.49.0-r2, I didn't check what changes were introduced with the new boost and new -rX. I only removed the BOOST_FILESYSTEM_VERSION=2 macro and made a proper patch that fixes this workaround (for me). Reported it also to upstream: http://dev.exiv2.org/issues/865 Confirming. Same problem, different versions however: media-gfx/exiv2-0.21.1-r1 dev-libs/boost-1.52.0-r4 Can you please backport this to 0.21.1 as well (I suppose with version "0.21.1-r3", since "-r2" already exists, but is marked unstable?) so that those with stable use flags are happy? I actually have ~amd64 for my boost because I use it in development, but most of my system is stable. BTW, the patch only fixed part of my problem, I didn't manage to get rid of the BOOST_FILESYSTEM_VERSION defined != 3 error, but I only copied & pasted part of the ebuild for 0.23-r2 (attached by Mario above) into a new 0.21.1-r3 ebuild and then got lazy and just ran USE="-contrib" Could you test this with the ebuild from bug #437432? I'd rather like to see 0.23 becoming stable as it introduces support for new cameras and lenses. Current stable is around 1.5 years old. Tested with: exiv2-0.23-r2.ebuild and exiv2-0.23-boost-fs-contrib.patch Working for me now. i can confirm the bug is solved by that ebuild and patch, i kindly request those to be added on tree please thank you Mario Kicherer you saved my system Tested with: exiv2-0.23-r2.ebuild and exiv2-0.23-boost-fs-contrib.patch Working for me now. Same for me exiv2-0.23 was broken after update to boost 1.51. It builds again with the provided files: exiv2-0.23-r2.ebuild and exiv2-0.23-boost-fs-contrib.patch fixed in CVS. |