Skip to content
Snippets Groups Projects
  1. May 03, 2015
    • Diederik de Groot's avatar
      Update configure.ac/Makefile for clang · 305ce3de
      Diederik de Groot authored
      Created autoconf/ast_check_raii.m4: contains AST_CHECK_RAII which
      checks compiler requirements for RAII:
      gcc: -fnested-functions support
      clang: -fblocks (and if required -lBlocksRuntime)
      The original check was implemented in configure.ac and now has it's
      own file. This function also sets C_COMPILER_FAMILY to either gcc or
      clang for use by makefile
      
      Created autoconf/ast_check_strsep_array_bounds.m4 (contains
      AST_CHECK_STRSEP_ARRAY_BOUNDS):
      which checks if clang is able to handle the optimized strsep & strcmp
      functions (linux). If not, the standard libc implementation should be
      used instead. Clang + the optimized macro's work with:
      strsep(char *, char []), but not with strsepo(char *, char *).
      Instead of replacing all the occurences throughout the source code,
      not using the optimized macro version seemed easier
      
      See 'define __strcmp_gc(s1, s2, l2) in bits/string2.h':
      llvm-comment: Normally, this array-bounds warning are suppressed for
      macros, so that unused paths like the one that accesses __s1[3] are
      not warned about.  But if you preprocess manually, and feed the
      result to another instance of clang, it will warn about all the
      possible forks of this particular if statement. Instead of switching
      of this optimization, another solution would be to run the preproces-
      sing step with -frewrite-includes, which should preserve enough
      information so that clang should still be able to suppress the diag-
      nostic at the compile step later on.
      
      See also "https://llvm.org/bugs/show_bug.cgi?id=20144"
      See also "https://llvm.org/bugs/show_bug.cgi?id=11536"
      
      Makefile.rules: If C_COMPILER_FAMILY=clang then add two warning
      suppressions:
      -Wno-unused-value
      -Wno-parentheses-equality
      In an earlier review (reviewboard: 4550 and 4554), they were deemed a
      nuisace and less than benefitial.
      
      configure.ac:
      Added AST_CHECK_RAII() see earlier
      Added AST_CHECK_STRSEP_ARRAY_BOUNDS() see earlier
      Removed moved content
      
      ASTERISK-24917
      Change-Id: I12ea29d3bda2254ad3908e279b7effbbac6a97cb
      305ce3de
  2. Jul 18, 2014
  3. Jun 20, 2014
  4. Mar 14, 2013
  5. Jan 29, 2013
  6. May 14, 2012
  7. Feb 16, 2012
  8. Jan 14, 2012
  9. Oct 06, 2011
    • Richard Mudgett's avatar
      Merged revisions 339720 via svnmerge from · 6e5f97df
      Richard Mudgett authored
      https://origsvn.digium.com/svn/asterisk/branches/10
      
      ................
        r339720 | rmudgett | 2011-10-06 17:58:40 -0500 (Thu, 06 Oct 2011) | 27 lines
        
        Merged revisions 339719 via svnmerge from 
        https://origsvn.digium.com/svn/asterisk/branches/1.8
        
        ........
          r339719 | rmudgett | 2011-10-06 17:47:50 -0500 (Thu, 06 Oct 2011) | 20 lines
          
          Fix regression in configure script for libpri capability checks.
          
          JIRA AST-598 added the PRI_L2_PERSISTENCE option to fix BRI PTMP TE layer
          2 persistence issues with some telcos.  ASTERISK-18535 attempted to fix
          the unexpected requirement that libpri *must* have that feature to work
          with Asterisk.  The AST_EXT_LIB_SETUP_DEPENDENT lines made the PRI
          optional features required.  Unfortunately, I thought
          AST_EXT_LIB_SETUP_DEPENDENT didn't do anything useful for libpri and
          deleted those lines for libpri.  The result was the HAVE_PRI_xxx defines
          that control the ability to use optional libpri features were also
          deleted.
          
          * Created AST_EXT_LIB_SETUP_OPTIONAL configuration macro to allow optional
          features in a library that the source code could take advantage of if the
          code supports the feature.
          
          (closes issue ASTERISK-18687)
          Reported by: Norbert
          Tested by: rmudgett
        ........
      ................
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@339721 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      6e5f97df
  10. May 04, 2011
  11. Jan 09, 2011
  12. Oct 07, 2010
  13. Jul 26, 2010
  14. Jul 23, 2010
  15. Jul 17, 2010
  16. Jul 15, 2010
  17. Jun 23, 2010
  18. Jun 13, 2010
    • Tzafrir Cohen's avatar
      bashism in configure script · 2743e9b2
      Tzafrir Cohen authored
      Theoretically the ./configure script is a pure bourne-shell script.
      Practically it may be run by bash if /bin/sh is not good enough. But we should not count on it. See bug report for the gory details.
      
      (closes issue #17485)
      Patches:
            0001-remove-bashism-from-ast_check_pwlib.m4.patch uploaded by tzafrir (license 46)
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@270184 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      2743e9b2
  19. Jun 04, 2010
  20. May 17, 2010
  21. May 09, 2010
  22. Aug 27, 2009
  23. Jun 30, 2009
    • Russell Bryant's avatar
      Move Asterisk-addons modules into the main Asterisk source tree. · c511a267
      Russell Bryant authored
      Someone asked yesterday, "is there a good reason why we can't just put these
      modules in Asterisk?".  After a brief discussion, as long as the modules are
      clearly set aside in their own directory and not enabled by default, it is
      perfectly fine.
      
      For more information about why a module goes in addons, see README-addons.txt.
      
      chan_ooh323 does not currently compile as it is behind some trunk API updates.
      However, it will not build by default, so it should be okay for now.
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@204413 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      c511a267
  24. Jun 16, 2009
  25. May 26, 2009
  26. May 04, 2009
  27. Mar 17, 2009
  28. Mar 10, 2009
  29. Feb 18, 2009
    • Jeff Peeler's avatar
      Modify h323 to build against PTLib as well as the older PWLib · c8fe75da
      Jeff Peeler authored
      Several changes in PTLib have occurred requiring build time detection. Changes
      accounted for include the library name change, config option change, install
      location change, and a boolean type change which is handled by ast_ptlib.h.
      Also, the sed check has been modified to properly work with autoconf >= 2.62.
      
      (closes issue #14224)
      Reported by: bergolth
      Patches:
            asterisk-autoconf-sed.patch uploaded by bergolth (license 661)
            asterisk-pwlib-v3.patch uploaded by bergolth (license 661)
      Tested by: jpeeler
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@177162 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      c8fe75da
  30. Jan 29, 2009
  31. Nov 26, 2008
  32. Nov 13, 2008
  33. Nov 12, 2008
Loading