1. 05 Jun, 2017 2 commits
  2. 23 Apr, 2016 1 commit
  3. 13 Feb, 2016 1 commit
  4. 27 Jan, 2016 1 commit
  5. 14 Dec, 2015 1 commit
  6. 30 Nov, 2015 4 commits
  7. 23 Sep, 2015 1 commit
  8. 29 Jul, 2014 1 commit
  9. 20 Jul, 2014 1 commit
  10. 21 Oct, 2013 2 commits
    • Guillem Jover's avatar
      Add funopen() function · f41fdcf1
      Guillem Jover authored
      This is a wrapper over the glibc fopencookie() function.
      
      We diverge from the FreeBSD, OpenBSD and DragonFlyBSD declarations,
      because seekfn() there wrongly uses fpos_t, assuming it's an integral
      type, and any code using that on a system where fpos_t is a struct
      (such as GNU-based systems or NetBSD) will fail to build. In which case,
      as the code has to be modified anyway, we might just as well use the
      correct declaration.
      f41fdcf1
    • Guillem Jover's avatar
      build: Set subdir-objects automake option · ee04e8de
      Guillem Jover authored
      Bump automake minimal version to 1.9.
      ee04e8de
  11. 14 Jul, 2013 3 commits
  12. 08 Jun, 2013 1 commit
    • Guillem Jover's avatar
      Force setproctitle() into .init_array section · 6faea4d2
      Guillem Jover authored
      The GNU .init_array support is an extension over the standard System V
      ABI .init_array support, which passes the main() arguments to the init
      function.
      
      This support comes in three parts. First the dynamic linker (from glibc)
      needs to support it. Then function pointers need to be placed in the
      section, for example by using __attribute__((constructor)), that the
      compiler (gcc or clang for example) might place in section .ctors and
      the linker (from binutils) will move to .init_array on the output
      object, or by placing them directly into .init_array by the compiler
      when compiling. If this does not happen and the function pointers end
      up in .ctors, then they will not get passed the main() arguments, which
      we do really need in this case.
      
      But this relies on recent binutils or gcc having native .init_array
      support, and not having it disabled through --disable-initfini-array.
      
      To guarantee we get the correct behaviour, let's just place the function
      pointer in the .init_array section directly, so we only require a recent
      enough glibc.
      
      Fixes: https://bugs.freedesktop.org/show_bug.cgi?id=65029
      6faea4d2
  13. 27 May, 2013 3 commits
  14. 03 Jun, 2012 1 commit
  15. 29 May, 2012 8 commits