1. 23 Nov, 2018 4 commits
  2. 28 Oct, 2018 1 commit
  3. 16 Oct, 2018 1 commit
  4. 03 Oct, 2018 1 commit
  5. 01 Oct, 2018 1 commit
  6. 05 Sep, 2018 1 commit
  7. 01 Sep, 2018 3 commits
  8. 20 Aug, 2018 1 commit
  9. 16 Aug, 2018 4 commits
    • Debarshi Ray's avatar
    • Debarshi Ray's avatar
      Prepare 3.29.91 · 4277e074
      Debarshi Ray authored
    • Debarshi Ray's avatar
      build: Silence warning about _FORTIFY_SOURCE requiring optimization · 9214b289
      Debarshi Ray authored
      Building with AX_CHECK_ENABLE_DEBUG([yes]), which is what happens by
      default for non-release builds, turns off compiler optimizations and
      overrides any optimization specified via CFLAGS in the build
      environment. This means that the nightly Flatpaks, and almost all
      other non-release builds, are built without any optimization. This
      triggers a warning about _FORTIFY_SOURCE requiring optimization, on
      distributions that build with _FORTIFY_SOURCE, when running
      g-ir-scanner to generate Goa-1.0.gir.
      Since g-ir-scanner uses Python's distutils.ccompiler, the compiler
      flags with which Python itself was built gets tagged into the
      compilation of the generated code that's used to generate the GIR. If
      the Python installation being used was built with _FORTIFY_SOURCE, the
      warning is triggered.
      It can be useful to turn off compiler optimizations to get a better
      debugging experience, but it becomes a problem if it stomps over the
      build environment while doing so. The person doing the builds should
      should get to decide between ease of debugging and other factors.
      After all, debugging is not the only thing that a developer does. One
      can use GDB reasonably well with the Autoconf default, which also
      happens to be what most distributions use, of "-g O2".
      This wouldn't have been such a problem if AX_CHECK_ENABLE_DEBUG
      attached its flags before the values from the environment instead of
      after, because in case of multiple -O options, the last such option is
      the one that's effective.
      Thankfully, "no" doesn't override the environment, which is what
      happens for release builds, and distributions generally set their own
      CFLAGS. Otherwise every single user-facing build would have been
      broken. Note that any release build without CFLAGS set in the
      environment would neither get debug symbols (ie., no "-g") nor any
      compiler optimization because AX_CHECK_ENABLE_DEBUG always suppresses
      the Autoconf defaults of "-g -O2".
      One solution could have been to default to "info" for non-release
      builds and recommend the use of --enable-debug=info while building from
      Git, but that would not address release builds without CFLAGS.
      Given that the only other thing the macro does is to define the NDEBUG
      pre-processor macro when debugging is set to "no", which isn't widely
      used in the GLib-based GNOME platform [1], it seems better to just
      remove it altogether.
      [1] glib/gio/xdgmime is the only widely used code path where assert(3)
          is used. It's also used in gio/kqueue/dep-list.c, which is
          *BSD-specific and in GTK+'s Broadway backend. All those can
          probably be replaced with g_assert*.
    • Debarshi Ray's avatar
      build: Turn off -Wcast-function-type · 2b981374
      Debarshi Ray authored
      GCC 8 introduced -Wcast-function-type. It is enabled by -Wextra, which
      is on the AX_COMPILER_FLAGS list. Unfortunately, this cannot be sanely
      used with the GNOME platform. It is exceedingly common practice to
      specify a function as a callback that ignores some of the trailing
      parameters passed to it. In fact, the following snippet that's part of
      the g_list_copy_deep documentation triggers -Wcast-function-type:
        another_list = g_list_copy_deep (list,
                                         (GCopyFunc) g_object_ref,
      Disabling warnings like this does go against the recommendation of the
      AX_COMPILER_FLAGS documentation, which suggests the use of #pragmas
      instead. However, unlike passing the flags through the command line,
      attempts to ignore -Wcast-function-type through a #pragma will trigger
      -Wpragmas on older versions of GCC, and, ironically, using
      G_GNUC_CHECK_VERSION to conditionally disable it on newer compilers
      will trigger -Wexpansion-to-defined, again, because of -Wextra.
  10. 20 Jul, 2018 5 commits
  11. 19 Jul, 2018 3 commits
  12. 18 Jul, 2018 5 commits
  13. 27 Jun, 2018 1 commit
  14. 17 Apr, 2018 9 commits