FS#45163 - [freeimage] Can't Load/Save JPEG-XR Images on 64bit Platform

Attached to Project: Community Packages
Opened by nyfair (nyfair) - Monday, 01 June 2015, 07:26 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Tuesday, 22 December 2015, 08:13 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Steps to reproduce:

Compile the following sample code for image format conversion
#include <stdio.h>
#include <stdlib.h>
#include "FreeImage.h"
int main(int argc, char *argv[]) {
int flag = (argc > 3) ? atoi(argv[3]) : 0;
FREE_IMAGE_FORMAT fifin = FreeImage_GetFIFFromFilename(argv[1]);
FREE_IMAGE_FORMAT fifout = FreeImage_GetFIFFromFilename(argv[2]);
FIBITMAP *dib = FreeImage_Load(fifin, argv[1]);
FreeImage_Save(fifout, dib, argv[2], flag);
FreeImage_Unload(dib);
return 0;
}

It fails when try to load or save jpeg-xr images.
I also build FreeImage from source (not from PKGBUILD), it has no problem.
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Tuesday, 22 December 2015, 08:13 GMT
Reason for closing:  No response
Additional comments about closing:  Closing for now. If it remains a problem, please reopen.
Comment by Sven-Hendrik Haase (Svenstaro) - Saturday, 11 July 2015, 16:10 GMT
What is your processor?
Comment by Sven-Hendrik Haase (Svenstaro) - Sunday, 26 July 2015, 18:30 GMT
You have to work with me here, I'm pretty sure it's CPU specific issue but I need to know which one.
Comment by nyfair (nyfair) - Monday, 27 July 2015, 18:30 GMT
This is not a CPU specific issue.
I use 5960x and can also reproduce the problem on other CPUs.
I also have no problem to build it with GCC 5.1/5.2.

I think the problem is caused by your CFLAGS on guiddef.h and JXRGlue.h because it always return wrong GUID for input/output image formats.
Comment by Sven-Hendrik Haase (Svenstaro) - Friday, 11 December 2015, 17:07 GMT
Might have been a gcc issue. Does this work now with the new package built by gcc 5.3?

Loading...