Changes between Version 100 and Version 101 of FAQ


Ignore:
Timestamp:
Aug 30, 2010, 7:02:51 PM (14 years ago)
Author:
jeremyhu (Jeremy Huddleston Sequoia)
Comment:

Update the state of RANDR

Legend:

Unmodified
Added
Removed
Modified

  • FAQ

    v100 v101  
    145145MacPorts does not use the X11 '''client''' libraries provided by the system, but installs its own copy. Reasons to do so are consistent support for older machines and not violating `/usr/X11`. Most X11 related software is newer in MacPorts anyway.
    146146
    147 Don't be scared away, MacPorts will still use the X11 server provided by the system.
     147Don't be scared away, MacPorts built applications are still compatible with the X11 server provided by the system.
    148148
    149149=== What does 'Xlib:  extension "RANDR" missing on display "/tmp/launch-XXXXXX/:0"' mean? === #randr
    150150
    151 Many X11 programs try to use the RANDR extension, and print this warning when it is not available. The RANDR extension is never available on Mac OS X, so when you use these programs you will see this message. It's harmless and you should ignore it.
     151Many X11 programs try to use the RANDR extension, and print this warning when it is not available. The RANDR extension is available in development builds of the X11 server and will eventually make its way into a production release.  If you want to test out RANDR support, install the xorg-server-devel port.  This warning is harmless and safe to ignore.
    152152
    153153=== Python fails to build === #pythonfails