search for: gcc46

...gz' Content type 'application/x-gzip' length 537153 bytes (524 Kb) opened URL ================================================== downloaded 524 Kb * installing *source* package 'rJava' ... ** package 'rJava' successfully unpacked and MD5 sums checked checking for gcc... gcc46 -std=gnu99 checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes chec...

...it stopped during the check of R_HAS_REMOVE_FINALIZERS (full log appended): ---------------------------------- R CMD INSTALL XML_3.95-0.1.tar.gz [..snip..] Checking for 1.8: -DR_HAS_REMOVE_FINALIZERS=1 -I/usr/local/include/libxml2 -I/usr/local/include Using libxml2.* checking for gzopen in -lz... gcc46 -std=gnu99 -I/usr/local/lib/R/include -DNDEBUG -I/usr/local/include -fpic -O2 -pipe -O2 -fno-strict-aliasing -pipe -msse3 -Wl,-rpath=/usr/local/lib/gcc46 -c testRemoveFinalizers.c -o testRemoveFinalizers.o testRemoveFinalizers.c: In function 'foo': testRemoveFinalizers.c:7:2: warning:...

...e changes within R-devel's src/nmath/pnbeta.c (and probably some other relevant places) and now building R-devel on FreeBSD 10.0-CURRENT (amd64) with gcc-4.6.4 and math/R-devel (selfmade forked port from math/R) fails like this: [..snip..] mkdir /usr/ports/math/R-devel/work/R-devel/bin/exec gcc46 -std=gnu99 -I../../src/extra -I. -I../../src/include -I../../src/include -I/usr/local/include -DHAVE_CONFIG_H -fopenmp -fpic -O2 -pipe -O2 -fno-strict-aliasing -pipe -msse3 -Wl,-rpath=/usr/local/lib/gcc46 -c Rmain.c -o Rmain.o gcc46 -std=gnu99 -export-dynamic -fopenmp -L/usr/local/lib...

Hi there, I've recently encountered a piece of code that uses some SSE2 intrinsics and builds with gcc46, but not clang: clang can't find _mm_movpi64_epi64(), while gcc46 defines it in its lib/gcc46/gcc/.../4.6.3/include/emmintrin.h: extern __inline __m128i __attribute__((__gnu_inline__, __always_inline__, __artificial__)) _mm_movpi64_epi64 (__m64 __A) { return _mm_set_epi64 ((__m64)0LL...

>> These results have far fewer failures than svn-trunk, and are also >> comparable to bootstrapping with gcc-4.6.2, summarized here: >> http://paste.lisp.org/display/126363 >> (Unfortunately, I no longer have the whole build/test log for the gcc46 bootstrap.) >> This consistency between different bootstraps of the release gives me >> some hope that g++-4.0.1 is yet usable. > > David, > Another alternative for darwin8 would be to bootstrap llvm/clang 3.0 using > the clang from the fink llvm29 package (since clang 2.9...

from http://source.winehq.org/git/wine.git, download the newest git on FreeBSD 8.2 AMD64, Code: ./configure --enable-win64 --prefix=/usr/local/lib32 --mandir=/usr/local/man CC=/usr/local/bin/gcc46 FLEX=/usr/local/bin/flex then I make and completed. but make install show error: > make: don't know how to make wine.maninstall-man-pages. Stop > *** Error code 2 > path wrong in FreeBSD OS or something?

...log at revision 1.9. (also patch file needed from the same dir.) These results have far fewer failures than svn-trunk, and are also comparable to bootstrapping with gcc-4.6.2, summarized here: http://paste.lisp.org/display/126363 (Unfortunately, I no longer have the whole build/test log for the gcc46 bootstrap.) This consistency between different bootstraps of the release gives me some hope that g++-4.0.1 is yet usable. I don't know how far diverged trunk is from the 3.0-branch, but there are far fewer CodeGen test failures than with svn-trunk. Both trunk and branch exhibit numerous PC...

...o patch file needed from the same dir.) > > These results have far fewer failures than svn-trunk, and are also > comparable to bootstrapping with gcc-4.6.2, summarized here: > http://paste.lisp.org/display/126363 > (Unfortunately, I no longer have the whole build/test log for the gcc46 bootstrap.) > This consistency between different bootstraps of the release gives me > some hope that g++-4.0.1 is yet usable. David, Another alternative for darwin8 would be to bootstrap llvm/clang 3.0 using the clang from the fink llvm29 package (since clang 2.9 should build fine agains...

...all I''m trying to compile xen tools with OVMF firmware, but the compilation fails due to the hardcoded use of gcc44 for OVMF. If I download the EDK2 source I get the same error if I set gcc to 4.4 but actually have 4.7, however, a patch is available for gcc47. I have tried to install both gcc46 and get the same error. I also tried gcc44 by instead get a python error. Gcc46 and gcc47 error when running make dist-tools "/usr/bin/gcc" -c -x assembler -imacros /home/kristian/xen/xen-unstable.hg/tools/firmware/ovmf-remote/Build/OvmfX64/DEBUG_GCC44/X64/UefiCpuPkg/Library/BaseUefiCpu...

...avid Fang wrote: >>> These results have far fewer failures than svn-trunk, and are also >>> comparable to bootstrapping with gcc-4.6.2, summarized here: >>> http://paste.lisp.org/display/126363 >>> (Unfortunately, I no longer have the whole build/test log for the gcc46 bootstrap.) >>> This consistency between different bootstraps of the release gives me >>> some hope that g++-4.0.1 is yet usable. >> >> David, >> Another alternative for darwin8 would be to bootstrap llvm/clang 3.0 using >> the clang from the fink llvm29...

On Thu, Dec 15, 2011 at 1:17 PM, David Fang <fang at csl.cornell.edu> wrote: > Hi, > > I've bootstrapped llvm/clang from svn-trunk on powerpc-darwin8 (g++-4.0.1), and > have the following test results to share. > Summary below, full log at: > http://www.csl.cornell.edu/~fang/sw/llvm/r146586-powerpc-darwin8-results.txt > > The only edits required were those I

Hi, I've bootstrapped llvm/clang from svn-trunk on powerpc-darwin8 (g++-4.0.1), and have the following test results to share. Summary below, full log at: http://www.csl.cornell.edu/~fang/sw/llvm/r146586-powerpc-darwin8-results.txt The only edits required were those I posted to llvm-commits yesterday (re: "some missing clang libs"). And I also edited LitConfig.py to point to

Hi, I would really like to see the LLVM project start to make official bug fix releases (e.g. 3.3.1, 3.3.2, etc.). I think that this would be useful for a lot of the users of LLVM, especially projects that use LLVM as a library. I am willing to help maintain bug fix releases, and I'm wondering if this is something that the LLVM project would officially support with a stable SVN branch and by