- Package:
- libmng-dev
- Source:
- libmng
- Description:
- M-N-G library (Development headers)
- Submitter:
- Keyikedalube Ndang
- Date:
- 2026-02-20 16:45:01 UTC
- Severity:
- normal
I'm having building synfig project using CMake on Debian Bullseye. The project collaborator mentioned the issue with Debian libmng package not installing pkg-config file as the problem. Here's the quoted link https://github.com/synfig/synfig/issues/928#issuecomment-554623877 Regards, Keyikedalube Ndang
I'm having *trouble* building...
Hello Debian maintainers,
Seems I reported this bug against the wrong package. There is a libmng2 package in experimental with the fix applied. Here's the [link](https://metadata.ftp-master.debian.org/changelogs//main/libm/libmng/libmng_2.0.3+dfsg-3_changelog) and a quoted changelog:
libmng (2.0.3+dfsg-3) experimental; urgency=low
* debian/libmng-dev.install:
+ Install pkgconfig file.
* debian/rules:
+ Synced from Ubuntu. Thanks!
+ Fixed clean target.
+ Use dh-autoreconf and fix dpkg-buildflags usage.
+ Fixed installation of pkgconfig.
+ Removed -V from dh_makeshlibs, debian/shlibs overrides it.
* Update debian/shlibs file.
Can that fix be applied on libmng1? Or is it better to pull libmng2 from experimental?
Sorry for the trouble. I realize since there is a new version of libmng2 along with updated libmng-dev on Debian experimental, applying the same fix (Install pkgconfig file) may not be needed in an older version. Moreover, libmng package has been left dormant since 2018 https://tracker.debian.org/pkg/libmng Again, sorry for the trouble. PS: This bug was reported against the right package ie., libmng-dev and not libmng1. I'm new so a little bit of confusion I had there :)
Sorry, forgot to close this earlier, but libmng-dev now includes the pkgconfig file as you mentioned earlier with libmng2.