[asterisk-dev] Which enviroments are supported, really?

[Corey Farrell]

The only wiki page I found on non-Linux is [1].  Probably the clearest 
statement is in the README.md [2].  I think we should probably add a 
more negative spin to the comments about Other platforms, at minimum 
state that they are not actively tested and may break at any time.

As for jenkins2.asterisk.org, only Linux is tested.  The active build 
agents are:

  * CentOS 7 (x86 and x86_64)
  * Fedora 25 (x86_64)
  * Ubuntu 16 (x86_64)

Ubuntu 14 (x86_64 and x86) is listed in CI but they have been offline 
for a while so they aren't currently tested automatically.  I've 
recently made a change which caused CentOS 6 to stop building, I got a 
report as soon as the next RC was released.  I'm confused by your 
statement that things don't work in Fedora unless you're trying to 
compile with LLVM or clang (ASTERISK-26205).  All active versions of 
Fedora should work, I'm guessing many inactive (end of life) versions of 
Fedora will also work.  For OSX I've made some changes recently to get 
compile working, never went beyond that.  My goal was simply to be able 
to run 'make && git review' from OSX, I've never attempted to run the 
binaries.

GNU bash is required by some scripts (they have #!/bin/bash). Any 
scripts that have '#!/bin/sh' should not use bash only features but I'm 
not sure if this is ever tested.  I'm not aware of any continuous 
testing done with compilers other than GCC.

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+on+%28Open%29Solaris
[2] https://github.com/asterisk/asterisk/#supported-operating-systems

On 01/21/2018 08:58 AM, Alexander Traud wrote:
> Recently, I was hit by a missing dependency of an external library (ASTERISK-27475). Because I was not able to resolve the issue otherwise, I re-visited the first-time experience of Asterisk, thinking that should solve my issue for sure.
>
> wget downloads.asterisk.org/pub/telephony/asterisk/asterisk-13-current.tar.gz
> tar -zxf asterisk-*
> cd asterisk-*
> sudo ./contrib/scripts/install_prereq install
> ./configure --with-pjproject-bundled
> make
> sudo make install samples config
> sudo asterisk -c
>
> Those eight steps are the path for a novice user to get Asterisk going. Consequently, those steps have to succeed in a supported environment, without a single error and should not give warnings.
>
> In OpenBSD, FreeBSD, and Fedora - with the current release (Asterisk 13.19 or 15.2) - these steps lead into errors. Asterisk is not even built! Furthermore, external libraries are not found by the script configure, the wrong ones are installed, and (even essential) ones are missing. Make errors out, PJProject and Asterisk are not built. Even when all issues are fixed or circumvented, the command-line interface of Asterisk prints not only warnings but several errors in such a standard installation.
>
> I contributed back many of my fixes to the current branches already. So the next releases should give a better out-of-the-box experience. However, all those issues could have been found by static testing, just executing the above commands on a virtual machine. Looking at the amount of issues, I asked myself whether I am doing something wrong. Especially as diagnosis revealed that some issues were 18 months old. Therefore: Which environments (platform, shell, and compiler) are really supported by the Asterisk team (has to work) and what is community contributed (should work)?
>
>     shell: GNU bash
> compiler: GCC
> platform: CentOS 7
>
> That is used by the continuous integration machine(s) and FreePBX currently. What else has to work? I do not earn a penny because of Asterisk. I do not want to waste time with a so lala supported environment. There must be a wiki entry, blog post, video, or mail summarizing the environments. For some reason, I was not able to find it, yet.
>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20180121/10da7c7e/attachment.html>