|
Bugzilla – Full Text Bug Listing |
| Summary: | fontforge complains about libpng versions | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.3 | Reporter: | Martin Schröder <martin> |
| Component: | Other | Assignee: | Takashi Iwai <tiwai> |
| Status: | RESOLVED NORESPONSE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Minor | ||
| Priority: | P5 - None | CC: | pgajdos |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Martin Schröder
2010-12-05 01:49:42 UTC
what happen after you install the libpng14-compat-devel? I just update the platform from win3.1 back to openSUSE10.3 assuming you are using that. (In reply to comment #1) > what happen after you install the libpng14-compat-devel? That deletes libpng12-compat-devel (don't know where that came from) and everything's fine. (In reply to comment #2) > I just update the platform from win3.1 back to openSUSE10.3 assuming you are > using that. No; see #219910 I think what happen is when you build something that require libpng12 specific library and then the symlink was be created by using the libpng12 library. The fontforge package is linking to the libpng.so directly and at runtime it get switch to use libpng12 by the symlink instead of the libpng14. Since fontforge is part of the development packages, what should be done in the spec is to require libpng14-compat-devel to make sure the runtime get the same version of libpng with the build time. Let us know if this fix your issue. Thanks When I run fontforge, I get
libpng: libpng.so.2: cannot open shared object file: No such file or directory
(not libpng.so). It seems to work without it, though.
I am convinced that this is result of the magic on the begining of gimage{read,write}png.c files. When I workarounded it by hardcodidng to use libpng14.so.14 -- see libpng14-dynamic.diff --, fontforge don't emit any such message. I have updated fontforge by the way to the upstream version 20110222 and I have submitted it into M17N.
Takashi, you seems to be maintainer. Please look at fontforge in M17N, I am sure you will find more elegant solution, therefore I will not submit it to factory.
Note that %suse_version of Factory is still 1140, so two conditions in specfile should be changed (from 1130 to 1140). I concentrated on build for factory and I have not checked yet, if fontforge builds for older distributions, for 11.4 will not certainly until Factory will not have right version and conditions will not be adapted.
Thanks
No, I'm no maintainer of the package. My name was copied to PDB by some random reason after Mike left... Anyway I'll check the package in M17N later. openSUSE 11.4 is EOL. Please reopen if the problem still appears on 12.2. Thanks. |