llvm dev - Nov 2006 - [LLVMdev] gcc 4 frontend binary for mac os x x86

On Nov 14, 2006, at 8:30 AM, Tanya M. Lattner wrote:
>
>>> I assume you have an Mac with an Intel processor.
>>
>> Yes. Sorry, I forgot to mentioned it in the mailbody.
>>
>>> Download this:
>>> http://llvm.org/releases/1.8/llvm-gcc4-1.8-x86-darwin.tar.gz
>>
>> I think that is the same tarball I used before.
>
> Ok. I'm confused.
Perhaps its my flavor of english :-/
> Do you want llvm-gcc3 or llvm-gcc4?
I want llvm-gcc4! Before I sent my first mail to this list, I used  
the gcc3-binary on a ppc mac (that works) and the gcc4-binary on my  
intel-mac - that creates x86-binaries but no llvm-bytecode.
> The tarball above is
> a binary for llvm-gcc4 for Mac x86.
This is one of the rare facts I understand ;-)
> You don't need to compile anything or
> fix any headers.
Ok. But then it doesn't work. Or I forgot to set pathes or make to  
less links ... I don't know.
>>> Let me know if that doesn't work.
>>
>> Again: there is no fixheader-script like you describe here http://
>> llvm.org/docs/GettingStarted.html#quickstart. (in the gcc3 frontends
>> there are fixheader-scripts, but there is no gcc3-frontend for darwin
>> intel/x86)
>
> There is no fixheader script for llvm-gcc4. That is for llvm-gcc3.
Ok.
> Lastly, I think maybe I missed the real question here.
Perhaps this is a real question:
The messages I posted last time
-----------------
ignoring nonexistent directory "/Users/moser/llvm/llvm-gcc4-1.8-x86- 
darwin/bin/../lib/gcc/i686-apple-darwin8.7.1/4.0.1/../../../../i686- 
apple-darwin8.7.1/include"
ignoring nonexistent directory "/build-llvm/llvm-gcc4-1.8-x86-darwin/ 
install/include"
ignoring nonexistent directory "/build-llvm/llvm-gcc4-1.8-x86-darwin/ 
install/lib/gcc/i686-apple-darwin8.7.1/4.0.1/include"
ignoring nonexistent directory "/build-llvm/llvm-gcc4-1.8-x86-darwin/ 
install/i686-apple-darwin8.7.1/include"
-----------------
have no meaning?

> If you want to emit
> llvm bytecode be sure to pass -emit-llvm to llvm-gcc.
Thats the next point:
$ llvm-gcc4-1.8-x86-darwin/bin/gcc -v -emit-llvm main.c
....
/usr/bin/ld: unknown flag: -emit-llvm
collect2: ld returned 1 exit status

I'm afraid  I made a very simple but serious mistake.

Thanks again
Nico

On Nov 14, 2006, at 1:07 AM, Nico Moser wrote:
>> If you want to emit
>> llvm bytecode be sure to pass -emit-llvm to llvm-gcc.
>
> Thats the next point:
> $ llvm-gcc4-1.8-x86-darwin/bin/gcc -v -emit-llvm main.c
> ....
> /usr/bin/ld: unknown flag: -emit-llvm
> collect2: ld returned 1 exit status
The linker does not know how to link llvm-byte code.
If you add  -c on the command line

$ llvm-gcc4-1.8-x86-darwin/bin/gcc -v -emit-llvm main.c

then you will get llvm-byte code in main.o file. You can
select the name of byte code file using standard gcc -o switch.

-
Devang

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20061114/a3e45d8e/attachment.html>

On Nov 14, 2006, at 10:21 AM, Devang Patel wrote:
> The linker does not know how to link llvm-byte code.
> If you add  -c on the command line
>
> $ llvm-gcc4-1.8-x86-darwin/bin/gcc -v -emit-llvm main.c
>
> then you will get llvm-byte code in main.o file. You can
> select the name of byte code file using standard gcc -o switch.

Shame on me - sorry for wasting the list :-[
I think I was confused by the little differences between gcc3 and  
gcc4 - sorry again.

Thanks
Nico
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20061114/bf63ba3b/attachment.html>