llvm dev - Aug 2006 - [LLVMdev] llvm-gcc4 on Debian

I know that Al Stone has compiled llvm-gcc4 successfully and I can
report the same. The problem I consistently run into is that llvm-gcc
ends up producing native format output; it does not produce bytecode,
nor does it invoke gccas or gccld.

I'm using the latest svn, and my configure args are:

--prefix=/work/scottm/llvm-cfrontend/obj/../i686-pc-linux-gnu \
--enable-llvm=/work/scottm/llvm/obj/i686-pc-linux-gnu/ \
--program-prefix=llvm- \
--disable-threads --disable-nls --disable-shared

configure doesn't complain and the llvm object directory exists and is
sane according to configure. Any clue?

I don't think llvm-gcc4 uses gccas or gccld, but it can emit bytecode
if you give it the --emit-llvm option:
llvm-gcc --emit-llvm -c -o foo.bc foo.c

On 8/14/06, Scott Michel <scottm at rushg.aero.org>
wrote:
> I know that Al Stone has compiled llvm-gcc4 successfully and I can
> report the same. The problem I consistently run into is that llvm-gcc
> ends up producing native format output; it does not produce bytecode,
> nor does it invoke gccas or gccld.
>
> I'm using the latest svn, and my configure args are:
>
> --prefix=/work/scottm/llvm-cfrontend/obj/../i686-pc-linux-gnu \
> --enable-llvm=/work/scottm/llvm/obj/i686-pc-linux-gnu/ \
> --program-prefix=llvm- \
> --disable-threads --disable-nls --disable-shared
>
> configure doesn't complain and the llvm object directory exists and is
> sane according to configure. Any clue?
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>

Ryan Brown wrote:
> I don't think llvm-gcc4 uses gccas or gccld, but it can emit bytecode
> if you give it the --emit-llvm option:
> llvm-gcc --emit-llvm -c -o foo.bc foo.c
That's a bit asymmetric with the previous gcc3 version, isn't it? That
would mean that the "An Example Using the LLVM Tool Chain" section
needs
to be updated for the gcc4 frontend.

OTOH, I could attempt to hack on the gcc4 frontend to use gccas and
gccld (not so hard). I have a patch that I'm testing that fixes llvmc,
which is out of sync with the "c" configuration file.