Summary:	ASTERISK-29719: I'm unable to compile Asterisk 18.8.0
Reporter:	Jon Westgate (0ryn)	Labels:
Date Opened:	2021-11-05 07:22:11	Date Closed:	2021-11-05 12:24:32
Priority:	Major	Regression?
Status:	Closed/Complete	Components:	pjproject/pjsip
Versions:	18.8.0	Frequency of Occurrence
Related Issues:
Environment:	Linux (Debian 11) gcc version 11.2.0 (Debian 11.2.0-10)	Attachments:
Description:	When compiling I get the following error: [LD] libasteriskpj.o -> libasteriskpj.so.2 /usr/bin/ld:libasteriskpj.exports:1: ignoring invalid character `-' in script /usr/bin/ld:libasteriskpj.exports:2022: syntax error in VERSION script collect2: error: ld returned 1 exit status make[1]: *** [Makefile:295: libasteriskpj.so.2] Error 1 make: *** [Makefile:388: main] Error 2 I've build asterisk loads of times and never had an error like this before :( Steps to reproduce this: Download and unpack asterisk code. (18.8.0) Run ./contrib/scripts/install_prereq install ./configure --prefix=/usr make menuselect make -j4 I'm not sure if I'm doing something wrong here. Asterisk 18.0.0 builds fine.
Comments:	By: Asterisk Team (asteriskteam) 2021-11-05 07:22:12.974-0500 The severity of this issue has been automatically downgraded from "Blocker" to "Major". The "Blocker" severity is reserved for issues which have been determined to block the next release of Asterisk. This severity can only be set by privileged users. If this issue is deemed to block the next release it will be updated accordingly during the triage process. By: Asterisk Team (asteriskteam) 2021-11-05 07:22:13.351-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. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed. 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]. Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur. Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/]. By: George Joseph (gjoseph) 2021-11-05 09:20:40.009-0500 Is this the first time you've tried gcc 11.2.0? You say 18.0.0 builds fine but was that with a different version of gcc? By: Jon Westgate (0ryn) 2021-11-05 10:41:49.867-0500 This is using the same version of gcc. Asterisk's 18.0 and 18.8 are just in different folders. I've just spun up another box and oddly I can compile 18.8.0 on another box with the same versions of gcc binutils etc. I wish I knew more about what happens behind the scenes when you run make. It's linking that's failing or the generation of the exports file. By: George Joseph (gjoseph) 2021-11-05 10:55:26.716-0500 Permissions maybe? {code} $ sudo chown -R <you>:<you> . $ make distclean {code} By: Jon Westgate (0ryn) 2021-11-05 11:55:05.184-0500 No Idea what I must have done. I did rm -rf asterisk-18.8.0 tar zxvf asterisk-18-current.tar.gz ./configure --prefix=/usr make menuselect make -j4 make install and job's a good one. Who knows why that failed. Feel free the close the ticket. Sorry for wasting everyone's time. Jon By: Sean Bright (seanbright) 2021-11-05 12:24:32.089-0500 No sweat. Thanks for letting us know it's resolved.