You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/05/06 19:06:16 UTC

[jira] [Commented] (TS-1768) use AC_SEARCH_LIBS instead of AC_CHECK_LIB

    [ https://issues.apache.org/jira/browse/TS-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649872#comment-13649872 ] 

ASF subversion and git services commented on TS-1768:
-----------------------------------------------------

Commit abb0d748d96d966e495f8a2bff21ec420498ee14 in branch refs/heads/master from [~jpeach@apache.org]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=abb0d74 ]

TS-1768: prefer AC_SEARCH_LIBS to AC_CHECK_LIB

AC_SEARCH_LIB should be preferred to AC_CHECK_LIB because the former
does not link the library under test the symbol is already present.
AC_SEARCH_LIBS conveniently appends the library to LIBS which makes
the Makefile.am simpler.

Unfortunately, our check for libresolv depends on the AC_CHECK_LIB
behavior. I didn't change this because the extensive use of macros
to rename API in libresolv makes the configuration tests more complex
that I wanted to deal with in this bug.

                
> use AC_SEARCH_LIBS instead of AC_CHECK_LIB
> ------------------------------------------
>
>                 Key: TS-1768
>                 URL: https://issues.apache.org/jira/browse/TS-1768
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: Build
>            Reporter: James Peach
>            Assignee: James Peach
>             Fix For: 3.3.5
>
>
> In general, we ought to be using AC_SEARCH_LIBS, for the reasons outlined here: http://www.flameeyes.eu/autotools-mythbuster/autoconf/finding.html. We will need to check each of the 40 or so AC_CHECK_LIB tests just to make sure the replacement is safe.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira