Bug 1187743

Summary: conky configure looks for lua incorrectly
Product: [Fedora] Fedora EPEL Reporter: Orion Poplawski <orion>
Component: conkyAssignee: Miroslav Lichvar <mlichvar>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: epel7CC: mlichvar, moceap
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-26 12:27:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1187095    

Description Orion Poplawski 2015-01-30 18:58:21 UTC
Description of problem:

conky's configure cannot find lua on EPEL7 because it looks for it incorrectly:

configure:13975: checking for LUA
configure:13983: $PKG_CONFIG --exists --print-errors "lua == 5.1"
Unknown version comparison operator '==' after package name 'lua' in file '(command line arguments)'

The proper operator is "=".

Also, the lua package in RHEL7 only provides lua.pc, not lua-5.1.pc, which is how it works in Fedora:

configure:14018: checking for LUA51
configure:14026: $PKG_CONFIG --exists --print-errors "lua-5.1 >= 5.1"
configure:14029: $? = 0

This should fix:

--- configure.ac.in.pkgconfig   2014-06-17 18:23:33.000000000 -0600
+++ configure.ac.in     2015-01-30 11:57:28.557584338 -0700
@@ -488,7 +488,7 @@

 AM_CONDITIONAL(BUILD_LUA, test x$want_lua = xyes)
 if test x$want_lua = xyes; then
-       PKG_CHECK_MODULES(LUA, lua == 5.1, [ ],[
+       PKG_CHECK_MODULES(LUA, lua = 5.1, [ ],[
                PKG_CHECK_MODULES(LUA51, lua-5.1 >= 5.1, [ ],[
                        PKG_CHECK_MODULES(LUA51, lua5.1 >= 5.1)
                ])

Comment 1 Miroslav Lichvar 2015-06-26 12:27:38 UTC
It seems this change was commit in the git, but there is still some problem reported in bug #1229450.

*** This bug has been marked as a duplicate of bug 1229450 ***