llvm dev - Aug 2008 - [LLVMdev] gfortran link failure in current llvm svn

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...
> ...
> > 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 instead of
/sw/src/fink.build/llvm-gcc42-2.3.999-20080810/llvm_gcc42_objdir/./prev-gcc/xgcc?
> 
> I think this is because some people may not have C++ in the list
> of languages to build.  There's even a PR about this:
> http://llvm.org/bugs/show_bug.cgi?id=1150
> 
> Ciao,
> 
> 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.
I meant that it uses the system c++ not because you didn't
configure with c++ in --enable-languages, but because someone
might not configure with c++.  I suppose the build system
could be modified to use the just built g++ if it exists,
and the system c++ compiler otherwise, but currently it
doesn't do that.

Ciao,

Duncan.

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...
> > 
> > --enable-languages=c,c++,fortran
> > 
> > in my configure options for llvm-gcc-4.2.
> 
> I meant that it uses the system c++ not because you didn't
> configure with c++ in --enable-languages, but because someone
> might not configure with c++.  I suppose the build system
> could be modified to use the just built g++ if it exists,
> and the system c++ compiler otherwise, but currently it
> doesn't do that.
> 
> Ciao,
> 
> Duncan.