Created attachment 291313 [details, diff] Partial libpng15 patch No longer compiles with stable libpng-1.5.5: ./../../wxcommon/wxJPEG.cxx: In function 'void user_error_proc(png_structp, png_const_charp)': ./../../wxcommon/wxJPEG.cxx:524:20: error: invalid use of incomplete type 'png_struct {aka struct png_struct_def}' /usr/include/libpng15/png.h:830:20: error: forward declaration of 'png_struct {aka struct png_struct_def}' ./../../wxcommon/wxJPEG.cxx: In function 'int wx_read_png(char*, wxBitmap*, int, wxColour*)': ./../../wxcommon/wxJPEG.cxx:679:25: error: invalid use of incomplete type 'png_struct {aka struct png_struct_def}' /usr/include/libpng15/png.h:830:20: error: forward declaration of 'png_struct {aka struct png_struct_def}' ./../../wxcommon/wxJPEG.cxx: In function 'int wx_write_png(char*, wxBitmap*)': ./../../wxcommon/wxJPEG.cxx:967:25: error: invalid use of incomplete type 'png_struct {aka struct png_struct_def}' /usr/include/libpng15/png.h:830:20: error: forward declaration of 'png_struct {aka struct png_struct_def}' make[5]: *** [wxJPEG.lo] Error 1 After patching these issues, it fails with: Error [CALL] 679 in ./../../wxcommon/wxJPEG.cxx: Bad place for function call, starting tok is png_set_longjmp_fn. Error [CALL] 967 in ./../../wxcommon/wxJPEG.cxx: Bad place for function call, starting tok is png_set_longjmp_fn. xform: Errors converting Related discussion: http://forums.gentoo.org/viewtopic-t-900074-highlight-.html Once removed, these bugs can be closed: Bug 312419 Bug 334679 Plus not sure why Bug 324161 is still open
(In reply to comment #0) Thanks Samuli for the summary of the issue, and links to related bugs and forum post, and for the p.mask message. > Plus not sure why Bug 324161 is still open When that bug was open, they were stable versions of dev-scheme/plt-scheme in the tree. So that bug intended to stay open until a version of dev-scheme/racket gets stabilized. Stable keywords were dropped for plt-scheme due to libpng-1.4 bump, so I think you're right, that bug could be closed.
(In reply to comment #1) > > Plus not sure why Bug 324161 is still open > ... so I think you're right, that bug could be closed. Closed. Thanks for verifying.
Removed from portage.