[LLVMdev] Compiling llvm-gcc on amd64 with 32 bits: assembler still carps

[Joachim Durchholz]

Am Montag, den 31.03.2008, 00:02 -0700 schrieb Tanya Lattner:
> On Mar 30, 2008, at 11:22 PM, Joachim Durchholz wrote:
> 
> > Am Sonntag, den 30.03.2008, 15:45 -0700 schrieb Tanya Lattner:
> >> On Mar 30, 2008, at 12:39 PM, Joachim Durchholz wrote:
> >>
> >>> OK, I now have
> >>>
> >>> LLVM_VERSION_INFO=kurier-bootstrap /home/jo/llvm-gcc-src/configure
> >>> --prefix=/home/jo --enable-optimized --build=i686-pc-linux-gnu
> >>> --host=i686-pc-linux-gnu --target=i686-pc-linux-gnu
> >>> --enable-llvm=/home/jo --enable-languages=c,c++
> >>
> >> Where have you built llvm? The enable-llvm dir should point to where
> >> you built llvm.
> >
> > The --prefix for LLVM and LLVM-GCC is the same, /home/jo.
> > IOW the LLVM binaries are in /home/jo/bin.
> > I'll try with --enable-llvm=/home/jo/bin today.

> No, not where the binaries are, but I think it should point to where  
> the libraries are. I don't usually do an install, so maybe someone  
> else can comment on this.

Saying --enable-llvm=/home/jo/lib or --enable-llvm=/home/jo/bin gives me

...  
checking for valgrind.h... (cached) no
checking for dsymutil... no
dsymutil is not available
checking for dsymutil... no
dsymutil is not available
configure: error: You must specify valid path to your LLVM tree with
--enable-llvm=DIR

quite early in 'make'.

--enable-llvm=/home/jo does a lot more work before it finally hits the
assembler problems.

So I conclude that --enable-llvm should point to wherever --prefix
pointed when LLVM was built, and the assembler problem have some other
source.

Regards,
Jo