similar to: [LLVMdev] cfrontend building

On Mon, 8 Aug 2005, Stephan Wienczny wrote: > Hallo, > I'm trying to write an gentoo ebuild for the c frontend. When make runs > libstdc++/configure I get some problems: > configure tries to determine the object extensionbut fails. This is the > output: > > checking host system type... i686-pc-linux-gnu > checking target system type... i686-pc-linux-gnu > checking

Am Montag, 8. August 2005 04:15 schrieb Chris Lattner: > > I have never seen this, and don't really have any ideas. What configure > options did you use? Did you follow the directions here? > > http://llvm.cs.uiuc.edu/docs/CFEBuildInstrs.html > Yes I followed those instructions - almost. This is my configure line: ../src/configure --prefix=/usr --disable-threads

Hi, When compiling the cfrontend for Linux/PPC architecture on a powermac G5, i got the following error : -------------------------------Compilation error listing if [ -f stmp-dirs ]; then true; else touch stmp-dirs; fi make GCC_FOR_TARGET="/usr/local/home/cyrille/project/llvm/cfrontend/build/gcc/xgcc -B/usr/local/home/cyrille/project/llvm/cfrontend/build/gcc/

Cyrille Mescam wrote: > Hi, > > > When compiling the cfrontend for Linux/PPC architecture on a powermac > G5, i got > the following error : I hate to ask a silly question, but are you using "make bootstrap" to build the cfrontend? Your output looks like gccas is being given a native code assembly language file to parse, and I seem to recall that that happens if

Hi Reid, > 1. Make sure your path now includes <builddir>/Debug/bin instead of > <builddir>/tools/Debug. This changed a little while back. Interesting. I don't have llvm/Debug/ after building "tools-only". Is that a symlink? Do symlinks work under cygwin? (I run xp and both of my partitions are ntfs) > If those don't clear the problem, please tell me

Hi all, subj has the first line: #! /usr/dcs/software/supported/bin/bash I think we could be more liberalistic :) best regards, --- Valery A.Khamenya

Stephan, I've seen this before. It happens when you do "make bootstrap" in llvm-gcc. While "make bootstrap" is the correct way to build GCC, its not the correct way to build llvm-gcc. Based on my experience with this, I suggest you completely erase your build tree and then follow the CFEBuildInstr.html instructions *to the letter* with zero deviations. If you

On Wed, Dec 08, 2004 at 11:23:39AM +1300, Oleg Smolsky wrote: > > 1. Make sure your path now includes <builddir>/Debug/bin instead of > > <builddir>/tools/Debug. This changed a little while back. > > Interesting. I don't have llvm/Debug/ after building "tools-only". Is > that a symlink? Do symlinks work under cygwin? (I run xp and both of my >

I am trying to compile the cfrontend for gcc3, not gcc4. I did ./configure --prefix=/opt/llvmgcc --enable-languages=c,c++ After adding the --enable-languages flag I get "xgcc: installation problem, cannot exec `gccas': No such file or directory" It is true, I don't have gccas in my PATH, nor does the file gccas appear in my cfrontend directory. Is my configuration wrong, yet

On Mon, Jun 13, 2005 at 11:02:10AM -0500, John Criswell wrote: > Cyrille Mescam wrote: > >Hi, > > > > > >When compiling the cfrontend for Linux/PPC architecture on a powermac > >G5, i got > >the following error : > > I hate to ask a silly question, but are you using "make bootstrap" to > build the cfrontend? Your output looks like gccas

Hi Guys I'm trying to port and build the GCC Front End to the Interix environment. I've succeded until the xgcc program executes: /usr/local/src/cfrontend/build/gcc/xgcc -B/usr/local/src/cfrontend/build/gcc/ -B/usr/local/src/cfrontend/install//i586-pc-interix3/bin/ -B/usr/local/src/cfrontend/install//i586-pc-interix3/lib/ -isystem

Am Montag, 8. August 2005 18:12 schrieb Reid Spencer: > Stephan, > > I've seen this before. It happens when you do "make bootstrap" in llvm-gcc. > While "make bootstrap" is the correct way to build GCC, its not the correct > way to build llvm-gcc. > > Based on my experience with this, I suggest you completely erase your build > tree and then follow

I am having some trouble getting llvm to build. I found some strange stuff going on in gcc/f/com.* In com.h I find ffeinfoKindType ffecom_gfrt_basictype ( ffecomGfrt ix); yet, in com.c I see ffeinfoBasicType ffecom_gfrt_basictype ( ffecomGfrt gfrt) I tried changing the line in com.h to ffeinfoBasicType ffecom_gfrt_basictype ( ffecomGfrt ix); and then doing make clean && make but I got a

Reid Spencer wrote: > This is an libpath problem. When xgcc runs it wants to dynamically linkthe libgcc.so. > When you run it from the command line it will find yoursystem libgcc.so (which works) Not really. For systems that have gcc 4.2 natively installed, like the current Debian testing, the compiler gets GCC_4.2.0 version errors. It isn't easy to work around b/c xgcc wants to link

On Fri, 16 Jun 2006, James Supancic wrote: > I am having some trouble getting llvm to build. > I found some strange stuff going on in gcc/f/com.* This sounds like you enabled the fortran frontend, which isn't supported. Please read the README.LLVM file in the root directory of the llvmgcc4 source distro. -Chris > In com.h I find > ffeinfoKindType ffecom_gfrt_basictype (

Hi Scooter, On Mon, 2006-11-06 at 12:07 -0800, Scott Michel wrote: > Reid Spencer wrote: > > This is an libpath problem. When xgcc runs it wants to dynamically linkthe libgcc.so. > > When you run it from the command line it will find yoursystem > libgcc.so (which works) > > Not really. For systems that have gcc 4.2 natively installed, like the > current Debian

"John Criswell" <criswell at cs.uiuc.edu> wrote in message news:4162A940.8090307 at cs.uiuc.edu... > Alex Vinokur wrote: > > Hi, > > > > I would like to use LLVM-GCC to compare its performance with other compilers. > > Something like testsuite "Computing very large Fibonacci numbers" at > >

> Okay, I took a closer look at your output. > > I was correct in that gccas is attempting to assemble a native PPC > assembly language file. However, this appears to be happening because > the assembly file is generated by the GCC Makefiles for libgcc2 (in > llvm-gcc/gcc/config/rs6000/t-ppccomm, I think). > > The first thing I would try is Marco's suggestion: add

Cyrille Mescam wrote: > On Mon, Jun 13, 2005 at 11:02:10AM -0500, John Criswell wrote: > >>Cyrille Mescam wrote: >> [snip] > > In fact, i am using the CFE build procedures. I am on instructions 5. > > cyrille > Okay, I took a closer look at your output. I was correct in that gccas is attempting to assemble a native PPC assembly language file. However,

> #! /usr/dcs/software/supported/bin/bash > I think we could be more liberalistic :) Hi, This anomaly is noted in the documentation for building the C front-end (http://llvm.cs.uiuc.edu/docs/CFEBuildInstrs.html); in step 4 it advises you to edit src/configure and "change the first line (starting w/ #!) to contain the correct full pathname of sh." We do provide binaries of the C