[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Tinycc-devel] [PATCH] Don't break compilation process with unknow o
Re: [Tinycc-devel] [PATCH] Don't break compilation process with unknow option
Wed, 7 Jan 2015 06:14:02 +0300
> That would avoid rewriting the Makefile to only add switches to CFLAGS that
> are supported by the compiler as it should have been done ;-) (no blame, we
> all do this).
After applying a "disable DTEST" patch to allow "make test" to pass a
./configure --cc=tcc; make; make install; make test
tcc -o tcctest.cc tcctest.c -I.. -I.. -w -DTCC_TARGET_I386
-std=gnu99 -O0 -fno-omit-frame-pointer
tcc: error: invalid option -- '-std=gnu99'
With a patch apllied a test can be performed with
make CFLAGS=-Wunsuported test
And your solution? What you will add to CFLAGS?
2015-01-05 0:01 GMT+03:00, RoboTux <address@hidden>:
> Le 2015-01-04 04:42, Sergey Korshunoff a écrit :
>>> GCC and clang also error out for unknown option. What option caused
>> program to fail to compile?
>> The patch is for the case with -Wunsupported. In such case a user will
>> is "Don't trap, only warning". There are many gcc options which tcc
>> don't support. But in many cases, this options are not important.
>> Changing a Makefiles is not a solution when trying to use tcc insteed
>> of gcc.
>> And a patch test command is:
>> /tcc -Wunsupported -traditional -E tcc.c -o tcc.i
> I'd prefer a patch that just gives a warning for unknown -W option. It
> would be just like if the detection was really bad. Doing the same for
> other options would be more risky IMHO. That would avoid rewriting the
> Makefile to only add switches to CFLAGS that are supported by the
> compiler as it should have been done ;-) (no blame, we all do this).
> Best regards,