search for: colorgcc

When I compile the latest CVS, I get the following error: Compiling param/params.c gcc.colorgcc: Internal compiler error: program cpp got fatal signal 11 make: *** [param/params.o] Error 1 What did I do wrong?? Stephen Gerstacker The Gradall Company phone: 339-2211 ext. 8814 ******************************************************* The information contained in this transmission is confid...

...ompiler/llvm-2.4/tools/llvm-config/LibDeps.txt because dependencies changed [ 93%] Checking for cyclic dependencies between LLVM libraries. [ 93%] Building llvm-config script. -- The C compiler identification is GNU -- The CXX compiler identification is GNU -- Check for working C compiler: /usr/lib/colorgcc/bin/gcc -- Check for working C compiler: /usr/lib/colorgcc/bin/gcc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working CXX compiler: /usr/lib/colorgcc/bin/c++ -- Check for working CXX compiler: /usr/lib/colorgcc/bin/c++ -- works -- Detecting CXX co...

I may try to use the Makefile then. When using gcc the Makefile is CC := colorgcc obj-m := hello.o KERNELDIR := /lib/modules/2.6.36.1/build PWD := $(shell pwd) modules: $(MAKE) -C $(KERNELDIR) M=$(PWD) modules #modules install: # $(MAKE) -C $(KERNELDIR) M=$(PWD) modules_install How to change it so the generating result is .bc file not the .o file? PLEASE BE KIND AND HELP...

Dear Chen, I tried the command you told me. It turns out that clang use -I option rather then -isystem. But after I included the init.h file, it fired at me that "asm/processor.h" is not fount. Then I included that file using -I option and some other files were said not found! It's like I opened a can of worms... I can still continue to include the file that is said not found. But

Thanks for your help and patience! Best regards, Zhen Kai At 2012-04-16 15:35:25,"陳韋任" <chenwj at iis.sinica.edu.tw> wrote: >> The thing is that I know the Makefile to complete that task. But what I want to know the clang command that can do that. Since the makefile will generate a .ko file while I can use the clang command "-O3-emit-llvm" to generate a

Olly and I have been discussing details of our policy for deprecating features, and we thought it would be useful to canvas users opinions on a particular aspect. From time to time, we remove features from the library (usually because we have a better replacement). To make life easier for users, we've been following a deprecation policy, so that users are given plenty of warning of