search for: ctime_r

...perspective for llvm's build farm. However there are some target specific macros: #define C_LINUX 1 #define FPU_WORDS_BIGENDIAN 0 #define WORDS_BIGENDIAN 0 Also SIZEOF_INT, SIZEOF_LONG,... but they are only used if the system doesn't have a proper <stdint.h> Also not sure of this: /* ctime_r takes 2 arguments */ #define HAVE_CTIME_R_2 1 What OS and CPU do the machines on llvm's buildfarm have? We could try a config.h that works on Linux (or MacOSX), and try to apply that to all, though there might be (non-obvious) failures. Any solutions to having these macros defined in the LLVM...

...target specific macros: >> #define C_LINUX 1 >> #define FPU_WORDS_BIGENDIAN 0 >> #define WORDS_BIGENDIAN 0 >> Also SIZEOF_INT, SIZEOF_LONG,... but they are only used if the system >> doesn't have a proper <stdint.h> >> Also not sure of this: >> /* ctime_r takes 2 arguments */ >> #define HAVE_CTIME_R_2 1 >> >> What OS and CPU do the machines on llvm's buildfarm have? We could >> try a >> config.h that works on Linux (or MacOSX), and try to apply >> that to all, though there might be (non-obvious) failures. >...

...> However there are some target specific macros: > #define C_LINUX 1 > #define FPU_WORDS_BIGENDIAN 0 > #define WORDS_BIGENDIAN 0 > Also SIZEOF_INT, SIZEOF_LONG,... but they are only used if the system > doesn't have a proper <stdint.h> > Also not sure of this: > /* ctime_r takes 2 arguments */ > #define HAVE_CTIME_R_2 1 > > What OS and CPU do the machines on llvm's buildfarm have? We could > try a > config.h that works on Linux (or MacOSX), and try to apply > that to all, though there might be (non-obvious) failures. > > Any solutions to...

...igned */ > #define HAVE_ATTRIB_ALIGNED 1 > > /* attrib packed */ > #define HAVE_ATTRIB_PACKED 1 > > /* have bzip2 */ > /* #define HAVE_BZLIB_H 1 */ > > /* ancillary data style fd pass */ > /* #define HAVE_CONTROL_IN_MSGHDR 1 */ > > /* Define to 1 if you have the `ctime_r' function. */ > /* #define HAVE_CTIME_R 1 */ > > /* ctime_r takes 2 arguments */ > /* #define HAVE_CTIME_R_2 1 */ > > /* ctime_r takes 3 arguments */ > /* #undef HAVE_CTIME_R_3 */ > > /* Define to 1 if you have the <dlfcn.h> header file. */ > /* #define HAVE_...

Chris Lattner wrote: > One way to do this is to add a "cut down" version of the app to the > test suite. I disabled optional features in clamav-config.h > >> 2. GPL license. Chris? > > Any open source license that allows unrestricted redistribution is > fine in llvm-test Ok, I have created a script that automatically checks out ClamAV 0.92-stable source code

...mmap... yes IEEE Math Checks checking for fpclassify... no checking for fpclassify with <math.h>... yes checking for finite... yes checking for isinf... yes checking if IEEE math works out of the box... yes Resolve Portability Issues checking if realloc can deal with NULL... yes checking if ctime_r need special care to act posixly correct... no checking for the pthreads library -lpthreads... no checking whether pthreads work without any flags... no checking whether pthreads work with -Kthread... no checking whether pthreads work with -kthread... no checking for the pthreads library -llthread....

...00000000009 Base _ZNSt3__113basic_ostreamIcNS_11char_traitsIcEEED1Ev 0000000000000000 DF *UND* 000000000000003e Base _ZNSt3__116generic_categoryEv 0000000000000000 DF *UND* 0000000000000212 GLIBC_2.2.5 strsignal 0000000000000000 DF *UND* 0000000000000021 GLIBC_2.2.5 ctime_r 0000000000000000 DF *UND* 0000000000000014 GLIBC_2.2.5 posix_spawn_file_actions_destroy 0000000000000000 DF *UND* 0000000000000019 GLIBC_2.2.5 isatty 0000000000000000 DF *UND* 0000000000000080 Base _ZNKSt3__16locale9has_facetERNS0_2idE 0000000000000000 DF *UND* 0000000...

I have a lot of people whispering "zfs" in my virtual ear these days, and at the same time I have an irrational attachment to xfs based entirely on its lack of the 32000 subdirectory limit. I''m not afraid of ext4''s newness, since really a lot of that stuff has been in Lustre for years. So a-benchmarking I went. Results at the bottom:

Hello, I update my building scripts to build LLVM 4.0 RC1 (with clang, lldb, libc++, libc++abi, lld) on CentOS 6 and I got a lot of undefined symbols during linking LLDB. I'm using clang-3.9 and this configuration: -DLLVM_TARGETS_TO_BUILD="X86" -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_COMPILER=/usr/bin/clang -DCMAKE_CXX_COMPILER=/usr/bin/clang++

ChangeLog: ========= v2 => v3: a) Patch 1 data structure cleanups, header file include cleanups, IDA interface reuse and switching to device_create_with_groups(..) as per feedback from Greg Kroah-Hartman. b) Patch 7 signal documentation, sleep workaround removal and sysfs access API cleanups as per feedback from Michael S. Tsirkin. v1 => v2: @ http://lwn.net/Articles/563131/ a)

ChangeLog: ========= v2 => v3: a) Patch 1 data structure cleanups, header file include cleanups, IDA interface reuse and switching to device_create_with_groups(..) as per feedback from Greg Kroah-Hartman. b) Patch 7 signal documentation, sleep workaround removal and sysfs access API cleanups as per feedback from Michael S. Tsirkin. v1 => v2: @ http://lwn.net/Articles/563131/ a)

ChangeLog: ========= v2 => v3: a) Patch 1 data structure cleanups, header file include cleanups, IDA interface reuse and switching to device_create_with_groups(..) as per feedback from Greg Kroah-Hartman. b) Patch 7 signal documentation, sleep workaround removal and sysfs access API cleanups as per feedback from Michael S. Tsirkin. v1 => v2: @ http://lwn.net/Articles/563131/ a)

ChangeLog: ========= v2 => v3: a) Patch 1 data structure cleanups, header file include cleanups, IDA interface reuse and switching to device_create_with_groups(..) as per feedback from Greg Kroah-Hartman. b) Patch 7 signal documentation, sleep workaround removal and sysfs access API cleanups as per feedback from Michael S. Tsirkin. v1 => v2: @ http://lwn.net/Articles/563131/ a)