Bugzilla Bug 9757

If I have my use flags set to USE-"gnome" when I emerge xchat (and or xmms) 
the ebuild fails on installing gnome-panel-1.4.1.  The reported error 
message is 

checking for png_init_io in -lpng... ./configure: ]: command not found
no
configure: error: libpng is required for gnome-core

!!! ERROR: The ebuild did not complete successfully.
!!! Function src_compile, Line 49, Exitcode 1
!!! (no error message)

I do have libpng installed:
qpkg -I -v | grep libpng
media-libs/libpng-1.2.5 *

After i emerged libpng-1.0.12-r1, everything works fine.

ok, What version did you have before this emerge? (gdk pixbuf is a dep of
gnome-panel, and that should depend on png)


and here I thought that libpng issues were a thing of the past...  :-(

libpng-1.2.5 was (and still is) emerged.

qpkg -I -v | grep libpng
media-libs/libpng-1.2.5 *
media-libs/libpng-1.0.12.r1 *

oh yech...

you suffered from the "loading two versions of libpng at the same time"
problem.. there are some ways to get around it, you figured out the simple
solution. the other is to remove the old libpng version, install only the new,
and then rebuild all the libraries and programs that link to the now missing old
version.

The problem appears as old libraries (gdk pixbuf) link to the old libpng, and
the test programs and new programs compiled link with the new libpng... then the
two versions will collide and programs fail to use png. 

So, what should Angel Ortiz do?

Last night i started installation from ut2003-cd. It was a great pain. A lot of
problems appeared. 
And this morning i reached the point where everything stopped. 

libpng-1.2.5 was installed, but gnome-panel doesnot recognize the library (see
above posting from Angel). It was a clean install, so i would not expect these
problems.

This and the softlinks in /etc/lib was the reason to test libpng-1.0.12.r1. 

Yeah what should I do?  :-D

This is a fresh install as well.  Just newly installed last night.  I had other
errors during the install related to libcrack.so.2 not being properly
registered.  ( a symlink fixed that)  (see bug   9726) but other than that the
install went smoothly.  No other errors besides this one. Are the gremlins back
for Halloween?

Here are all the gnome packages that I have.  Again a fresh install so all I
really emerged so far are gnome, evolution and mozilla.  Still working on my
system.  I hope this is helpful :)  (maybe some whacked out package looking for
something old?)

qpkg -I -v | grep gnome
gnome-base/ORBit2-2.4.3 *
gnome-base/gconf-1.2.1 *
gnome-base/libgtop-2.0.0-r1 *
gnome-base/gnome-mime-data-2.0.1 *
gnome-base/bonobo-activation-1.0.3 *
gnome-base/libbonobo-2.0.0-r1 *
gnome-base/gnome-vfs-2.0.4-r2 *
gnome-base/libgnome-2.0.5 *
gnome-base/libglade-2.0.1 *
gnome-base/libgnomecanvas-2.0.4 *
gnome-base/libbonoboui-2.0.3 *
gnome-base/libgnomeui-2.0.5 *
gnome-base/gnome-desktop-2.0.9 *
gnome-base/libgnomeprint-1.116.0 *
gnome-base/librsvg-2.0.1 *
gnome-base/gail-0.17 *
gnome-base/gnome-panel-2.0.10 *
gnome-base/libgnomeprintui-1.116.0 *
gnome-base/eel-2.0.7 *
gnome-base/nautilus-2.0.7 *
gnome-base/gdm-2.4.0.11 *
gnome-base/gnome-session-2.0.8 *
gnome-base/gnome-applets-2.0.3 *
gnome-base/control-center-2.0.1.1 *
gnome-base/gnome-2.0.2-r2 *
gnome-base/ORBit-0.5.17 *
gnome-base/gnome-libs-1.4.2 *
gnome-base/libglade-0.17-r6 *
gnome-base/oaf-0.6.10 *
gnome-base/gconf-1.0.8-r3 *
gnome-base/gnome-vfs-1.0.5-r2 *
gnome-base/control-center-1.4.0.5-r1 *
gnome-base/gnome-print-0.35-r3 *
gnome-base/bonobo-1.0.19-r1 *
gnome-base/libghttp-1.0.9-r2 *
app-text/gnome-spell-0.4.1-r3 *
gnome-extra/gnome-system-monitor-2.0.2 *
gnome-extra/gconf-editor-0.3.1 *
gnome-extra/libgtkhtml-2.0.2 *
gnome-extra/gnome-utils-2.0.5 *
gnome-extra/gnome-media-2.0.2.5-r1 *
gnome-extra/gnome-games-2.0.4 *
gnome-extra/yelp-1.0.6 *
gnome-extra/gnome2-user-docs-2.0.1 *
gnome-extra/bug-buddy-2.2.0 *
gnome-extra/bonobo-conf-0.16 *
gnome-extra/gal-0.20 *
gnome-extra/gtkhtml-1.0.4 *
x11-terms/gnome-terminal-2.0.1 *

See Bug#:9769

Ok, there are now two tickets for this same problem, which I too am having.
I am attempting a fresh install and have skipped xmms for the time being.
I too had a problem with a symlink not being created - so I created it myself.
Later, after the failed ebuild, I updated portage & followed the post-install message.
I ran /sbin/ldconfig, and even tried it in a chroot'd envrionment - booted off the CD.
Now, I am a programmer - though not a C programmer.  But the ']' on the 9,251st line of the file 'configure' shouldn't be there, should it?
Perhaps it was patched incorrectly?

*** Bug 9850 has been marked as a duplicate of this bug. ***

*** This bug has been marked as a duplicate of 9792 ***