Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#50293 - Complie imagemagick with 32 bit depth.
Attached to Project:
Arch Linux
Opened by Siddharth J Singh (dante666) - Sunday, 07 August 2016, 08:05 GMT
Last edited by Antonio Rojas (arojas) - Sunday, 07 August 2016, 09:15 GMT
Opened by Siddharth J Singh (dante666) - Sunday, 07 August 2016, 08:05 GMT
Last edited by Antonio Rojas (arojas) - Sunday, 07 August 2016, 09:15 GMT
|
DetailsDescription:
Compiling imagemagick --with-quantum-depth=16 results in the following warning in octave. Can we compile it using 32 bit depth? http://wiki.octave.org/GraphicsMagick (Please note that in the site it shows 8 bit depth and the solution is to compile with 16 bit depth. Probably for older times.) >>warning: your version of GraphicsMagick limits images to 16 bits per pixel" >>warning: called from >> imformats>default_formats at line 256 column 11 >> imformats at line 79 column 3 >> imageIO at line 106 column 11 >> imread at line 106 column 30 Additional info: * imagemagick version 6.9.5.4-1 Steps to reproduce: 1) Start Octave(tested with 4.0.3) 2) run imread("image.jpg") |
This task depends upon
Comment by Antonio Rojas (arojas) -
Sunday, 07 August 2016, 08:36 GMT
so, are you talking about imagemagick or about graphicsmagick? Because they are different things.
Comment by Siddharth J Singh (dante666) -
Sunday, 07 August 2016, 09:11 GMT
Yes, you are correct. My mistake, I got really confused. Closing!!