On Thu, Sep 10, 2009 at 09:19:36AM +0200, Per Olofsson wrote: > I thought I'd try building the new snapshots with clang instead of > gcc, to see what the static analyzer would catch. Unfortunately all 14 > gcc.mak files explicitly set CC and CFLAGS, instead of inheriting > values from the main makefile, making it a real chore. It's a similar problem as with the global makefile: I'm not really using it while developing. Sometimes, I need a debug version of the compiler, so I'll remove -O2 from CFLAGS in the makefile. Do you have an idea how to fix it without taking me the option to change a setting for one of the tools on the fly? > As the CC and > CFLAGS values vary a bit, I can't easily fix it with a perl oneliner > either... At least the CC value is always the same: uz@trixie:~/src/cc65/src$ grep "CC\s*=" */make/gcc.mak ar65/make/gcc.mak:CC = gcc ca65/make/gcc.mak:CC = gcc cc65/make/gcc.mak:CC=gcc cl65/make/gcc.mak:CC=gcc co65/make/gcc.mak:CC = gcc common/make/gcc.mak:CC = gcc da65/make/gcc.mak:CC=gcc grc/make/gcc.mak:CC = gcc ld65/make/gcc.mak:CC=gcc od65/make/gcc.mak:CC=gcc sim65/make/gcc.mak:CC = gcc The CFLAGS value varies, but for a reason. Some of the tools need #defines, others don't. Regards Uz -- Ullrich von Bassewitz uz@musoftware.de ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Thu Sep 10 20:12:11 2009
This archive was generated by hypermail 2.1.8 : 2009-09-10 20:12:13 CEST