Summary: | app-emulation/emul-linux-x86-baselibs needs a copy of libjpeg.so.62 and .7 and .8 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Andrew Frink <andrew.frink> |
Component: | [OLD] Library | Assignee: | AMD64 Project <amd64> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | andrew.frink, bugzilla, denilsonsa, marcusvini, pacho, roy |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 165270, 299149 |
Description
Andrew Frink
2010-02-02 19:42:33 UTC
Yes, emul-linux-x86-baselibs needs now, media-libs/jpeg:62 (for libjpeg.so.62) - This is like "jpeg-compat" media-libs/jpeg:7 (for libjpeg.so.7) - This is like "jpeg-compat" =media-libs/jpeg-8*:0 (for libjpeg.so.8) - This is what everything should be linked against. These can be installed on same system. *** Bug 303297 has been marked as a duplicate of this bug. *** Any reason why v8 of jpeg was removed in the more recent baselibs? It was working! It wan't ever added to emul-linux-x86-baselibs :-/ (In reply to comment #4) > It wan't ever added to emul-linux-x86-baselibs :-/ Is there a reason that I (the user) cannot just build these myself along with the 64 bit versions? I'm asking in all seriousness as this is the second time this has happened in the last 6 months or so. Yes i know jpeg-8 is ~amd64, but bumping jpeg should mean bumping emul-linux-x86-baselibs as well. This may need some help from the wine end as well, as it assumes that /usr/include/jpeglib.h is the correct header file even if it is going to load the 32bit version (it probably should be). Although the WINE devs seem to be very hostile towards Gentoo for some reason. Maybe WINE needs to depend on "=media-libs/jpeg-X" where X is the version in baselibs. I'm using app-emulation/emul-linux-x86-baselibs-20091231, (In reply to comment #5) > Is there a reason that I (the user) cannot just build these myself along with > the 64 bit versions? I'm asking in all seriousness as this is the second time Bug 145737. Fixed (In reply to comment #7) > Fixed > Can we say a little more? like "fixed in version _______" (In reply to comment #8) > (In reply to comment #7) > > Fixed > > Can we say a little more? like "fixed in version _______" > Yes, of course, it's fixed in current testing one -> 20100220 Fixes like this (related with packages additions, removals...) are usually included in the testing version added just before closing the bug report ;-) Regards |