OpenBSD X11 changes summary for 2016-07-24 to 2016-07-31 inclusive
==================================================================

Makefile                                kdrive
lib                                     xserver

== Makefile ========================================================== 01/04 ==

  http://cvsweb.openbsd.org/cgi-bin/cvsweb/X11/Makefile

Makefile


  > Merge the build of Xephyr in the main xserver build.
  > Recent X server doesn't require to build the DIX with different
  > options for xfree86 and kdrive.
  > Tested for beeing a no-op on m88k by Kenji Aoyama. Thanks (matthieu@)

== kdrive ============================================================ 02/04 ==

  http://cvsweb.openbsd.org/cgi-bin/cvsweb/X11/kdrive

kdrive

  - Makefile.bsd-wrapper                  

  > Merge the build of Xephyr in the main xserver build.
  > Recent X server doesn't require to build the DIX with different
  > options for xfree86 and kdrive.
  > Tested for beeing a no-op on m88k by Kenji Aoyama. Thanks (matthieu@)

== lib =============================================================== 03/04 ==

  http://cvsweb.openbsd.org/cgi-bin/cvsweb/X11/lib

lib

  ~ mesa/src/gallium/auxiliary/rtasm/rtasm_execmem.c
  ~ mesa/src/mapi/u_execmem.c             ~ mesa/src/mesa/main/execmem.c

  > Disable the code that allocates W|X memory.  There is fallback code that
  > gets used if allocating W|X memory fails, which is probably a bit slower.
  > However, that is much better than commit a W^X violation which currently
  > gets you killed.
  > ok jca@ (kettenis@)

== xserver =========================================================== 04/04 ==

  http://cvsweb.openbsd.org/cgi-bin/cvsweb/X11/xserver

xserver

  ~ Makefile.bsd-wrapper                  

  > Merge the build of Xephyr in the main xserver build.
  > Recent X server doesn't require to build the DIX with different
  > options for xfree86 and kdrive.
  > Tested for beeing a no-op on m88k by Kenji Aoyama. Thanks (matthieu@)

===============================================================================
_______________________________________________
owc mailing list
[email protected]
http://www.squish.net/mailman/listinfo/owc

Reply via email to