search for: llvm_objdir

...s-array.o fortran/trans-common.o fortran/trans-const.o fortran/trans-decl.o fortran/trans-expr.o fortran/trans-intrinsic.o fortran/trans-io.o fortran/trans-openmp.o fortran/trans-stmt.o fortran/trans-types.o llvm-main.o libbackend.a ../libcpp/libcpp.a /sw/src/fink.build/llvm-gcc42-2.3.999-20080810/llvm_objdir/Release/lib/libLLVMBitReader.a /sw/src/fink.build/llvm-gcc42-2.3.999-20080810/llvm_objdir/Release/lib/libLLVMipo.a /sw/src/fink.build/llvm-gcc42-2.3.999-20080810/llvm_objdir/Release/lib/libLLVMBitWriter.a /sw/src/fink.build/llvm-gcc42-2.3.999-20080810/llvm_objdir/Release/lib/LLVMX86.o /sw/src/fink....

Hi, > I am confused. Shouldn't the gcc 4.2 front-end build behave > just like the FSF gcc build. The first stage builds the compilers > and the second stage rebuilds them using those from the first > stage? the FSF gcc requires you to build the C compiler (I think - will check). Thus a newly built C compiler is always available to build later stages. We can't reasonably

Duncan, I am confused. Shouldn't the gcc 4.2 front-end build behave just like the FSF gcc build. The first stage builds the compilers and the second stage rebuilds them using those from the first stage? Jack On Mon, Aug 11, 2008 at 03:56:23PM +0200, Duncan Sands wrote: > > I don't be that can be the cause because I have... > > > >

...s-array.o fortran/trans-common.o fortran/trans-const.o fortran/trans-decl.o fortran/trans-expr.o fortran/trans-intrinsic.o fortran/trans-io.o fortran/trans-openmp.o fortran/trans-stmt.o fortran/trans-types.o llvm-main.o libbackend.a ../libcpp/libcpp.a /sw/src/fink.build/llvm-gcc42-2.3.999-20080810/llvm_objdir/Release/lib/libLLVMBitReader.a /sw/src/fink.build/llvm-gcc42-2.3.999-20080810/llvm_objdir/Release/lib/libLLVMipo.a /sw/src/fink.build/llvm-gcc42-2.3.999-20080810/llvm_objdir/Release/lib/libLLVMBitWriter.a /sw/src/fink.build/llvm-gcc42-2.3.999-20080810/llvm_objdir/Release/lib/LLVMX86.o /sw/src/fink....

...-infodir=%p/share/info --with-gmp=%p --with-libiconv-prefix=/usr --with-system-zlib << PatchScript: << #!/bin/sh -ev cd ../llvm-gcc-4.2-%r patch -p1 < %a/%n.patch << CompileScript: << #!/bin/bash -ev ulimit -s `ulimit -s` darwinvers=`uname -r|cut -f1 -d.` mkdir ../llvm_objdir cd ../llvm_objdir if [ `uname -p` = "powerpc" ]; then TRIPLE=powerpc-apple-darwin$darwinvers else TRIPLE=i686-apple-darwin$darwinvers fi ../llvm-2.2-%r/configure %c --build=$TRIPLE --target=$TRIPLE --host=$TRIPLE --enable-optimized --enable-assertions make tools-only mkdir .....

...--with-system-zlib --with-as=`xcode-select -print-path`/usr/bin/as --with-ld=`xcode-select -print-path`/usr/bin/ld --with-nm=`xcode-select -print-path`/usr/bin/nm << CompileScript: << #!/bin/bash -ev export LD=`xcode-select -print-path`/usr/bin/ld ulimit -s `ulimit -s` mkdir ../llvm_objdir cd ../llvm_objdir # ../llvm-%v/configure %c --enable-optimized --enable-assertions --enable-pic --enable-targets=host-only ../llvm-2.8/configure %c --enable-optimized --enable-assertions --enable-pic --enable-targets=host-only num_cpu=$(echo `sysctl -n hw.ncpu`) make -j $num_cpu << Install...

Current llvm release 2.8 branch at r115409 is broken on x86_64-apple-darwin10. #!/bin/bash -ev export LD=`xcode-select -print-path`/usr/bin/ld xcode-select -print-path ulimit -s `ulimit -s` ulimit -s mv ../clang-2.8 ./tools/clang mkdir ../llvm_objdir cd ../llvm_objdir ../llvm-2.8/configure --prefix=/sw --prefix=/sw --mandir=/sw/share/man --infodir=/sw/share/info --with-gmp=/sw --with-libiconv-prefix=/usr --with-system-zlib --with-as=`xcode-select -print-path`/usr/bin/as --with-ld=`xcode-select -print-path`/usr/bin/ld --with-nm=`xcode-selec...

...rth wrote: > Current llvm release 2.8 branch at r115409 is broken on x86_64-apple-darwin10. > > #!/bin/bash -ev > export LD=`xcode-select -print-path`/usr/bin/ld > xcode-select -print-path > ulimit -s `ulimit -s` > ulimit -s > mv ../clang-2.8 ./tools/clang > mkdir ../llvm_objdir > cd ../llvm_objdir > ../llvm-2.8/configure --prefix=/sw --prefix=/sw --mandir=/sw/share/man --infodir=/sw/share/info --with-gmp=/sw --with-libiconv-prefix=/usr --with-system-zlib --with-as=`xcode-select -print-path`/usr/bin/as --with-ld=`xcode-select -print-path`/usr/bin/ld --with-nm=`xco...

On 04/10/2010 08:01 PM, Jack Howarth wrote: > > bash-3.2$ GCC=/sw/bin/gcc-4 CC=gcc-4 CXX=g++-4 CFLAGS=-I/sw/include CXXFLAGS=-I/sw/include LLVM_CONFIG=/sw/lib/llvm/bin/llvm-config make > g++-4 -c -I/sw/lib/llvm/include -D_DEBUG -D_GNU_SOURCE -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -MD -MP -DIN_GCC -DREVISION=\"100954M\"

Is there a particular method one should used to build the libLTO.dylib from the llvm svn on darwin9? Unless I am confused, it seems that libLTO.dylib gets built when I do a configure and make directly in the llvm svn tree but not when I created separate llvm_objdir directory and execute configure and make within it. Thanks in advance for any clarifications. Jack

On Sat, Apr 10, 2010 at 01:52:18PM +0200, Duncan Sands wrote: > Hi Jack, > > > Is anyone building dragon-egg on darwin? > > Anton built it once. There were some problems with dynamic libraries: gcc's > plugin support requires the use of dynamic libraries, and the configure logic > it uses thinks that darwin does not support dynamic libraries! So it is >

...o] Error 1 If I manually run /sw/lib/llvm/bin/llvm-config, I get... bash-3.2$ /sw/lib/llvm/bin/llvm-config --prefix /sw/lib/llvm bash-3.2$ /sw/lib/llvm/bin/llvm-config --src-root /sw/src/fink.build/llvm-2.7-1/llvm-2.7 bash-3.2$ /sw/lib/llvm/bin/llvm-config --obj-root /sw/src/fink.build/llvm-2.7-1/llvm_objdir bash-3.2$ /sw/lib/llvm/bin/llvm-config --bindir /sw/lib/llvm/bin bash-3.2$ /sw/lib/llvm/bin/llvm-config --includedir /sw/lib/llvm/include bash-3.2$ /sw/lib/llvm/bin/llvm-config --libdir /sw/lib/llvm/lib bash-3.2$ /sw/lib/llvm/bin/llvm-config --cppflags -I/sw/lib/llvm/include -D_DEBUG -D_GNU_SOURC...

.../bin/as --with-ld=/Developer/usr/bin/ld --with-nm=/Developer/usr/bin/nm --build=i686-apple-darwin9 --target=i686-apple-darwin9 --host=i686-apple-darwin9 --with-arch=nocona --with-tune=generic --with-gxx-include-dir=/usr/include/c++/4.0.0 --enable-llvm=/sw/src/fink.build/llvm-gcc42-2.5-1/llvm-2.5/../llvm_objdir --enable-languages=c,c++,fortran Thread model: posix gcc version 4.2.1 (Based on Apple Inc. build 5636) (LLVM build) /sw/lib/llvm-gcc-4.2/libexec/gcc/i686-apple-darwin9/4.2.1/collect2 -dynamic -dylib -arch i386 -flat_namespace -macosx_version_min 10.5.6 -single_module -undefined suppress -weak_ref...

...e/info --with-gmp=/sw --with-libiconv-prefix=/usr --with-system-zlib --build=i686-apple-darwin9 --target=i686-apple-darwin9 --host=i686-apple-darwin9 --with-arch=nocona --with-tune=generic --with-gxx-include-dir=/usr/include/c++/4.0.0 --enable-llvm=/sw/src/fink.build/llvm-gcc42-2.3-1000/llvm-2.3/../llvm_objdir --enable-languages=c,c++,fortran,;t t Would it be useful to file bugzilla reports on llvm/llvm-gcc4.2 for these failures? Jack

.../bin/as --with-ld=/Developer/usr/bin/ld --with-nm=/Developer/usr/bin/nm --build=i686-apple-darwin9 --target=i686-apple-darwin9 --host=i686-apple-darwin9 --with-arch=nocona --with-tune=generic --with-gxx-include-dir=/usr/include/c++/4.0.0 --enable-llvm=/sw/src/fink.build/llvm-gcc42-2.4-1/llvm-2.4/../llvm_objdir --enable-languages=c,c++,fortran These results look very close to what we got in llvm 2.3 on Intel Darwin. Jack

.../bin/as --with-ld=/Developer/usr/bin/ld --with-nm=/Developer/usr/bin/nm --build=i686-apple-darwin9 --target=i686-apple-darwin9 --host=i686-apple-darwin9 --with-arch=nocona --with-tune=generic --with-gxx-include-dir=/usr/include/c++/4.0.0 --enable-llvm=/sw/src/fink.build/llvm-gcc42-2.5-1/llvm-2.5/../llvm_objdir --enable-languages=c,c++,fortran