Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 569718 - media-gfx/enblend-4.1.3-r1: -- Performing Test VIGRA_SETIMAGEINDEX - Failed
Summary: media-gfx/enblend-4.1.3-r1: -- Performing Test VIGRA_SETIMAGEINDEX - Failed
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-25 13:35 UTC by niks1024
Modified: 2015-12-25 14:04 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
build.log.gz (media-gfx:enblend-4.1.3-r1:20151225-130720.log.gz,4.16 KB, application/x-gzip)
2015-12-25 13:35 UTC, niks1024
Details

Note You need to log in before you can comment on or make changes to this bug.
Description niks1024 2015-12-25 13:35:15 UTC
This bug might not be what it seems as I'm only rebuilding media-gfx/enblend-4.1.3-r1 (previously built-on 23:24:46 2015.08.14.) while the installed media-libs/vigra-1.10.0 was last built 2 weeks before that enblend build (04:42:24 2015.07.29.) meaning that either enblend sources has silently changed (obviously unlikely as it would require new hashes for the ebuild to work at all) or what actually is broken is the VIGRA_SETIMAGEINDEX test itself.

I'm on hardened/linux/amd64 profile but using only the hardened toolchain without grsec or anything like that other than vanilla Tomoyo and Yama and neither of thetwo seem to have been triggered in this case. My compiler is gcc (Gentoo Hardened 5.3.0 p1.0, pie-0.6.5) 5.3.0 and my arch is ~amd64.

Reproducible: Always

Steps to Reproduce:
1. emerge -v1 =media-gfx/enblend-4.1.3-r1
Actual Results:  
-- Performing Test VIGRA_SETIMAGEINDEX
-- Performing Test VIGRA_SETIMAGEINDEX - Failed
CMake Error at ConfigureChecks.cmake:69 (message):
  Vigra library too old
Comment 1 niks1024 2015-12-25 13:35:53 UTC
Created attachment 420776 [details]
build.log.gz
Comment 2 niks1024 2015-12-25 14:04:03 UTC
Rebuilding vigra fixed the issue so I'll put it to down to C++ ABI break or something.