forked from OSchip/llvm-project
21e67472c2
Summary: When clang is used under GNU/Linux in a chroot without /proc mount, it falls back on the BSD method. However, since the buf variable is used twice and fails with snprintf to produce the correct path. When called as relatived (ie ./clang), it was failing with: "" -cc1 [...] -x c++ x.cc error: unable to execute command: Executable "" doesn't exist! I also took the opportunity to simply the code (the first arg of test_dir was useless). Reviewers: rafael Reviewed By: rafael CC: cfe-commits Differential Revision: http://llvm-reviews.chandlerc.com/D2361 llvm-svn: 196791 |
||
|---|---|---|
| .. | ||
| Host.inc | ||
| Memory.inc | ||
| Mutex.inc | ||
| Path.inc | ||
| Process.inc | ||
| Program.inc | ||
| README.txt | ||
| RWMutex.inc | ||
| Signals.inc | ||
| ThreadLocal.inc | ||
| TimeValue.inc | ||
| Unix.h | ||
| Watchdog.inc | ||
| system_error.inc | ||
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.