[asterisk-bugs] [JIRA] (ASTERISK-25329) Asterisk configure fails on 'cannot find ptlib-config', despite ptlib-config existing

[Kevin Harwell (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-25329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kevin Harwell updated ASTERISK-25329:
-------------------------------------

    Target Release Version/s: 16.3.0

> Asterisk configure fails on 'cannot find ptlib-config', despite ptlib-config existing
> -------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-25329
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25329
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/BuildSystem
>    Affects Versions: 13.5.0, 13.7.0
>         Environment: Debian 7.8, 32bit
>            Reporter: Rusty Newton
>              Labels: patch
>      Target Release: 13.20.0, 15.3.0, 16.0.0, 16.3.0
>
>         Attachments: ptlib-config.patch
>
>
> When configuring Asterisk 13.5.0 I get
> {noformat}
> checking for /usr/include/ptlib.h... yes
> checking for ptlib-config... no
> ./configure: line 27669: --ldflags: command not found
> Cannot find ptlib-config - please install and try again
> {noformat}
> apt-file search shows "libpt-dev: /usr/share/ptlib/make/ptlib-config"
> and apt-get shows "libpt-dev is already the newest version."
> configure doesn't seem to find it ptlib-config..
> {noformat}
> root at debian1:/# find . -name "*ptlib*"
> ./usr/include/ptlib.h
> ./usr/include/openh323/ptlib_extras.h
> ./usr/include/ptlib
> ./usr/include/ptlib/unix/ptlib
> ./usr/include/ptlib/unix/ptlib/ptlib.inl
> ./usr/lib/pkgconfig/ptlib.pc
> ./usr/lib/ptlib-2.10.4
> ./usr/share/ptlib
> ./usr/share/ptlib/make/ptlib-config
> ./usr/share/ptlib/make/ptlib.mak
> {noformat}
> workaround is to specify the location manually:
> {noformat}
> export PTLIB_CONFIG=/usr/share/ptlib/make/ptlib-config
> {noformat}
> Ran configure again and it was fine.



--
This message was sent by Atlassian JIRA
(v6.2#6252)