search for: enable_timestamps

Displaying 7 results from an estimated 7 matches for "enable_timestamps".

2016 Jun 28
3
ENABLE_TIMESTAMPS and update to CMake v3.5.2
I am in the middle of the fun and games of updating my out-of-tree sources to the LLVM head revisions, and after updating to CMake v3.5.2 I am now getting a warning that 'ENABLE_TIMESTAMPS' is being ignored. Has support for embedding the timestamp in the build been removed or is there a new way of configuring it? I generally build internal transitional builds with this enabled so that I can tell one build from another reasonably easily, especially when the corresponding sour...
2016 Jun 28
0
ENABLE_TIMESTAMPS and update to CMake v3.5.2
...On Tue, Jun 28, 2016 at 3:25 PM, Martin J. O'Riordan via llvm-dev <llvm-dev at lists.llvm.org> wrote: > I am in the middle of the fun and games of updating my out-of-tree sources > to the LLVM head revisions, and after updating to CMake v3.5.2 I am now > getting a warning that ā€˜ENABLE_TIMESTAMPSā€™ is being ignored. > > > > Has support for embedding the timestamp in the build been removed or is > there a new way of configuring it? I generally build internal transitional > builds with this enabled so that I can tell one build from another > reasonably easily, especially...
2012 Jul 13
2
[LLVMdev] Dealing with a corrupted /proc/self/exe link
...le discovery (the other one works well). Here is the patch: Index: autoconf/configure.ac =================================================================== --- autoconf/configure.ac (revision 160127) +++ autoconf/configure.ac (working copy) @@ -647,6 +647,20 @@ AC_DEFINE_UNQUOTED([ENABLE_TIMESTAMPS],$ENABLE_TIMESTAMPS, [Define if timestamp information (e.g., __DATE__) is allowed]) +dnl Enable reading of the "/proc/self/exe" link. +AC_ARG_ENABLE(proc-self-exe, + AS_HELP_STRING([--enable-proc-self-exe], + [Enable reading of the "/proc/self/ex...
2012 Jul 13
0
[LLVMdev] [llvm-commits] Dealing with a corrupted /proc/self/exe link
...re is the patch: > > > > Index: autoconf/configure.ac > =================================================================== > --- autoconf/configure.ac (revision 160127) > +++ autoconf/configure.ac (working copy) > @@ -647,6 +647,20 @@ > AC_DEFINE_UNQUOTED([ENABLE_TIMESTAMPS],$ENABLE_TIMESTAMPS, > [Define if timestamp information (e.g., __DATE__) is allowed]) > > +dnl Enable reading of the "/proc/self/exe" link. > +AC_ARG_ENABLE(proc-self-exe, > + AS_HELP_STRING([--enable-proc-self-exe], > + [Enable readi...
2016 May 03
8
RFC: Should the default LLVM build be deterministic?
Hello LLVM-Dev, Today if a user checks out LLVM, configures with no options specified, and builds the result is non-deterministic. Meaning if you clean and build again the binaries are not identical. This impacts all target platforms equally and is caused by the default value of LLVM_ENABLE_TIMESTAMPS being On. I believe this is incorrect behavior, and Iā€™m curious what the wider community thinks. It is my belief that the default LLVM configuration (meaning no options specified) should be deterministic, and that any option in our build/configuration system that can impact determinism should be...
2012 Jul 13
2
[LLVMdev] [llvm-commits] Dealing with a corrupted /proc/self/exe link
...; >> >> Index: autoconf/configure.ac >> =================================================================== >> --- autoconf/configure.ac (revision 160127) >> +++ autoconf/configure.ac (working copy) >> @@ -647,6 +647,20 @@ >> AC_DEFINE_UNQUOTED([ENABLE_TIMESTAMPS],$ENABLE_TIMESTAMPS, >> [Define if timestamp information (e.g., __DATE__) is allowed]) >> >> +dnl Enable reading of the "/proc/self/exe" link. >> +AC_ARG_ENABLE(proc-self-exe, >> + AS_HELP_STRING([--enable-proc-self-exe], >> +...
2014 Apr 04
2
[LLVMdev] successful full recurse of mips32
We have NFS mounted drives. I first build an clang/llvm hosted compiler for Mips linux using the clang/llvm linux x86 compiler. Call this clang1. then in directory recurse on Mips host, I place this clang1 compiler and build clang2. then i rename recurse to recurse1 and create a new recurse directory. in recurse I copy clang2 from recurse1 to a recurse but name it clang1. then i build