Bug 1187743 - conky configure looks for lua incorrectly
Summary: conky configure looks for lua incorrectly
Keywords:
Status: CLOSED DUPLICATE of bug 1229450
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: conky
Version: epel7
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Miroslav Lichvar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1187095
TreeView+ depends on / blocked
 
Reported: 2015-01-30 18:58 UTC by Orion Poplawski
Modified: 2015-06-26 12:27 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-26 12:27:38 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

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 ***


Note You need to log in before you can comment on or make changes to this bug.