I am not about the bugs themselves. I am going to fix and/or report them. I fixed already several of them. And more are coming. However, I am interested which environments are supported.
After a mayor release like Asterisk 15, I would have expected that someone does a cross-check before the 15.1 release, at least before the 15.2 release. Those eight steps are automatic stuff. All one has to do is to setup a new virtual machine, with a vanilla installation. Then, the actual work is to double-check the results (of configure, make, and make install). Obviously, nobody does this. Even those who do the ports, either do not understand the result of configure correctly or ignore it without reporting. For example, in BSD, the external library libedit is the default, no need to build the internal one of Asterisk. However, ./configure of Asterisk fails to find it and (tries to) build its own one. That is an issue since commit 7d4ccea (summer 2012). I was so surprised about the number of issues. One can learn so much by doing interoperability tests. And in this case, this learning is near to free. > Ubuntu 16.04 LTS (x86_64) That is great news (for me), because that is my main platform. Consequently, I do not have to consider to move. > ... Fedora ... ASTERISK-27598, for more details see ASTERISK-27599 That was reported in May 2017: ASTERISK-26981. Actually, the first report was in December 2015: ASTERISK-24597. > ... GNU bash ... ASTERISK-27606 -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
