Bug 199638
| Summary: | sysutils/libcdio-paranoia: (00:00:21) configure: error: Required libcdio library not found. Please get libcdio from http://www.gnu.org/software/libcdio/ and install it. | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Ports & Packages | Reporter: | Julien Cigar <julien> | ||||||||
| Component: | Individual Port(s) | Assignee: | Tilman Keskinoz <arved> | ||||||||
| Status: | Closed FIXED | ||||||||||
| Severity: | Affects Some People | CC: | swills | ||||||||
| Priority: | --- | Flags: | bugzilla:
maintainer-feedback?
(arved) |
||||||||
| Version: | Latest | ||||||||||
| Hardware: | amd64 | ||||||||||
| OS: | Any | ||||||||||
| Attachments: |
|
||||||||||
|
Description
Julien Cigar
2015-04-23 08:50:00 UTC
the port has been like this for 8 months without a report. Something is wrong on your system. Can you provide config.log? Created attachment 155904 [details]
/wrkdirs/usr/ports/sysutils/libcdio-paranoia/work/libcdio-paranoia-10.2+0.90+1/config.log
config.log file (from poudriere bulk -w)
the config.log complains that libcdio depends on glib-2.0. But the original files don't list this dependency. Can you also upload /usr/local/libdata/libcdio.pc Created attachment 155987 [details] libcdio-paranoia patch Attached patch fixes it, I saw this too. It hasn't shown up in portsmon: http://portsmon.freebsd.org/portoverview.py?category=sysutils&portname=libcdio-paranoia&wildcard= So perhaps there's some local config that causes it. Forgot to link to my build failure log: http://poudriere.mouf.net/poudriere/data/11amd64-default/2015-04-24_18h01m57s/logs/errors/libcdio-paranoia-10.2+0.90+1_1.log While the patch "fixes" the build for libcdio-paranoia, it is wrong. The root cause seems to be in the libcdio.pc file potentially breaking every port that depends on libcdio. So if at all we should add glib-20 as a dependency of libcdio. But nothing in libcdio and libcdio-paranoia uses glib-2.0 so i would like to understand the reason, why the build fails for you. (Unfortunately i can't reproduce it.) before introducing another dependency. Would it be possible to upload a libcdio.pc file so that we can examine where the extra dependency comes from? Created attachment 156002 [details]
/usr/local/libdata/pkgconfig/libcdio.pc
I hope it is the correct file as the package is part of a poudriere build (and I don't have such file in the work/ dir)
Looking at libcdio.pc, it has a commented reference to glib-2.0, so I think this is the comment parsing bug in pkgconf. Updating to pkgconf-0.9.10 should fix it. You're right, works fine with pkgconf 0.9.10! I'm closing the bug report, sorry for the noise. |
