summaryrefslogtreecommitdiffstats
path: root/llvm/autoconf/configure.ac
Commit message (Collapse)AuthorAgeFilesLines
...
* Remove all checking for the various terminfo headers (term.h andChandler Carruth2013-08-121-5/+0
| | | | | | | | | | | | | | | | 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
* Target a minimal terminfo library rather than necessarily a full cursesChandler Carruth2013-08-121-14/+14
| | | | | | | | | | | | | | | | | | | | library for color support detection. This still will use a curses library if that is all we have available on the system. This change tries to use a smaller subset of the curses library, specifically the subset that is on some systems split off into a separate library. For example, if you install ncurses configured --with-tinfo, a 'libtinfo' is install that provides just the terminfo querying functionality. That library is now used instead of curses when it is available. This happens to fix a build error on systems with that library because when we tried to link ncurses into the binary, we didn't pull tinfo in as well. =] It should also provide an easy path for supporting the NetBSD libterminfo library, but as I don't have access to a NetBSD system I'm leaving adding that support to those folks. llvm-svn: 188160
* Add support for linking against a curses library when available andChandler Carruth2013-08-071-0/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | using it to detect whether or not a terminal supports colors. This replaces a particularly egregious hack that merely compared the TERM environment variable to "dumb". That doesn't really translate to a reasonable experience for users that have actually ensured their terminal's capabilities are accurately reflected. This makes testing a terminal for color support somewhat more expensive, but it is called very rarely anyways. The important fast path when the output is being piped somewhere is already in place. The global lock may seem excessive, but the spec for calling into curses is *terrible*. The whole library is terrible, and I spent quite a bit of time looking for a better way of doing this before convincing myself that this was the fundamentally correct way to behave. The damage of the curses library is very narrowly confined, and we continue to use raw escape codes for actually manipulating the colors which is a much sane system than directly using curses here (IMO). If this causes trouble for folks, please let me know. I've tested it on Linux and will watch the bots carefully. I've also worked to account for the variances of curses interfaces that I could finde documentation for, but that may not have been sufficient. llvm-svn: 187874
* Link with -rdynamic instead of -Wl,-export-dynamic.Bob Wilson2013-08-021-2/+2
| | | | | | | | | | | | | | | Recent versions of the OS X linker support this but follow the existing OS X linker convention of using an underscore in the option name, i.e., -export_dynamic. Rather than changing our configure scripts to check for that alternate spelling, it is simpler to just use the compiler's -rdynamic option and let it deal with translating that to the appropriate linker option. One potential disadvantage of this approach is that the compiler will typically ignore -rdynamic on platforms where it is not supported, so the HAVE_LINK_EXPORT_DYNAMIC in config.h will not necessarily show whether that option has any effect or not. I don't see any in-tree uses of that macro, so I'm assuming it is OK. llvm-svn: 187686
* Remove dead or useless header checks from cmake and autoconfReid Kleckner2013-07-261-4/+4
| | | | | | | | | | On Windows, this improves clean cmake configuration time on my workstation from 1m58s to 1m32s, which is pretty significant. There's probably more that can be done here, but this is the low hanging fruit. Eric volunteered to regenerate ./configure for me. llvm-svn: 187209
* Remove the mblaze backend from llvm.Rafael Espindola2013-07-251-6/+1
| | | | | | Approval in here http://lists.cs.uiuc.edu/pipermail/llvmdev/2013-July/064169.html llvm-svn: 187145
* No ',' between programs.Eric Christopher2013-07-081-1/+1
| | | | llvm-svn: 185867
* Find xdot or xdot.py.Matt Arsenault2013-07-081-6/+6
| | | | | | Ubuntu installs this as xdot, so finding xdot.py would fail. llvm-svn: 185860
* Reapply r185601 with a fix for the cmake build.Eric Christopher2013-07-041-0/+1
| | | | llvm-svn: 185605
* Temporarily revert 185601 as it caused cmake build regressions.Eric Christopher2013-07-041-1/+0
| | | | llvm-svn: 185603
* Add support for futimens for platforms that don't support futimes.Eric Christopher2013-07-041-0/+1
| | | | | | Patch by pashev.igor. llvm-svn: 185601
* The build system is currently miss-identifying GNU/kFreeBSD as FreeBSD.Sylvestre Ledru2013-07-011-2/+9
| | | | | | | | | | | | | | | | | This kind of simplification is sometimes useful, but in general it's not correct. As GNU/kFreeBSD is an hybrid system, for kernel-related issues we want to match the build definitions used for FreeBSD, whereas for userland-related issues we want to match the definitions used for other systems with Glibc. The current modification adjusts the build system so that they can be distinguished, and explicitly adds GNU/kFreeBSD to the build checks in which it belongs. Fixes bug #16444. Patch by Robert Millan in the context of Debian. llvm-svn: 185311
* Add an autoconf option for turning on -gsplit-dwarf by defaultEric Christopher2013-06-251-0/+13
| | | | | | | | | | | | | when building llvm. This saves quite a bit of time and space when linking. Please report any problems via bugzilla. Caveats: a) This will only work on linux b) This requires a fairly new binutils c) This requires a fairly new gdb llvm-svn: 184808
* Don't define LLVM_LIBDIR, it is not used anymore.Rafael Espindola2013-06-111-5/+1
| | | | llvm-svn: 183769
* Make R600 non-experimental.Rafael Espindola2013-05-221-2/+3
| | | | | | | The r600 backend has been in tree for some time now. Marking it as non-experimental to avoid accidental breakage. llvm-svn: 182442
* We're in 3.4 land now.Bill Wendling2013-05-071-2/+2
| | | | llvm-svn: 181350
* [SystemZ] Add to --enable-targets=allUlrich Weigand2013-05-061-1/+1
| | | | | | | | | This patch finally enables the SystemZ target in the default build (with --enable-targets=all). Patch by Richard Sandiford. llvm-svn: 181209
* [SystemZ] Add configure bitsUlrich Weigand2013-05-061-1/+6
| | | | | | | | | | This patch wires up the SystemZ target in configure, so that it can now be built using --enable-targets=systemz. It is not yet included in the default build (--enable-targets=all); this will be done by a follow-up patch. Patch by Richard Sandiford. llvm-svn: 181208
* Allow host triple to be correctly overridden in CMake buildsTim Northover2013-05-041-1/+1
| | | | | | | | | | | The intended semantics mirror autoconf, where the user is able to specify a host triple, but if it's left to the build system then "config.guess" is invoked for the default. This also renames the LLVM_HOSTTRIPLE define to LLVM_HOST_TRIPLE to fit in with the style of the surrounding defines. llvm-svn: 181112
* Autoconf: Compile cxxabi.h in C++ mode.Benjamin Kramer2013-05-031-1/+4
| | | | | | Should fix PR15877. llvm-svn: 181026
* Only use cxxabi.h's demangler, if it is actually available.Joerg Sonnenberger2013-04-271-1/+1
| | | | llvm-svn: 180684
* Add basic zlib support to LLVM. This would allow to use ↵Alexey Samsonov2013-04-231-0/+27
| | | | | | compression/uncompression in selected LLVM tools. llvm-svn: 180083
* Add AArch64 into $llvm_cv_target_arch in configure, reviewed by Tim ↵Jia Liu2013-04-221-0/+1
| | | | | | Northover & Eric Christopher llvm-svn: 180025
* Refine fenv.h handling: check if the desired macros exist, before usingJoerg Sonnenberger2013-03-251-0/+1
| | | | | | | it. NetBSD/ARM and TILE-Gx are examples for platforms that have an unusable fenv.h and this avoids the need for a blacklist. llvm-svn: 177865
* Turn anonymous type in anonymous union warning back on after cleaning upEric Christopher2013-03-151-2/+1
| | | | | | issues. llvm-svn: 177136
* configure: remove workaround for gcc's -Wno-maybe-uninitializedDmitri Gribenko2013-02-131-23/+5
| | | | | | | Since r174770 gcc version check is not needed because CXX_FLAG_CHECK implements the workaround itself. llvm-svn: 175080
* Conditionalize constant folding of math intrinsics on the availability of an ↵Owen Anderson2013-02-071-0/+1
| | | | | | implementation on the host. This is a little bit unfortunate, but until someone decides to implement a full libm for APFloat, we don't have a better way to get this functionality. llvm-svn: 174561
* Enable AArch64 as a target built by default.Tim Northover2013-02-041-1/+1
| | | | llvm-svn: 174322
* Pass CPPFLAGS/CFLAGS/CXXFLAGS from the environment of configure toPatrik Hagglund2013-02-041-0/+5
| | | | | | | | | | | | | | | | | Makefile.config. This is implied at the bottom of the help text of configure (besides CC/CXX/LDFLAGS, already passed to Makefile.config). For backward compatibility, the values of CFLAGS and CXXFLAGS defaults to empty, overriding the default values provided by autoconf (for example, '-g -O2' when CC=gcc'). $(CPP) is not used by our makefiles. Therefore, the value of CPP is not passed to Makefile.config, despite beeing mentioned by 'configure --help'. llvm-svn: 174313
* Recognize aarch64 for --enable-targets as advertised.Joerg Sonnenberger2013-02-031-0/+1
| | | | llvm-svn: 174288
* Add -Wno-nested-anon-types to -pedantic builds of LLVM. This Clang warningRichard Smith2013-01-311-1/+2
| | | | | | | | | | | | | | | | | | | catches uses of an extremely minor and widely-available C++ extension (which every C++ compiler I could find supports, but EDG and Clang reject in strict mode). The diagnosed code pattern looks like this: struct X { union { struct { int a; int b; } S; }; }; llvm-svn: 174103
* Add AArch64 as an experimental target.Tim Northover2013-01-311-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds support for AArch64 (ARM's 64-bit architecture) to LLVM in the "experimental" category. Currently, it won't be built unless requested explicitly. This initial commit should have support for: + Assembly of all scalar (i.e. non-NEON, non-Crypto) instructions (except the late addition CRC instructions). + CodeGen features required for C++03 and C99. + Compilation for the "small" memory model: code+static data < 4GB. + Absolute and position-independent code. + GNU-style (i.e. "__thread") TLS. + Debugging information. The principal omission, currently, is performance tuning. This patch excludes the NEON support also reviewed due to an outbreak of batshit insanity in our legal department. That will be committed soon bringing the changes to precisely what has been approved. Further reviews would be gratefully received. llvm-svn: 174054
* build: add --with-python optionSaleem Abdulrasool2013-01-301-0/+29
| | | | | | | | | | | This adds a new --with-python option to allow configuration of the python binary for building. If not specified, $PATH will be searched for common python binary names (python, python2, python3). If specified, and the path is not executable, it will attempt to search $PATH. Signed-off-by: Saleem Abdulrasool <compnerd@compnerd.org> Reviewed-by: Eric Christopher <echristo@gmail.com>, Daniel Dunbar <daniel@zuster.org> llvm-svn: 173890
* [autoconf]: Fix description in HAVE_CRASHREPORTER_INFO.NAKAMURA Takumi2013-01-301-2/+2
| | | | | | | http://llvm-reviews.chandlerc.com/D332 Signed-off-by: Saleem Abdulrasool <compnerd@compnerd.org> llvm-svn: 173879
* [autoconf] Fix m4 quoting for newer autotoolsNAKAMURA Takumi2013-01-301-36/+57
| | | | | | | | | This simply fixes up quoting of macro invocations to appease newer versions of autotools. http://llvm-reviews.chandlerc.com/D332 Signed-off-by: Saleem Abdulrasool <compnerd@compnerd.org> llvm-svn: 173878
* Disable Uninitialized Use Warnings for Broken gcc VersionsDavid Greene2013-01-151-2/+17
| | | | | | | | | | | | Some versions of gcc accept unsupported -W flags and run just fine if there are no warnings, but die with an unsupported flag error if a warning is encountered. gcc 4.3 and gcc 4.4 both exhibit this behavior for -Wno-maybe-uninitialized. Therefore, if the flag check for -Wno-maybe-uninitialized succeeds, only use -Wno-maybe-uninitialized if we are using gcc version 4.7 or greater. Use -Wno-uninitialized otherwise. llvm-svn: 172543
* Disable -Wuninitialized for gccDavid Greene2013-01-091-1/+21
| | | | | | | | | | | | | | If the compiler is gcc, disable variants of -Wuninitialized depending on the gcc version. This gets a lot of false positive warnings out of the build. Generate a new configure for the gcc -Wno-uninitialized fix. Pick up -Wno-uninitialized from configure Add the option -Wno[-maybe]-uninitialized as determined by configure. llvm-svn: 172006
* Configure: if we compile with clang, check that it is not brokenDmitri Gribenko2013-01-091-0/+26
| | | | | | | | | | | | | | | Some linux distibutions (for example, Mageia 2, Fedora 17) ship Clang that is essentially broken for the end user. Clang can not find or compile libstdc++ headers. The issue is that our configure prefers clang over gcc, thus selecting a broken Clang when a working GCC is available. Now we detect this issue by compiling a simple program. If it does not compile, configure stops with an error suggesting the user to select a different compiler. llvm-svn: 171975
* Fix a stray 'dnl' that my editor line-wrapped into this comment. ThanksChandler Carruth2013-01-051-2/+2
| | | | | | to filcab on IRC for spotting. llvm-svn: 171573
* Finally, fix the autoconf setup to allow for a missing clock_gettime;Chandler Carruth2013-01-051-3/+4
| | | | | | the source code should now be set up to handle this. llvm-svn: 171570
* Add time getters to the process interface for requesting the elapsedChandler Carruth2013-01-041-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | wall time, user time, and system time since a process started. For walltime, we currently use TimeValue's interface and a global initializer to compute a close approximation of total process runtime. For user time, this adds support for an somewhat more precise timing mechanism -- clock_gettime with the CLOCK_PROCESS_CPUTIME_ID clock selected. For system time, we have to do a full getrusage call to extract the system time from the OS. This is expensive but unavoidable. In passing, clean up the implementation of the old APIs and fix some latent bugs in the Windows code. This might have manifested on Windows ARM systems or other systems with strange 64-bit integer behavior. The old API for this both user time and system time simultaneously from a single getrusage call. While this results in fewer system calls, it also results in a lower precision user time and if only user time is desired, it introduces a higher overhead. It may be worthwhile to switch some of the pass timers to not track system time and directly track user and wall time. The old API also tracked walltime in a confusing way -- it just set it to the current walltime rather than providing any measure of wall time since the process started the way buth user and system time are tracked. The new API is more consistent here. The plan is to eventually implement these methods for a *child* process by using the wait3(2) system call to populate an rusage struct representing the whole subprocess execution. That way, after waiting on a child process its stats will become accurate and cheap to query. llvm-svn: 171551
* Update the configure scripts as well as the makefiles for the move fromChandler Carruth2013-01-021-1/+1
| | | | | | VMCore to IR. llvm-svn: 171360
* Update the copyright coredits -- Happy new year 2013!NAKAMURA Takumi2013-01-011-2/+2
| | | | llvm-svn: 171342
* Fix quoting in configure. Patch by Krzysztof Parzyszek!Benjamin Kramer2012-12-261-2/+2
| | | | llvm-svn: 171108
* Add options to disable building of ARCMT, Rewriter and Static AnalyzerRoman Divacky2012-12-131-0/+48
| | | | | | in clang. The default remains to build those. llvm-svn: 170134
* Fix a pasto.Eric Christopher2012-11-191-3/+3
| | | | | | Noticed by Dimitri Andric! llvm-svn: 168319
* Kick off 3.3 cycle for LLVM trunk.Benjamin Kramer2012-11-171-2/+2
| | | | llvm-svn: 168272
* Remove the CellSPU port.Eric Christopher2012-11-141-4/+2
| | | | | | Approved by Chris Lattner. llvm-svn: 167984
* Add mips64-* and mips64el-* triples to configure scriptsSimon Atanasyan2012-10-291-4/+6
| | | | | | as valid triples denote Mips target. llvm-svn: 166961
* Re-enable support for --program-prefix.Jordan Rose2012-10-011-0/+5
| | | | | | | | | The Apple buildbots have been modified not to pass --target, so they shouldn't choke on a default program prefix anymore. Patch by Rick Foos! llvm-svn: 164956
OpenPOWER on IntegriCloud