RPCS3/llvm-mirror
1
0
Fork 0
mirror of https://github.com/RPCS3/llvm-mirror.git synced 2024-10-20 03:23:01 +02:00
Code Issues Projects Releases Wiki Activity
ecf7881af3
llvm-mirror/lib/Support/Unix
History
Chandler Carruth ecf7881af3 Remove all checking for the various terminfo headers (term.h and 
curses.h). Finding these headers is next to impossible. For example, on
Debian systems libtinfo-dev provides the terminfo reading library we
want, but *not* term.h. For the header, you have to use libncurses-dev.
And libncursesw-dev provides a *different* term.h in a different
location!

These headers aren't worth it. We want two functions the signatures of
which are clearly spec'ed in sys-v and other documentation. Just declare
them ourselves and call them. This should fix some debian builders and
provide better support for "minimal" debian systems that do want color
autodetection.

llvm-svn: 188165
2013-08-12 10:40:11 +00:00
..
Host.inc revert r147542 after comments from Joerg Sonnenberger 2012-01-05 18:28:46 +00:00
Memory.inc Revert "[PowerPC] Improve consistency in use of __ppc__, __powerpc__, etc." 2013-07-26 22:13:57 +00:00
Mutex.inc
Path.inc Check for $PWD in llvm::sys::current_path. 2013-08-10 00:50:57 +00:00
Process.inc Remove all checking for the various terminfo headers (term.h and 2013-08-12 10:40:11 +00:00
Program.inc Add missing 'n'. 2013-07-26 20:44:45 +00:00
README.txt
RWMutex.inc
Signals.inc Revert part of 186302 to fix buildbots. 2013-07-15 04:37:54 +00:00
system_error.inc
ThreadLocal.inc
TimeValue.inc Fix a FIXME about the format and add a test. 2013-07-11 15:35:23 +00:00
Unix.h Remove dead or useless header checks from cmake and autoconf 2013-07-26 16:54:23 +00:00
Watchdog.inc Add a new watchdog timer interface. The interface does not permit handling timeouts, so 2013-03-26 01:27:52 +00:00

README.txt 

llvm/lib/Support/Unix README
===========================

This directory provides implementations of the lib/System classes that
are common to two or more variants of UNIX. For example, the directory
structure underneath this directory could look like this:

Unix           - only code that is truly generic to all UNIX platforms
  Posix        - code that is specific to Posix variants of UNIX
  SUS          - code that is specific to the Single Unix Specification
  SysV         - code that is specific to System V variants of UNIX

As a rule, only those directories actually needing to be created should be
created. Also, further subdirectories could be created to reflect versions of
the various standards. For example, under SUS there could be v1, v2, and v3
subdirectories to reflect the three major versions of SUS.