configure.in in the libgdiplus-2.10.9 source explicitly states -lpng14. The libpng dependency of the ebuild is also satisfied by libpng-1.5 and, thus, the code doesn't compile with libpng-1.5 installed but libpng-1.4 not installed. Changing "-lpng14" to "-lpng15" in configure.in let me compile libgdiplus-2.10.9, but I haven't tested whether there are runtime errors... Maybe the check for libpng14 could be replaced by a check for libpng and a check whether the version is recent enough, but since I really don't have any idea in dealing with configure.in, I'd rather not submit a patch...
Please provide build.log and verify you have updated to libpng properly
Created attachment 326112 [details] log of failed build
I do not quite understand what you mean by "verify you have updated to libpng properly". I can, however, assure you that everything depending on libpng works fine and # eix libpng [I] media-libs/libpng Available versions: (1.2) 1.2.49 ~1.2.50 (0) 1.5.10 ~1.5.11 ~1.5.12 {{apng neon static-libs}} Installed versions: 1.5.10(06:21:48 PM 09/24/2012)(apng -neon -static-libs) Homepage: http://www.libpng.org/ Description: Portable Network Graphics library and # pkg-config --libs libpng -lpng15 so I am pretty sure that my libpng is all right.
Oh dear, I just noticed: # pkg-config --libs libpng12 -lpng14
*** This bug has been marked as a duplicate of bug 319101 ***
http://mirror.meleeweb.net/pub/linux/gentoo/portage/metadata/news/2011-10-15-libpng15/2011-10-15-libpng15.en.txt
sorry, I do not agree that this bug is a duplicate of the other bug you linked. Consider the following: If I remove the /usr/lib64/pkgconfig/libpng12.pc (which should not be there anyways) and rebuild libgdiplus (yes, it does build in this case), then the configure script says: checking for libpng14... checking for libpng12... no so, there is no libpng support in the resulting libgdiplus. However, I *do* have a working libpng-1.5 and libgdiplus *does* compile *with* libpng support if I force it to link against libpng-1.5 by patching configure.in. Concerning the text file you linked, I did what it says there (some revdep-rebuilding was necessary) and now find /usr/ -name '*.la' -exec grep png14 {} + returns nothing at all, so I assume that I "have updated to libpng properly", but the error remains.
Will CC libpng maintainers because this looks really strange to me
in the past, packages used scan libpng versions, but that shouldn't be necessary anymore. or at least, they could add a fallback to hit "libpng". reading that configure.in shows other fails. like running pkg-config directly (even though it already sets up $PKG_CONFIG).
(In reply to comment #4) > Oh dear, I just noticed: > > # pkg-config --libs libpng12 > -lpng14 you shouldn't have file called libpng12.pc installed at all, in /usr/lib/pkgconfig/ or /usr/share/pkgconfig/ or same directories inside /usr/local so i'd say this is a situation you have created yourself, now deal with it
(In reply to comment #9) > reading that configure.in shows other fails. like running pkg-config > directly (even though it already sets up $PKG_CONFIG). we can reuse this bug for that, since the libpng related error is bogus, I guess
(In reply to comment #10) > (In reply to comment #4) > > Oh dear, I just noticed: > > > > # pkg-config --libs libpng12 > > -lpng14 > > you shouldn't have file called libpng12.pc installed at all, in > /usr/lib/pkgconfig/ or /usr/share/pkgconfig/ or same directories inside > /usr/local I bet you have a symlink called libpng12.pc -> libpng.pc or libpng14.pc only libpng15.pc and libpng.pc, both needs to return -lpng15, and that they will do if you use libpng from Portage as intended
(In reply to comment #10) > (In reply to comment #4) > > Oh dear, I just noticed: > > > > # pkg-config --libs libpng12 > > -lpng14 > > you shouldn't have file called libpng12.pc installed at all, in > /usr/lib/pkgconfig/ or /usr/share/pkgconfig/ or same directories inside > /usr/local > > so i'd say this is a situation you have created yourself, now deal with it okay, that's about the most arrogant reply I've read on this bugzilla so far... Surely, I could tell you that everything done to pkgconfig was done by portage on my system, but there's not really a point, since we've progressed past this issue (see my own Comment 7 and SpanKY's Comment 9, which, seeing that your comments started with 10 you should have read before...)
(In reply to comment #13) > okay, that's about the most arrogant reply I've read on this bugzilla so > far... sorry. really. > Surely, I could tell you that everything done to pkgconfig was done by > portage on my system, but there's not really a point, since we've progressed > past this issue (see my own Comment 7 and SpanKY's Comment 9, which, seeing > that your comments started with 10 you should have read before...) i've read them, but what I said still stands, pkg-config --libs libpng12 does not print anything on Gentoo systems as there is no file or symlink called libpng12.pc installed by any package. both libpng12 and libpng14 are gone from portage, well, there is the libpng slot for 1.2 which installs only 1 file, and that is not the .pc file so really, find the libpng12.pc and delete it, follow the libpng update note Pacho pointed out in Comment #6. the only result installed via portage is: $ pkg-config --libs libpng12 Package libpng12 was not found in the pkg-config search path. Perhaps you should add the directory containing `libpng12.pc' to the PKG_CONFIG_PATH environment variable No package 'libpng12' found $ pkg-config --libs libpng14 Package libpng14 was not found in the pkg-config search path. Perhaps you should add the directory containing `libpng14.pc' to the PKG_CONFIG_PATH environment variable No package 'libpng14' found $ pkg-config --libs libpng15 -lpng15 $ pkg-config --libs libpng -lpng15
> so really, find the libpng12.pc and delete it, follow the libpng update note > Pacho pointed out in Comment #6. the only result installed via portage is: > > $ pkg-config --libs libpng12 > Package libpng12 was not found in the pkg-config search path. > Perhaps you should add the directory containing `libpng12.pc' > to the PKG_CONFIG_PATH environment variable > No package 'libpng12' found > $ pkg-config --libs libpng14 > Package libpng14 was not found in the pkg-config search path. > Perhaps you should add the directory containing `libpng14.pc' > to the PKG_CONFIG_PATH environment variable > No package 'libpng14' found > $ pkg-config --libs libpng15 > -lpng15 > $ pkg-config --libs libpng > -lpng15 I did all this on 2012-10-09, leading to a successful compile of libgdiplus without libpng support (build log says "checking for libpng14... checking for libpng12... no") because configure.in is somewhat messy/faulty. On my system, I "fixed" (meaning dirtily hacked) configure.in to detect my libpng-15. I think of this ticket as a pointer to an error in configure.in that someone with more knowledge of build systems than me might want to fix, just as SpanKY pointed out.
(In reply to comment #15) > I did all this on 2012-10-09, leading to a successful compile of libgdiplus > without libpng support (build log says "checking for libpng14... checking > for libpng12... no") because configure.in is somewhat messy/faulty. On my > system, I "fixed" (meaning dirtily hacked) configure.in to detect my > libpng-15. I think of this ticket as a pointer to an error in configure.in > that someone with more knowledge of build systems than me might want to fix, > just as SpanKY pointed out. the configure.in is properly setupped: checking for libpng14... checking for libpng12... no checking for png_read_info in -lpng... yes checking png.h usability... yes checking png.h presence... yes checking for png.h... yes checking for png_structp in png.h... yes as in: else AC_MSG_RESULT(no) AC_CHECK_LIB(png, png_read_info, [AC_CHECK_HEADER(png.h, png_ok=yes, png_ok=no)], it has a fallback after libpng12.pc and libpng14.pc (neither installed by portage, as already pointed out many times) to search for the -lpng library, and it does. really, fix your system and stop arguing...
the only bug here to fix is the calling of `pkg-config` directly which breaks cross-compiling and is not related to your issue... at all.
ah, you're right, I see the fallback now. Thanks for clearifying. I'll just shut up now and let you guys do your thing :]
(In reply to comment #18) > ah, you're right, I see the fallback now. Thanks for clearifying. I'll just > shut up now and let you guys do your thing :] yep. I suspect you, at some point, encoutered problems with the libpng upgrade in the past -> therefore you had to install libpng12 or libpng14 manually and you made an `make install` that resulted in the libpng12.pc or libpng14.pc files/symlinks to be installed after removing them away, the fallback works as designed in configure.in futhermore you are partly correct that the libpng12 and libpng14 searches COULD be dropped from the configure.in, but that is an upstream issue and not related to Gentoo. i'm glad you got it figured out!
please retry with 4.2-r3
