[Bug 604702] Custom Fedora patch to mingw32-libjpeg breaks API

bugzilla at redhat.com bugzilla at redhat.com
Thu Jun 2 11:44:57 UTC 2011


Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=604702

--- Comment #7 from Erik van Pienbroek <erik-fedora at vanpienbroek.nl> 2011-06-02 07:44:56 EDT ---
@Kalev, comment 3: I have a mingw-libjpeg-turbo package ready, but it's already
based on the new guidelines (with win64 support). I could put it up for review,
but it won't build successfully at the moment because the mingw-w64 toolchain
isn't approved in Fedora yet

@Levente, comment 4: It's strange that you encountered an API/ABI difference
between libjpeg and libjpeg-turbo. When libjpeg-turbo was introduced in Fedora
14 no rebuilds were necessary at all as can be seen at
https://fedoraproject.org/wiki/Features/libjpeg-turbo

@Kalev, comment 5: That was also the plan I was having with the
mingw-libjpeg-turbo package once the mingw-w64 toolchain gets approved for
inclusion in Fedora. A mass rebuild will be required at that time anyway

@Levente, comment 6: The patch mentioned in comment 1 only applies to libtiff.
It isn't supposed to work in libjpeg. All packages using libjpeg would have to
apply a variant to this patch as it all depends on the headers which get
included in c/c++ files which want to use libjpeg headers

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


More information about the mingw mailing list