You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Bryan Call (JIRA)" <ji...@apache.org> on 2016/08/16 15:51:20 UTC
[jira] [Updated] (TS-2334) --with-tcmalloc does not test whether
the "found" library actually exists
[ https://issues.apache.org/jira/browse/TS-2334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bryan Call updated TS-2334:
---------------------------
Labels: newbie (was: )
> --with-tcmalloc does not test whether the "found" library actually exists
> -------------------------------------------------------------------------
>
> Key: TS-2334
> URL: https://issues.apache.org/jira/browse/TS-2334
> Project: Traffic Server
> Issue Type: Bug
> Components: Build
> Affects Versions: 4.1.2, 4.2.0
> Reporter: Igor Galić
> Assignee: Eric Sproul
> Labels: newbie
> Fix For: sometime
>
>
> Our {{TS_CHECK_TCMALLOC}} does not work.
> I found this when compiling --with-tcmalloc on Ubuntu, where the {{tcmalloc}} library is called {{tcmalloc_minimal}}. (And its corresponding -dev package, will, intuitively be named {{libgoogle-perftools-dev}}. )
> But none of this actually matters. I don't need to have any tcmalloc libraries installed for this to fail horribly: {{-ltcmalloc}} will be added to the build simply because I specified {{--with-tcmalloc}} this causes pretty much everything in the configure run to break, or at least run with defaults. (e.g.: glibc2 is not recognized to have a reentrant {{gethostbyname()}}, see TS-2331)
> proposal: ACTUALLY check if {{tcmalloc}} can be found, abort {{configure}} if it can't.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)