search for: have_

Hello. I see many discrepancies in config.h file generated by CMake and autoheader. Most of them are following: In autofoo-generated config: > /* Define to 1 if you have the `<name>' function. */ > #define HAVE_<name> 1 > but in CMake-generated: > #undef HAVE_<name> > This happens because in config.h.cmake (config.h.in analog) these functions just are not checked for. Another difference: autofoo sets this by default: > #define ENABLE_PIC 1 > while CMake not. There are many ot...

Henrik Bach wrote: > Hi > > I noticed that these defines (line 35 to 37) are hardcoded in the > DataTypes.h include file: > ---------------- > #define HAVE_SYS_TYPES_H 1 > #define HAVE_INTTYPES_H 1 > #define HAVE_STDINT_H 1 > ---------------- > > Shouldn't they have be defined by the configure script into > llvm/Config/config.h? These lines are set by the configure script (checkout DataTypes.h.in in the source tree in the same...

Hi I noticed that these defines (line 35 to 37) are hardcoded in the DataTypes.h include file: ---------------- #define HAVE_SYS_TYPES_H 1 #define HAVE_INTTYPES_H 1 #define HAVE_STDINT_H 1 ---------------- Shouldn't they have be defined by the configure script into llvm/Config/config.h? Henrik _________________________________________________________________ Undg� pop-ups med MSN Toolbar - http://toolbar.msn.dk/...

I''m at the bloody forehead stage, so I figure it''s time to ask. After installing the robot coop''s memcache-client which everyone apparently recommends, it refuses to work because the rails cache.rb is invoking the read() method on the cache, which it _does not have_. Their library has get() and put() but no read() and write() as rails expects. What gives? Is everyone quietly writing wrapper libraries around this? No mention on any blogs...help would be greatly appreciated My setup from environment.rb initialize: CACHE = MemCache.new :c_threshold => 1...

On Jan 4, 2011, at 7:45 AM, arrowdodger wrote: > Hello. I see many discrepancies in config.h file generated by CMake and autoheader. > > Most of them are following: > In autofoo-generated config: > /* Define to 1 if you have the `<name>' function. */ > #define HAVE_<name> 1 > but in CMake-generated: > #undef HAVE_<name> > This happens because in config.h.cmake (config.h.in analog) these functions just are not checked for. > We may just not use those functions anymore - do you have a list of these? > Another difference: > autofo...

...t; > @@ -545,8 +545,98 @@ do_lgetxattr (const char *path, const char > > *name, size_t *size_r)> > > return buf; /* caller frees */ > > > > } > > > > +int > > +copy_xattrs (const char *src, const char *dest) > > +{ > > +#if defined(HAVE_LISTXATTR) && defined(HAVE_GETXATTR) && > > defined(HAVE_SETXATTR) > I wonder if there are any platforms that lack one of listxattr, > getxattr and setxattr, but at the same time have one of these calls. > The xattr code (in general) is incredibly complex because of al...

...oject uses different variable names for results of these checks. For example, most subprojects check if pthread is available and store the result in: COMPILER_RT_HAS_LIBPTHREAD (compiler-rt) LIBCXX_HAS_PTHREAD_LIB (libc++) LIBCXXABI_HAS_PTHREAD_LIB (libc++abi) LIBUNWIND_HAS_PTHREAD_LIB (libunwind) HAVE_LIBPTHREAD (llvm) This means that even though this check would ideally be performed just once (per target) and reused everywhere, it's performed 5 times. The same is true for most flags and library checks. I think that this is really unnecessary and could be easily improved by unifying CMake v...

@settings.should allow_publish_ip("127.0.0.1") fails with undefined method `allow_publish_ip'' for #<#<Class:0x2f8fd48>:0x2f5a968> @settings.should_allow_publish_ip("127.0.0.1") works fine This is rspec 0.8.2. http://rspec.rubyforge.org/documentation/expectations.html says that matching arbitrary predicates is deprecated and to see

In the new version 0.90.0, rbind won't take a vector and a matrix from me, but works OK if I coerce the vector to a matrix. The following was run on a new session (i.e., no prior work), and has been duplicated on 2 machines: an SGI running Irix 6.5, and an Intel box running Red Hat Linux 6.0. Either case works fine in version 0.65.1. > t3 <- c(.5, .5) > t4 <-

...ecessary double-semicolon tests/amdgpu: add parentheses to make operation priority explicit tests/amdgpu: drop unused variables tests/util: fix signed/unsigned comparisons tests/util: drop unused parameters tests/etnaviv: drop unused `return 0` meson: add missing HAVE_RADEON configure: remove unused HAVE_CUNIT define configure: remove unused HAVE_INSTALL_TESTS define meson,configure: remove unused HAVE_OMAP define meson,configure: remove unused HAVE_TEGRA define meson,configure: remove unused HAVE_FREEDRENO define meson,configu...

...estfs-availability.pod' \ src/Makefile.am:2089: -e 's/@AVAILABILITY@//' \ src/Makefile.am:2090: -e '/@STRUCTS@/rguestfs-structs.pod' \ src/Makefile.am:2091: -e 's/@STRUCTS@//' \ maint.mk: use $(...), not @...@ make: *** [sc_makefile_at_at_check] Error 1 prohibit_HAVE_MBRTOWC 0.04 prohibit_HAVE_MBRTOWC prohibit_S_IS_definition 0.05 prohibit_S_IS_definition prohibit_always-defined_macros Can't open stat-macros.h: No such file or directory. daemon/guestfsd.c:# define O_CLOEXEC 0 src/generator.ml:#define PRId64 \"lld\" src/generator.ml:#define PRIu64 \...

...names for results of these checks. For example, most subprojects check if pthread is available and store the result in: > > COMPILER_RT_HAS_LIBPTHREAD (compiler-rt) > LIBCXX_HAS_PTHREAD_LIB (libc++) > LIBCXXABI_HAS_PTHREAD_LIB (libc++abi) > LIBUNWIND_HAS_PTHREAD_LIB (libunwind) > HAVE_LIBPTHREAD (llvm) > > This means that even though this check would ideally be performed just once (per target) and reused everywhere, it's performed 5 times. The same is true for most flags and library checks. > > I think that this is really unnecessary and could be easily improved...

...relies on your host compiler and the Clang you just built using the same ABI, which isn't guaranteed (unless you're using a multi-stage build) and I'm surprised we haven't yet seen issues due to this (or maybe we did and people just aren't aware of the problem). (Why do we need HAVE_* flags?) It's because in the runtimes build, there's no guarantee about the order in which runtimes are being built, so you cannot use e.g. if (TARGET cxxabi_shared) from within libc++ build because you don't have any guarantee whether libc++abi has already been processed. So instead,...

Hi everyone Following are a number of build-system cleanup patches. Some of them are prep-work for a possible upcoming automake/gnulib introduction. Best regards, Tiziano

...se checks. For example, most subprojects check if pthread is available and store the result in: >> >> COMPILER_RT_HAS_LIBPTHREAD (compiler-rt) >> LIBCXX_HAS_PTHREAD_LIB (libc++) >> LIBCXXABI_HAS_PTHREAD_LIB (libc++abi) >> LIBUNWIND_HAS_PTHREAD_LIB (libunwind) >> HAVE_LIBPTHREAD (llvm) >> >> This means that even though this check would ideally be performed just once (per target) and reused everywhere, it's performed 5 times. The same is true for most flags and library checks. >> >> I think that this is really unnecessary and could be...

...eant to be "portable" :) Also after I have set it up in the llvm testsuite, is there an easy way to run clang on it? Currently I have to hack autoconf generated makefiles if I want to test clang on it. 1. I've manually run, and generated a clamav-config.h. This usually just contains HAVE_* macros for headers, which should all be available on a POSIX system, so it shouldn't be a problem from this 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_LO...

...{ > int *q; > int A = B + C; > q = &A; > if (Z) > A = 10; > else > *q = 20; > return A; > } Ok, there are certain 'optimizations' that you cannot turn off in LLVM. A trivial example of this is copy-propagation. LLVM does not _even have_ a copy instruction, so the 'q = &A' instruction is just deleted, and any references to q use &A instead. This means that your *q turns into a direct assignment to A. > % llvmgcc test1.c -o test1.llvm -S > % llvm-as test1.llvm > % opt -no-aa -mem2reg test1.llvm.bc > tes...

...> Also after I have set it up in the llvm testsuite, is there an easy > way > to run clang on it? Currently I have to hack autoconf generated > makefiles if I want to test clang on it. > > 1. I've manually run, and generated a clamav-config.h. > This usually just contains HAVE_* macros for headers, which should all > be available on a POSIX system, so it shouldn't be a problem from this > perspective for llvm's build farm. > However there are some target specific macros: > #define C_LINUX 1 > #define FPU_WORDS_BIGENDIAN 0 > #define WORDS_BIGENDIA...

...a scalar NOTE: p = &A; d = *p + 10; is treated with some implicit copy propagation. quote from Chris, "Ok, there are certain 'optimizations' that you cannot turn off in LLVM. A trivial example of this is copy-propagation. LLVM does not _even have_ a copy instruction, so the 'q = &A' instruction is just deleted, and any references to q use &A instead. This means that your *q turns into a direct assignment to A." Anyone from the LLVM group should correct me if any of the above observations are incorrec...

...al/samba/var LMHOSTSFILE: /usr/local/samba/lib/lmhosts LIBDIR: /usr/local/samba/lib SHLIBEXT: so LOCKDIR: /usr/local/samba/var/locks PIDDIR: /usr/local/samba/var/locks SMB_PASSWD_FILE: /usr/local/samba/private/smbpasswd PRIVATE_DIR: /usr/local/samba/private System Headers: HAVE_SYS_ACL_H HAVE_SYS_FCNTL_H HAVE_SYS_FILIO_H HAVE_SYS_IOCTL_H HAVE_SYS_IPC_H HAVE_SYS_MMAN_H HAVE_SYS_MODE_H HAVE_SYS_MOUNT_H HAVE_SYS_PARAM_H HAVE_SYS_RESOURCE_H HAVE_SYS_SELECT_H HAVE_SYS_SHM_H HAVE_SYS_SOCKET_H HAVE_SYS_SOCKIO_H HAVE_SYS_STATFS_H HAVE_S...