Xref: utzoo gnu.gcc.bug:1611 comp.windows.x:14700 Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!brutus.cs.uiuc.edu!samsung!ginosko!uunet!mcsun!hp4nl!mhres!jv From: jv@mh.nl (Johan Vromans) Newsgroups: gnu.gcc.bug,comp.windows.x Subject: Re: Odd behaviour of gcc 1.36 compiled xterm Message-ID: Date: 29 Oct 89 23:12:29 GMT References: <1124@pcsbst.UUCP> Sender: jv@mhres.mh.nl Organization: Multihouse Gouda, the Netherlands Lines: 19 In-reply-to: jkh@meepmeep.pcs.com's message of 28 Oct 89 15:39:15 GMT In article <1124@pcsbst.UUCP> jkh@meepmeep.pcs.com (Jordan K. Hubbard) writes: > Anyway, I've compiled the whole X11R3 suite (well, it's closer to X11R4 > Beta, really.. Hmmm.) with GCC 1.36 with the following flags: > > CCOPTIONS = -fcombine-regs -fstrength-reduce -ftraditional -DNOSTDHDRS ... ^^^^^^^^^^^^^ The pre-processor option is spelled "-traditional". "-ftraditional" does *NOT* influence the pre-processor, but also doesn't yield a message about being an unknown compiler option. Johan -- Johan Vromans jv@mh.nl via internet backbones Multihouse Automatisering bv uucp: ..!{uunet,hp4nl}!mh.nl!jv Doesburgweg 7, 2803 PL Gouda, The Netherlands phone/fax: +31 1820 62944/62500 ------------------------ "Arms are made for hugging" -------------------------