similar to: [LLVMdev] cannot find gccas

>> Patch attached. >> >> This patch with header installation patch ( >> http://mail.cs.uiuc.edu/pipermail/llvmdev/2005-February/003300.html ) >> let external project (I am test it at my YAFL frontend for LLVM) build >> using installed LLVM version instead using LLVM obj/src dirs. > > I think the patch looks basically sane. The one wierd thing I notice

Vladimir, I took a *very quick* look at your patch. I won't be able to look at it in more detail until this weekend, but perhaps you can address a couple of concerns: 1. I don't understand the need for LLVMToolDirSlash. This seems like a gratuitous change to me. 2. I don't think the change to CPP.Flags is right. It won't find the LLVM header files 3. Removing the

1) Build clang with GCC-4.9.2, when compling other application s with clang/clang++, the default linker is ld, can I replace it with other linker tool， if we can, how to do it? I.E. can we use collect2 instead? 2) how to specify the path, if we do not use the default vertion GCC? Best Regards! Eric Lew -------------- next part -------------- An HTML attachment was scrubbed... URL:

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

Reid, I think it is the first time it is run that the errors occcur !? Not sure but that would seem logical. Aaron

Is there a way I can use arclx.exe to load syslinux? Or has anyone had any experiance using an SGI Workstation 540? And what kind of options to put in Load Identifier = Linux Install OSLoader = \sgiboot\arclx.exe OSLoad Filename = /sgiboot\vmlinux OSLoad Partition = CDROM System Partition = CDROM OSLoad Options = load_ramdisk=1 ramdisk_size=6000 root=/dev/fd0 rw which is in the bios Those

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

On Saturday 15 September 2007, Tanya Lattner wrote: > 2) Download llvm-2.1, llvm-test-2.1, and the llvm-gcc4.0 source. > Compile everything. Run "make check" and the full llvm-test suite > (make TEST=nightly report). I tried to do this, but ran into trouble. LLVM itself compiled fine. GCC compilation is broken when Java support is enabled. I can file a detailed bug report

More bison woes. llvm-2.1 + the patch Chris mentioned builds without bison, but llvm-gcc4 doesn't: /home/emil/ll/llvm-gcc4.0-2.1.source/missing bison -d -o gengtype-yacc.c ../../llvm-gcc4.0-2.1.source/gcc/gengtype-yacc.y WARNING: `bison' missing on your system. You should only need it if you modified a `.y' file. You may need the `Bison' package in order for

> On Thu, 20 Apr 2006, [UTF-8] Rafael Esp?ndola wrote: > > > I am trying to bootstrap the just released gcc 4.0.1 and the cvs head llvm. > > > > I was able to build the llvm tools without a problem. > > gcc has a small problem (from the apple branch IIRC): libojc is built > > unconditionally, so objc must be in the --enable-languages option for > > the

LLVM-GCC 4.0 fails on Cygwin, possibly due to lack of symbolic links. Configuring in i686-pc-cygwin/libstdc++-v3 configure: creating cache ./config.cache checking build system type... i686-pc-cygwin checking host system type... i686-pc-cygwin checking target system type... i686-pc-cygwin checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes

hello all! I can not install centos 5 in graphic mode on my pc ,my VGA card is XFX6800XT,when installtion started ,it tell me that my VGA card is 6600GT,it detected wrong! And then installtion can not be run with normal display. so I install in text mode ,after installtion , I can't start Xwindow! I only could work with console. I tried to install "NVdriver 9775",an error occured

Hello, LLVM community. I've built a cross-toolchain on Windows and I'm now trying to run unit tests for the LLVM libraries. I used Ninja as a build system and MSVC as host compiler without an issue, but when I try to run 'ninja check-llvm-unit', I get the following error: llvm-lit.py: C:/Users/sergej/Developer/llvm-project/llvm\utils\lit\lit\TestingConfig.py:102: fatal: unable

Hi LLVMers, The root of my SRC_DIR is: /home/hb/projects/src/llvm-1/llvm/ and the root of my OBJ_DIR is: /home/hb/projects/build/FC1/llvm-1-1. However, the configure script seems to have stripped some of the / from the paths: Makefile.common:63: /home/hb/projects/buildFC1llvm-1-1/Makefile.config: No such file or directory Makefile.common:69: /home/hb/projects/srcllvm-1/Makefile.rules: No such

On Sat, 2005-06-18 at 10:32 +0200, Henrik Bach wrote: > Hi LLVMers, > > The root of my SRC_DIR is: /home/hb/projects/src/llvm-1/llvm/ > and the root of my OBJ_DIR is: /home/hb/projects/build/FC1/llvm-1-1. > > However, the configure script seems to have stripped some of the / from the > paths: > Makefile.common:63: /home/hb/projects/buildFC1llvm-1-1/Makefile.config: No

officially support for llvm-gcc4.0 has been dropped. unofficially I still keep llvm-gcc4.0 compiling because I need it for some stuff. But this will only last until I can use 4.2. Andrew On Sat, Mar 22, 2008 at 5:00 AM, Joachim Durchholz <jo at durchholz.org> wrote: > Hi all, > > I'm wondering what the comparative status of llvm-gcc4.0 vs. llvm-gcc4.2 > is. Can anybody

On Mar 22, 2008, at 3:37 PM, Joachim Durchholz wrote: > Am Samstag, den 22.03.2008, 09:45 -0500 schrieb Andrew Lenharth: >> officially support for llvm-gcc4.0 has been dropped. >> unofficially I still keep llvm-gcc4.0 compiling because I need it for >> some stuff. But this will only last until I can use 4.2. > > OK, that's a clear roadmap. > Please do not rely

Am Samstag, den 22.03.2008, 09:45 -0500 schrieb Andrew Lenharth: > officially support for llvm-gcc4.0 has been dropped. > unofficially I still keep llvm-gcc4.0 compiling because I need it for > some stuff. But this will only last until I can use 4.2. OK, that's a clear roadmap. Maybe the docs should be updated to reflect this status? They still present 4.0 as if it were the default

>> Also I have in Makefile.rules (but not include in patch) some >> modification for simplify used common Makefile.rules in LLVM projects and >> non-LLVM project (guarding some LLVM specific parts by ifdef >> LLVM_OBJ_ROOT/LLVM_SRC_ROOT vars). > > I'm not sure about this, perhaps Reid would like to comment? > Patch attached. This patch with header

Branches have been created. You are free to checkin to cvs head again. I'll send mail once I have the prerelease tar balls up. Please continue to review and revise the documentation. I can fold this into the release later. Thanks, Tanya On Thu, 13 Apr 2006, Tanya Lattner wrote: > > I will be creating the release branch at 1:00pm PDT. Please refrain from > checking in from