[LLVMdev] Fw: run into a problem with a version of GCC not listed here

[Török Edwin]

I assume you meant to send this to the list as well.

Begin forwarded message:

Date: Fri, 22 Oct 2010 20:36:06 +0200 (CEST)
From: "017667932270" <jurij at o2online.de>
To: <edwintorok at gmail.com>
Subject: AW: Re: [LLVMdev] run into a problem with a version of GCC not
listed here


hi edwin,
tanks again for  clearing up.

i found now a solution for my problem.
i like to report the problem and the solution!
maybe someone else had the same problem.

the problem:
the build of LLVM compiler suite, do not work properly
with RHEL linux 4.8 with  GCC 3.4.6. 
using a  RHEL linux 5.5 and gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-48)
the LLVM compiler suite works very well. 
but my  RHEL linux 4.8 machine
could not execute the build tools due to missing glibc 2.5.
- i have to work on RHEL 4.8 machine due to some tool dependency in my
work flow.

the solution to build a working LLVM suite compatible with RHEL 4.8 and
RHEL 5.5 is as follows:
first you need to build a new version of GCC 4.5.1 on the RHEL 4.8
machine. use the GCC 4.5.1 to compile the LLVM suite!
this  compiled version works well with all RHEL 4.x and RHEL 5.x linux
system. (32bit and 64bit) for the compilation of the LLVM you have set
the LD_LIBRARY_PATH and the LD_RUN_PATH to the new installed GCC
compiler directory!

-  compile the GCC 4.5.1 is not a simple task.
   i automate this task by a simple bash script:
- this script downloads all needed sources and generates a necessary
  settigs file in the <INSTALL>/i686-pc-linux-gnu_gcc-4.5.1/settings.sh 
directory.

the script is attached. "maybe it could use someone"

best regards:
jurij 



  



-----Ursprüngliche Nachricht-----
Datum: Tue, 19 Oct 2010 10:08h
Von: Török Edwin <edwintorok at gmail.com>
An: "017667932270" <yuri.kostasenko at o2online.de>
Betreff: Re: [LLVMdev] run into a problem with a version of GCC not
listed here


On Mon, 18 Oct 2010 23:11:22 +0200 (CEST)
"017667932270" <yuri.kostasenko at o2online.de> wrote:

> hi edwin,
> thank 4 fast response,
> i assume, than clang is target independent.

No, C language is target dependent.
You can have a single clang compiler that can generate code for
multiple architectures (if you tell it with -triple what to generate).

> is that corret?
> or 
> must clang also be adjusted to the target?
> 
> the backend for a new targed XPIC works on windows XP very well, but
> with my linux i have an abort:
> 0  llc 0x0883b520
> Stack dump:
> 0.      Program arguments: /appl/c_compiler/xpic/llvm-2.7/bin/llc -O2
> -f -march=xpic new_main.bc -o new_main.s 1.      Running pass 'xpic
> DAG->DAG Pattern Instruction Selection' on function '@fib_recursive'

As someone else said on the list, what is this XPIC target, because it
is not part of LLVM. You should contact whoever wrote it to figure out
what is wrong with it.

Best regards,
--Edwin


Unterwegs über Ihre E-Mails informiert mit der kostenlosen
SMS-Benachrichtigung von o2! Mehr Infos unter
http://www.o2online.de/goto/benachrichtigung 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: build-gcc-toolchain45.sh
Type: application/octet-stream
Size: 18246 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20101022/c4ec6d28/attachment.obj>