[Home]

Summary:ASTERISK-28409: unexpected build problem at install procedure
Reporter:PICCORO Lenz McKAY (mckaygerhard)Labels:patch
Date Opened:2019-05-08 12:25:24Date Closed:2020-03-13 13:41:28
Priority:MajorRegression?
Status:Closed/CompleteComponents:Channels/chan_vpb
Versions:16.0.0 16.0.1 16.1.0 16.1.1 16.2.0 16.2.1 16.3.0 Frequency of
Occurrence
Occasional
Related
Issues:
Environment:OS Debian 8 lasted pjproject bundled default configuration when try to buildAttachments:( 0) ASTERISK-28409.patch
Description:when try to build the chan_vpb module i got taht error: chan_vpb.cc:427:1: error: uninitialized const member 'ast_channel_tech::send_text_data' … quite xtrange … why?

{code}
[  486s] i586-linux-gnu-gcc -o sip/route.o -c sip/route.c -MD -MT sip/route.o -MF .sip_route.o.d -MP -pthread -I/usr/src/packages/BUILD/include -fgnu89-inline -g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2   -I/usr/include/libxml2  -pipe -Wall -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations       -fPIC -DAST_MODULE=\"chan_sip\" -DAST_MODULE_SELF_SYM=__internal_chan_sip_self    
[  486s] /usr/src/packages/BUILD/build_tools/make_linker_version_script chan_sip "" "/usr/src/packages/BUILD"
[  486s] i586-linux-gnu-gcc -o chan_sip.so -pthread -fPIE -pie -Wl,-z,relro -Wl,-z,now -Wl,--as-needed    -shared -Wl,--version-script,chan_sip.exports,--warn-common  chan_sip.o sip/security_events.o sip/dialplan_functions.o sip/reqresp_parser.o sip/utils.o sip/config_parser.o sip/route.o  
[  486s] i586-linux-gnu-g++ -o chan_vpb.oo -c chan_vpb.cc -MD -MT chan_vpb.oo -MF .chan_vpb.oo.d -MP -pthread -I/usr/src/packages/BUILD/include -fgnu89-inline -g -O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -I/usr/include/libxml2 -pipe -Wall -fPIC -DAST_MODULE=\"chan_vpb\" -DAST_MODULE_SELF_SYM=__internal_chan_vpb_self
[  486s] cc1plus: warning: command line option '-fgnu89-inline' is valid for C/ObjC but not for C++
[  486s] chan_vpb.cc:393:1: error: uninitialized const member 'ast_channel_tech::send_text_data'
[  486s]  };
[  486s]  ^
[  486s] chan_vpb.cc:427:1: error: uninitialized const member 'ast_channel_tech::send_text_data'
[  486s]  };
[  486s]  ^
[  487s] /usr/src/packages/BUILD/Makefile.rules:169: recipe for target 'chan_vpb.oo' failed
[  487s] make[3]: *** [chan_vpb.oo] Error 1
[  487s] make[3]: Leaving directory '/usr/src/packages/BUILD/channels'
[  487s] Makefile:383: recipe for target 'channels' failed
[  487s] make[2]: *** [channels] Error 2
[  487s] make[2]: Leaving directory '/usr/src/packages/BUILD'
{code}
Comments:By: Asterisk Team (asteriskteam) 2019-05-08 12:25:25.598-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].

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.

By: George Joseph (gjoseph) 2019-05-08 13:48:38.501-0500

The module you're having difficulty with is in 'extended' support status and is supported only by community members.  Your issue is in the queue. Your patience is appreciated as a community developer may work the issue when time and resources become available.

Asterisk is an open source project and community members work the issues on a voluntary basis. You are welcome to develop your own patches and submit them to the project.[1]

If you are not a programmer and you are in a hurry to see a patch provided then you might try rallying support on the Asterisk users mailing list or forums.[2] Another alternative is offering a bug bounty on the asterisk-dev mailing list.[3] Often a little incentive can go a long way.

[1]: https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process
[2]: http://www.asterisk.org/community/discuss
[3]: https://wiki.asterisk.org/wiki/display/AST/Asterisk+Bug+Bounties


Because the voicetronix libraries that this module depends on are  no longer available in many distrbutions, we don't build this module during testing.  It hasn't been updated to compile with newer versions of gcc.


By: PICCORO Lenz McKAY (mckaygerhard) 2019-05-09 09:05:33.055-0500

slution patch thanks to https://community.asterisk.org/t/build-problems-asterisk-16/79593/2 please merge it!

https://groups.google.com/forum/m/?place=forum/venenuxsarisari#!topic/venenuxsarisari/FXcLQsaGxwQ

Debian report:  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928712.

By: Sean Bright (seanbright) 2020-03-13 13:41:29.091-0500

Per the debian issue you linked, it looks like this has something to do with your environment.