search for: cfeinstal

...g the CFE to build an executable named llvm-gcc instead of gcc. The hyphenated name was chosen to be consistent with other LLVM tools, it is also needed on some platforms so that llvm-nm can be found in the path when the CFE is configuring the libstdc++ (don't ask why!). Quick Fix: 1. Put the $CFEINSTALL/bin directory into your PATH variable 2. Remove $CFEINSTALL/bin/* 3. Remove shell aliases for "llvmgcc" and "llvmgxx" or change them to invoke llvm-gcc and llvm-gxx. 4. Rebuild llvm with "make tools-only" 5. Rebuild the CFE with --program-prefix=llvm- 6. Rebuild...

Hi all, After successfully building llvm tools-only and cfontend, I went back to llvm directory and ran configure --with-llvmgccdir=$CFEINSTALL Unfortunately, at the end of the process I got the following configure: WARNING: ***** llvm C/C++ front end was not found, or does not configure: WARNING: ***** appear to be working. And I do have CFEINSTALL environment variable.... BTW, I have noticed that executables cfrontend produces are cal...

...: unable to detect exception model To work aroud the problem I edited gcc/objc/config-lang.in and removed the comment from the line #target_libs=target-libobjc With this change it is again possible to build without objc. The complete configure line was ../llvm-gcc4-1.7.source/configure --prefix=$CFEINSTALL --enable-languages=c,c++ --program-prefix=llvm- --enable-llvm=/home/rafael/dev/obj/ --enable-checking Best Regards, Rafael

...idea how >it ever worked. In any case, this patch should help things: > >http://mail.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20040809/017143.html > > > Thanks, now I can compile llvm-gcc without problems. However, when I go back to rebuild llvm, reconfigure, setting the CFEINSTALL dir, then make it can build the tools ok but not the runtime: make[1]: Entering directory `/usr/pd/llvm/llvm/runtime' make[2]: Entering directory `/usr/pd/llvm/llvm/runtime/GCCLibraries' make[3]: Entering directory `/usr/pd/llvm/llvm/runtime/GCCLibraries/crtend' Compiling crtend.c to...

On Mon, Aug 16, 2004 at 01:07:39PM +0200, Robert Feldt wrote: > However, when I go back to rebuild llvm, reconfigure, setting the > CFEINSTALL dir, then make it can build the tools ok but not the > runtime: [snip] > Compiling crtend.c to bytecode > Files/ATI: not found [snip] > I don't understand the error message since I see no reference to > Files/ATI. Any clues? Can you please give us the output log with you run...

...LLVM tools *must* have an LLVM symbol table in them. This happens automatically for the crtend.a library, but not for the runtime libraries produced by the C/C++ Front End. In order to get your programs to link again, you *must* do the following *after* rebuilding with the latest CVS sources: cd $CFEINSTALL cd lib llvm-ranlib libiberty.a llvm-ranlib libstdc++.a llvm-ranlib libsupc++.a llvm-ranlib gcc/*/*/libgcc.a llvm-ranlib gcc/*/*/libgcov.a This will ensure that the archives built by CFE will have LLVM style bytecode symbol tables in them. Reid. -------------- next part -------------- A non-text...

...23:45:35 -0800 Reid Spencer <reid at x10sys.com> wrote: > The entire makefile system was rewritten a couple of weeks ago. This is > a good thing, your compiles now go twice as fast. Resistance is futile, > just adapt :) > > The install target installed the bytecode libs into CFEINSTALL as before > and also installs the native libraries to your prefix/lib directory. > This is intentional. > > Reid > > On Wed, 2004-11-10 at 23:32, Jeff Cohen wrote: > > But there already was an "install", and it did far more than install the > > bytecode fi...

...t; To work aroud the problem I edited gcc/objc/config-lang.in and removed > the comment from the line > #target_libs=target-libobjc > > With this change it is again possible to build without objc. The > complete configure line was > > ../llvm-gcc4-1.7.source/configure --prefix=$CFEINSTALL > --enable-languages=c,c++ --program-prefix=llvm- > --enable-llvm=/home/rafael/dev/obj/ --enable-checking This is the right fix, thanks! I've applied it to the main llvmgcc tree. -Chris -- http://nondot.org/sabre/ http://llvm.org/

...ed gcc/objc/config-lang.in and removed > > the comment from the line > > #target_libs=target-libobjc > > > > With this change it is again possible to build without objc. The > > complete configure line was > > > > ../llvm-gcc4-1.7.source/configure --prefix=$CFEINSTALL > > --enable-languages=c,c++ --program-prefix=llvm- > > --enable-llvm=/home/rafael/dev/obj/ --enable-checking > > This is the right fix, thanks! I've applied it to the main llvmgcc tree. > > -Chris >

The entire makefile system was rewritten a couple of weeks ago. This is a good thing, your compiles now go twice as fast. Resistance is futile, just adapt :) The install target installed the bytecode libs into CFEINSTALL as before and also installs the native libraries to your prefix/lib directory. This is intentional. Reid On Wed, 2004-11-10 at 23:32, Jeff Cohen wrote: > But there already was an "install", and it did far more than install the > bytecode files. That changed too? > > >...

...M symbol table in them. This happens > automatically for the crtend.a library, but not for the runtime > libraries produced by the C/C++ Front End. In order to get your programs > to link again, you *must* do the following *after* rebuilding with the > latest CVS sources: > > cd $CFEINSTALL > cd lib > llvm-ranlib libiberty.a > llvm-ranlib libstdc++.a > llvm-ranlib libsupc++.a > llvm-ranlib gcc/*/*/libgcc.a > llvm-ranlib gcc/*/*/libgcov.a > > This will ensure that the archives built by CFE will have LLVM style > bytecode symbol tables in them. > > Re...

But there already was an "install", and it did far more than install the bytecode files. That changed too? On Wed, 10 Nov 2004 23:28:27 -0800 Reid Spencer <reid at x10sys.com> wrote: > Yeah, its just "install" now. > > I'll fix the documentation. > > Reid. > > On Wed, 2004-11-10 at 23:19, Jeff Cohen wrote: > > My rebuild from scratch

...lt;reid at x10sys.com> wrote: > > > The entire makefile system was rewritten a couple of weeks ago. This is > > a good thing, your compiles now go twice as fast. Resistance is futile, > > just adapt :) > > > > The install target installed the bytecode libs into CFEINSTALL as before > > and also installs the native libraries to your prefix/lib directory. > > This is intentional. > > > > Reid > > > > On Wed, 2004-11-10 at 23:32, Jeff Cohen wrote: > > > But there already was an "install", and it did far more tha...

...e: > > > > > The entire makefile system was rewritten a couple of weeks ago. This is > > > a good thing, your compiles now go twice as fast. Resistance is futile, > > > just adapt :) > > > > > > The install target installed the bytecode libs into CFEINSTALL as before > > > and also installs the native libraries to your prefix/lib directory. > > > This is intentional. > > > > > > Reid > > > > > > On Wed, 2004-11-10 at 23:32, Jeff Cohen wrote: > > > > But there already was an "ins...

...up on your questions. Here are my instructions to compile the cfe: 5. Configure, build, and install the C front-end: a. Before configure: export CPPFLAGS="-D__MINGW32__ " ?export LDFLAGS=-Wl,-no-keep-memory" export CFEINSTALL=/C/LLVM/cfe cd objdir make distclean If objdir != srcdir: Change all absolute paths given to source directory relative by using --srcdir option for configure: configure --prefix=$CFEINSTALL --disable-threads --disable-nls --disable-shared --enable-languages=c,c++ --program-prefix=llvm- --srcd...

>>Does anyone know a source for a pre-built version of the same? > >To my knowledge there is no pre-built version of the cfe. See following link for CFE :- http://illuvium.com/download/ It maybe a bit out of date. I believe the CFE maybe broken at the moment, at least the Cygwin nightly test reports that it is broken and I believe this is the same thing ?

...gt; > The entire makefile system was rewritten a couple of weeks ago. This is > > > > a good thing, your compiles now go twice as fast. Resistance is futile, > > > > just adapt :) > > > > > > > > The install target installed the bytecode libs into CFEINSTALL as before > > > > and also installs the native libraries to your prefix/lib directory. > > > > This is intentional. > > > > > > > > Reid > > > > > > > > On Wed, 2004-11-10 at 23:32, Jeff Cohen wrote: > > > > >...

...i, I am still new to LLVM and also GNU softwares. I am doing a project using LLVM. I was building cfrontend on my windows cygwin, however I encountered this problem, may I now what is the cause? ******************************** my configuration output is: bash-2.05b$ ../src/configure --prefix=$CFEINSTALL --disable-threads --disable-n ls --disable-shared --enable-languages=c,c++ loading cache ./config.cache checking host system type... i686-pc-cygwin checking target system type... i686-pc-cygwin checking build system type... i686-pc-cygwin checking for a BSD compatible install... (cached) /usr/bi...

...res. > > I am doing a project using LLVM. > > I was building cfrontend on my windows cygwin, however I encountered > this problem, may I now what is the cause? > > ******************************** > my configuration output is: > bash-2.05b$ ../src/configure --prefix=$CFEINSTALL --disable-threads --disable-n > ls --disable-shared --enable-languages=c,c++ > > loading cache ./config.cache > checking host system type... i686-pc-cygwin > checking target system type... i686-pc-cygwin > checking build system type... i686-pc-cygwin > checking for a BSD com...

On Sun, 15 Aug 2004, Robert Feldt wrote: > However, I wonder if someone supplies pre-built cfrontend binaries for > cygwin? Nope, we don't have one yet, sorry. > I followed the instructions and tried to build them myself but get > when building the cfrontend. Any ideas? That is really wierd. Looking at that line of gcc.c, I have no idea how it ever worked. In any case, this