| Summary: | ASTERISK-26294: build: --disable-dev-mode precludes --with-pjproject-bundled in ./configure | ||
| Reporter: | Private Name (falves11) | Labels: | |
| Date Opened: | 2016-08-13 14:13:41 | Date Closed: | |
| Priority: | Minor | Regression? | |
| Status: | Open/New | Components: | Core/BuildSystem Core/General |
| Versions: | 13.10.0 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Linux 64, Ubuntu 14.04 | Attachments: | |
| Description: | if I use --disable-dev-mode, the pjsip is not recognized by configure. I don't remember why I always use disable-dev-mode, but years ago there was an important reason.
./configure LDFLAGS="-z muldefs" --libdir=/usr/lib64 --with-unixodbc=$(odbc_config --include-prefix)/ --with-pjproject-bundled | grep -i "error\|pjsip" checking for error_at_line... yes checking for strerror... yes checking for pjsip_dlg_create_uas_and_inc_lock declared in pjsip.h... yes checking for pjsip_tsx_create_uac2 declared in pjsip.h... yes checking for pjsip_get_dest_info declared in pjsip.h... yes checking for pjsip_endpt_set_ext_resolver declared in pjsip.h... yes checking for poptStrerror in -lpopt... yes root@STREAM-PC:/usr/src/asterisk# ./configure LDFLAGS="-z muldefs" --libdir=/usr/lib64 --with-unixodbc=$(odbc_config --include-prefix)/ --disable-dev-mode --with-pjproject-bundled | grep -i "error\|pjsip" checking for error_at_line... yes checking for strerror... yes checking for pjsip_dlg_create_uas_and_inc_lock in -lpjsip... no checking for pjsip_tsx_create_uac2 in -lpjsip... no checking for pjsip_get_dest_info in -lpjsip... no checking for pjsip/include/pjsip/sip_util.h in -lpj... no checking for pjsip_endpt_set_ext_resolver in -lpjsip... no checking if "struct pjsip_tls_setting setting; int proto; proto = setting.proto;" compiles using pjsip.h... no checking for pjsip_evsub_add_ref in -lpjsip... no checking for poptStrerror in -lpopt... yes | ||
| Comments: | By: Asterisk Team (asteriskteam) 2016-08-13 14:13:42.083-0500 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. By: Alexander Traud (traud) 2020-04-17 11:23:12.304-0500 Do you still face that issue? I try to reproduce your issue but failed yet. | ||