similar to: [LLVMdev] gfortran link failure in current llvm svn

Hi Jack, > The curent llvm svn (r54623) is unable to link the gfortran > compiler in llvm-gcc-4.2 svn. I am getting the error... ... > Undefined symbols: > "_create_init_utf16_var", referenced from: > _darwin_build_constant_cfstring in libbackend.a(darwin.o) this is probably due to recent Apple changes. Fortran builds on linux. > Why is c++ being used

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... > > > >

Duncan, Actually, shouldn't this be just an error in the Makefile.in or Makefile.am? Why should a link line like... c++ -g -O2 -mdynamic-no-pic -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Wold-style-definition -Wmissing-format-attribute -mdynamic-no-pic -DHAVE_CONFIG_H -o f951 \

On Aug 10, 2008, at 11:40 PM, Duncan Sands wrote: > Hi Jack, > >> The curent llvm svn (r54623) is unable to link the gfortran >> compiler in llvm-gcc-4.2 svn. I am getting the error... > ... >> Undefined symbols: >> "_create_init_utf16_var", referenced from: >> _darwin_build_constant_cfstring in libbackend.a(darwin.o) > > this is

Duncan, I don't be that can be the cause because I have... --enable-languages=c,c++,fortran in my configure options for llvm-gcc-4.2. Jack On Mon, Aug 11, 2008 at 08:40:52AM +0200, Duncan Sands wrote: > Hi Jack, > > > The curent llvm svn (r54623) is unable to link the gfortran > > compiler in llvm-gcc-4.2 svn. I am getting the error... > ...

IMHO, this is one of my biggest concerns about Apple eventually switching over to llvm-gcc. The absence of the rigorous patch review process required in FSF gcc will tend to allow these sort of issues to slip by. Jack On Tue, Aug 12, 2008 at 09:05:11PM -0700, Bill Wendling wrote: > On Aug 10, 2008, at 11:40 PM, Duncan Sands wrote: > >> Hi Jack, >> >>>

I've created fink packaging for a building the llvm and llvm-gcc-4.2 svn pulls under fink on Mac OS X. Hopefully the fink info script and patch should be clear enough for some comments on my build approach. The llvm-gcc and llvm-g++ compilers seem okay so far. The llvm-gfortran compiler seems to always spew a warning.. WARNING: 128-bit integers not supported! ...even when just compiling a

Is anyone able to bootstrap llvm-gcc42 svn on x86_64-apple-darwin10? Currently it is failing here with... /sw/src/fink.build/llvm-gcc42-2.9-0/llvm_gcc42_objdir/./prev-gcc/xgcc -B/sw/src/fink.build/llvm-gcc42-2.9-0/llvm_gcc42_objdir/./prev-gcc/ -B/sw/lib/llvm-gcc-4.2/x86_64-apple-darwin10/bin/ -c -g -O2 -mdynamic-no-pic -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes

Does anyone know if the issue with building the gfortran front-end on Darwin will be addressed for llvm 2.4? The last time a checked a few weeks back, llvm-gcc-4.2 svn was still producing the linkage error... > Undefined symbols: > "_create_init_utf16_var", referenced from: > _darwin_build_constant_cfstring in libbackend.a(darwin.o) I believe the analysis of this was

Anton, With regard to the gfortran test cases which don't fail on x86_64 Linux, these are the exact gfortran.log entries for them under i686 Darwin9... > FAIL: gfortran.dg/array_constructor_12.f90 -O0 (internal compiler error) > FAIL: gfortran.dg/array_constructor_12.f90 -O0 (test for excess errors) Executing on host:

On Sat, Apr 10, 2010 at 08:29:07PM -0500, Peter O'Gorman wrote: > 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

I'm on Debian Etch and re-compile llvm/llvm-gcc-4.2 from scratch. I'm on svn revision 46813. I'm using the following commands for the compilation: ---------------------------------- # Get the sources mkdir /s/llvm cd /s/llvm svn co http://llvm.org/svn/llvm-project/llvm/trunk /s/llvm/svn.llvm svn co http://llvm.org/svn/llvm-project/llvm-gcc-4.2/trunk /s/llvm/svn.gcc42 # Compile llvm

Hi, > if /bin/sh ./libtool --mode=compile /s/llvm/obj.gcc42/./gcc/xgcc -B/s/llvm/obj.gcc42/./gcc/ -B/usr/local/i686-pc-linux-gnu/bin/ -B/usr/local/i686-pc-linux-gnu/lib/ -isystem /usr/local/i686-pc-linux-gnu/include -isystem /usr/local/i686-pc-linux-gnu/sys-include -DHAVE_CONFIG_H -I. -I/s/llvm/svn.gcc42/libgomp -I. -I/s/llvm/svn.gcc42/libgomp/config/linux/x86

On Feb 6, 2008, at 5:18 AM, Duncan Sands wrote: > Hi, > >> if /bin/sh ./libtool --mode=compile /s/llvm/obj.gcc42/./gcc/xgcc -B/ >> s/llvm/obj.gcc42/./gcc/ -B/usr/local/i686-pc-linux-gnu/bin/ -B/usr/ >> local/i686-pc-linux-gnu/lib/ -isystem /usr/local/i686-pc-linux-gnu/ >> include -isystem /usr/local/i686-pc-linux-gnu/sys-include - >> DHAVE_CONFIG_H -I.

Building the prerelease of llvm-gcc 2.4 on Intel darwin9 with the following patch... --- llvm-gcc-4.2-2.3.999-20081024.source/gcc/stub-c.c.org 2008-10-30 18:55:45.000000000 -0400 +++ llvm-gcc-4.2-2.3.999-20081024.source/gcc/stub-c.c 2008-10-30 18:57:29.000000000 -0400 @@ -157,3 +157,27 @@ { gcc_assert(0); } + + +bool cvt_utf8_utf16 (const unsigned char *, size_t, unsigned char **, +

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\"

The tutorial for installing wine said there should be a constant flow of information in the terminal window while it's installing, though for me it appears to be stuck on "---> Building apple-gcc42" for the last 20 minutes. Is this normal? Why does the installation take so long / what is it doing / how difficult is it to reverse whatever it's doing?

Here is some more info: [naromero:~/pmr] naromero% llvm-gcc -v Using built-in specs. Target: x86_64-apple-darwin10 Configured with: ../llvm-gcc-4.2-2.9.source/configure --prefix=/opt/local --host=x86_64-apple-darwin10 --enable-llvm=/opt/local --enable-languages=c,c++,objc,obj-c++,fortran --libdir=/opt/local/lib/llvm-gcc42 --includedir=/opt/local/include/llvm-gcc42 --infodir=/opt/local/share/info

The -arch option is handled by Apple's "driver-driver", and the MacPorts build is probably not using that. See the driverdriver.c source file in llvm-gcc for details. On Aug 22, 2011, at 3:08 PM, Nichols A. Romero wrote: > Here is some more info: > > [naromero:~/pmr] naromero% llvm-gcc -v > Using built-in specs. > Target: x86_64-apple-darwin10 > Configured with: