Summary: | ASTERISK-27723: [patch] BuildSystem: Enable OSS Audio Emulation Library in NetBSD. | ||
Reporter: | Alexander Traud (traud) | Labels: | patch |
Date Opened: | 2018-03-06 12:59:58.000-0600 | Date Closed: | |
Priority: | Minor | Regression? | |
Status: | Open/New | Components: | Channels/chan_oss Core/BuildSystem |
Versions: | 13.19.2 15.2.2 | Frequency of Occurrence | |
Related Issues: | |||
Environment: | NetBSD 7.1.1 | Attachments: | ( 0) NetBSD_enable_oss.patch |
Description: | The channel driver {{chan_oss}} uses the Open Sound System (OSS). In NetBSD, OSS is not really available but emulated. This emulation happens via the shared library [{{libossaudio.so}}|http://netbsd.gw.com/cgi-bin/man-cgi?ossaudio+3]. Therefore, to use that emulation, {{chan_oss}} has to declare a dependency on OSS. This is done in {{chan_oss}} already. The script {{./configure}} helps to detect its presence. However, in {{./configure}} only the presence of the header file is tested. Therefore, OSS_LIB stays empty, {{-lossaudio}} is not send to the linker when chan_oss is made, and therefore the final {{chan_oss}} library does not declare a dependency to {{-lossaudio}}. This can be double-checked via the tool {{ldd}}.
On the command-line interface (CLI) of Asterisk, a warning is shown that {{chan_oss}} could not be loaded: 'Undefined PLT symbol "_oss_ioctl" (symnum = 64)'. The trick is to specify a symbol in {{./configure}}. Then, AST_EXT_LIB_CHECK checks also the library, and OSS_LIB=-lossaudio. This issue was reported in April 2002, six years ago. | ||
Comments: | By: Asterisk Team (asteriskteam) 2018-03-06 12:59:59.618-0600 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]. |