[jira] [Resolved] (DAEMON-241) configure incorrectly includes -lcap in the LIBS variable in Makedefs

["Mladen Turk (Resolved) (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DAEMON-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mladen Turk resolved DAEMON-241.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 1.0.10

It was probably packaging error with old configure being cached. Anyhow fixed the issue by ensuring we only check for header not library. Also warning is shown if in configure stage if libcap headers cannot be found
                
> configure incorrectly includes -lcap in the LIBS variable in Makedefs
> ---------------------------------------------------------------------
>
>                 Key: DAEMON-241
>                 URL: https://issues.apache.org/jira/browse/DAEMON-241
>             Project: Commons Daemon
>          Issue Type: Bug
>          Components: Jsvc
>    Affects Versions: 1.0.9
>            Reporter: Phil Clay
>             Fix For: 1.0.10
>
>
> The unix/configure script included in commons-daemon-1.0.9-native-src.tar.gz incorrectly includes "-lcap" in the LIBS variable in the generated Makedefs file.
> This causes the version of libcap on the linker machine to be required at jsvc runtime.  (Which is what https://issues.apache.org/jira/browse/DAEMON-234 was trying to prevent)
> As a workaround, I ran autoconf to regenerate the configure script.  After doing so, the newly regenerated configure script will properly exclude -lcap from the LIBS variable in Makedefs when configure is executed.
> So, I believe autoconf needs to be executed to regenerate the configure script included in the source tarball.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira