Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#13074 - pkgconfig configuration file currupted
Attached to Project:
Arch Linux
Opened by Maxime de Roucy (akira86) - Saturday, 31 January 2009, 20:50 GMT
Last edited by Ronald van Haren (pressh) - Sunday, 01 February 2009, 17:22 GMT
Opened by Maxime de Roucy (akira86) - Saturday, 31 January 2009, 20:50 GMT
Last edited by Ronald van Haren (pressh) - Sunday, 01 February 2009, 17:22 GMT
|
DetailsDescription:
pkg-config configuration file /usr/lib/pkgconfig/pm-utils.pc there is a ")" instead of an "}" which make compilation of some software crash. I was working on a another bug http://bugs.archlinux.org/task/12022 and I can't managed to compile miro... that's how I found this bug. Additional info: * package version : 0.23-1 /usr/lib/pkgconfig/pm-utils.pc : before, line 9 : pm_powerhooks=${pm_libdir)/power.d after(solve), line : pm_powerhooks=${pm_libdir}/power.d It's not hard to solve but I think is important to signal this bug in order to update the pkgconfig package. |
This task depends upon
Closed by Ronald van Haren (pressh)
Sunday, 01 February 2009, 17:22 GMT
Reason for closing: Duplicate
Additional comments about closing: duplicate of FS#13078 (actually the other way around but
that one contains a link to the upstream
report. Sorry I did not see this
report.)
Sunday, 01 February 2009, 17:22 GMT
Reason for closing: Duplicate
Additional comments about closing: duplicate of

sorry, I was working on this bug http://bugs.archlinux.org/task/13072 ; not the other one.

This is an upstream bug. Please report there too.