Mail Archives: djgpp/2008/03/25/20:16:14
On Tue, 25 Mar 2008 15:02:08 -0700 (PDT) in comp.os.msdos.djgpp,
jmichae3 AT yahoo DOT com wrote:
>On Mar 15, 11:04 pm, Brian Inglis <Brian DOT Ing DOT DOT DOT AT SystematicSW DOT Invalid>
>wrote:
>> On Sat, 15 Mar 2008 14:19:17 -0700 (PDT) in comp.os.msdos.djgpp,
>>
>> jmich DOT DOT DOT AT yahoo DOT com wrote:
>> >do you think tvision could be brought up to 4.2-3 standards? usually
>> >what the problem is during the compile is a string literal bsing used
>> >in a char * and apparently GCC 4.2-3 chokes on it. I know it's not
>> >proper, but wouldn't it be fixed if those were changed to
>> >const_cast<char*>("blahblah") instead of "blahblah"?
>>
>> Try removing compile flags -Werror, -pedantic, and -ansi if used, and
>> add -std=c89 to see if that eliminates compile failures.
>> The first option mentioned changes all warnings into errors, so all
>> warning options used e.g. -W... increase the likelihood of compile
>> failures.
>> If the code is not GCC clean, you will get some or evan a lot of
>> warnings, but unless the code is really bad, as in causing undefined
>> behaviour, you should not get compilation failures.
>>
>
>I specified no compile flags.
Thought you were using a makefile, which might use $(CFLAGS), and will
do so if you are using implicit .c.o rules.
Try using -std=c89 to allow K&R parsing.
Do not use -traditional, as that is now just a CPP switch.
--
Thanks. Take care, Brian Inglis Calgary, Alberta, Canada
Brian DOT Inglis AT CSi DOT com (Brian[dot]Inglis{at}SystematicSW[dot]ab[dot]ca)
fake address use address above to reply
- Raw text -