google-code-export / photivo

Automatically exported from code.google.com/p/photivo
GNU General Public License v3.0
3 stars 0 forks source link

Photivo and lcms #58

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Photivo version 2011-11-15(rev60ebb3c31a0d)+
(Ubuntu 11.10 amd64)

Compiles fine, but trying to run and got:

##################################
lcms: Error #12288; cmsWhitePointFromTemp: invalid temp
##################################

I've removed my ~/.photivo setting files, no effect.

Original issue reported on code.google.com by salvadh...@gmail.com on 18 Nov 2011 at 5:24

GoogleCodeExporter commented 9 years ago
I had this error with recent versions of Photivo in openSUSE too. It is because 
of Photivo linked with both lcms and lcms2. The dependence for lcms comes from 
GraphicsMagick. To eliminate it I had to compile GraphicsMagick with 
--without-lcms key.

Sergey.

Original comment by salser...@gmail.com on 18 Nov 2011 at 7:44

GoogleCodeExporter commented 9 years ago
Same issue on amd64 version of Lucid as of today.

Original comment by dominico...@gmail.com on 18 Nov 2011 at 6:52

GoogleCodeExporter commented 9 years ago
Sergey, that's the point. I've done some tests, and '--without-lcms' saves the 
world :)

Fixes (Ubuntu PPA) on the way.

Original comment by salvadh...@gmail.com on 18 Nov 2011 at 8:29

GoogleCodeExporter commented 9 years ago
Issue 59 has been merged into this issue.

Original comment by brother.john.gm@googlemail.com on 21 Nov 2011 at 5:38

GoogleCodeExporter commented 9 years ago
Same problem here.
It is annoying for packaged distributions that rely on existing builds of 
GraphicsMagick, which would need to be recompiled without a feature (LCMS). It 
won't be accepted.

Original comment by thibault...@gmail.com on 25 Nov 2011 at 9:11

GoogleCodeExporter commented 9 years ago
@thibault
So your distri’s repo has GM with quantum depth 16 and lcms1 support? Then 
we’d need to find out if lcms1 and lcms2 can somehow co-exist in one project 
because Photivo relies on lcms2. If that’s not possible then a custom build 
of GM with lcms2 instead of lcms1 (that’s what --without-lcms does if 
lcms2-devel is installed) is the only option.

Btw: Flickr thread for this issue: 
http://www.flickr.com/groups/photivo/discuss/72157628035952589/

Original comment by brother.john.gm@googlemail.com on 28 Nov 2011 at 11:03

GoogleCodeExporter commented 9 years ago
Well, since Fedora 16 GM is compiled with a bit depth of 16 bits. 
So I guess we have two options:
1) Rebuild GM with --without-lcms to force lcms2 only support (I don't know how 
that affects other packages though, any idea?)
2) Wait for the next GM release 1.4 which depends on lcms2 only. (This actually 
works ATM with a snapshot)

Thanks,

Original comment by thibault...@gmail.com on 28 Nov 2011 at 12:54

GoogleCodeExporter commented 9 years ago
Going with a custom GM and gradually switching to the packages from the distri 
repos as they come with 16bit/lcms2 is the best approach imo. That disrupts the 
current packaging process the least.

Original comment by brother.john.gm@googlemail.com on 28 Nov 2011 at 7:31

GoogleCodeExporter commented 9 years ago
Alright, thanks.
So the inclusion of photivo in Fedora will be delayed till we have GM 1.4 in.

Original comment by thibault...@gmail.com on 28 Nov 2011 at 7:51