Summary: | media-libs/ming-0.3.0 ebuild fails: missing libungif | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Howard B. Golden <howard_b_golden> |
Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | VERIFIED DUPLICATE | ||
Severity: | normal | CC: | notellin |
Priority: | High | ||
Version: | 2006.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Howard B. Golden
2006-08-20 12:03:18 UTC
Run revdep-rebuild, this doesn't need libungif at all. *** This bug has been marked as a duplicate of 83238 *** (In reply to comment #1) > Run revdep-rebuild, this doesn't need libungif at all. > > *** This bug has been marked as a duplicate of 83238 *** > Hi Jakub, This is not the same as 83238 83238 and friends reports missing "libungif" This bug reports missing "-lungif". The reporter has assumed "libungif" I'm having the same problem on every PC I update which has ming installed. To my non-programmer eyes, it looks like the compile command should end after .../libming.a or that "-lz -lungif -lpng \" is in the wrong place. /var/tmp/portage/ming-0.3.0/work/ming-0.3.0/libming.a \ -lz -lungif -lpng \ <====== (In reply to comment #2) > This is not the same as 83238 Of course it is. > This bug reports missing "-lungif". > The reporter has assumed "libungif" So what? You've got junk left from libungif on your system. This shouldn't even try to link against ungif, if it does, your need to run revdep-rebuild to get rid of it. If you still have libungif installed, you should unmerge it ASAP. And no, it's not needed for ming to compile. (In reply to comment #3) > (In reply to comment #2) > > This is not the same as 83238 > > Of course it is. > > > This bug reports missing "-lungif". > > The reporter has assumed "libungif" > > So what? You've got junk left from libungif on your system. This shouldn't even > try to link against ungif, if it does, your need to run revdep-rebuild to get > rid of it. If you still have libungif installed, you should unmerge it ASAP. > And no, it's not needed for ming to compile. > Hi Jakub, You are correct in that I had left over stuff from ealier versions of libgdiplus. This is what I have on at least three different PCs: ssss_server ~ # emerge -Cp libungif >>> These are the packages that would be unmerged: --- Couldn't find 'libungif' to unmerge. >>> No packages selected for removal by unmerge. ssss_server ~ # locate libungif /usr/lib/libungif.so.4.1.0 /usr/lib/libungif.so.4 /usr/portage/distfiles/libungif-4.1.3.tar.bz2 /usr/portage/dev-dotnet/libgdiplus/files/libgdiplus-1.1.10-libungif-configure-fix.diff /usr/portage/dev-dotnet/libgdiplus/files/libgdiplus-1.1.13-libungif-configure-fix.diff /usr/portage/app-editors/emacs/files/emacs-21.4-libungif-gif-gentoo.patch ssss_server ~ # emerge -pDv libgdiplus These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] dev-dotnet/libgdiplus-1.1.16.1 USE="gif jpeg png tiff" 0 kB Total size of downloads: 0 kB ssss_server ~ # emerge -pDv emacs These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] app-editors/emacs-21.4-r5 USE="X Xaw3d motif nls -leim -lesstif -nosendmail" 0 kB Total size of downloads: 0 kB ssss_server ~ # libungif and earlier versions of libgdiplus had already been unmerged from all of the PCs. revdep-rebuild didn't see any problem. Deleting the two libungif files resolved the problem. Thanks for responding. I've proceded to manually remove the two left over artifacts from the other PCs. Obviously, I haven't any clue as to why they weren't automatically removed in the first place. Hopefully, this will help anyone else who encounters the problem. |