[
https://issues.apache.org/jira/browse/TS-2334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13817474#comment-13817474
]
Leif Hedstrom commented on TS-2334:
-----------------------------------
I'm not saying we shouldn't make the checks better, but the configure option
supports what you need. E.g.
{code}
--with-tcmalloc-lib=tcmalloc_minimal
{code}
> --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.0, 4.2.0
> Reporter: Igor Galić
>
> 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.1#6144)
