Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!gegeweb.org!de-l.enfer-du-nord.net!feeder2.enfer-du-nord.net!feeder.erje.net!news-1.dfn.de!news.dfn.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Martin Wuerthner Newsgroups: comp.sys.acorn.programmer Subject: Re: Porting 'zip' - CC fatal error msg query Date: Fri, 10 Jun 2011 20:07:57 +0200 Organization: MW Software Lines: 24 Message-ID: <37ef45e151.martin@bach.planiverse.com> References: <4def6e1b$0$11158$e4fe514c@dreader31.news.xs4all.nl> X-Trace: individual.net coQSaRikUFa5bYZlrLHuDQjI9Quw2zjLjETdH0C0rJ1NwKZqLS X-Orig-Path: bach.planiverse.com%martin Cancel-Lock: sha1:WXfCLCzwmHNB1745ks2N4xPl6C8= X-Editor: EmailEdit 6.00 User-Agent: Messenger-Pro/6.00 (MsgServe/6.00) (RISC-OS/5.16) NewsHound/v1.50-32 Xref: x330-a1.tempe.blueboxinc.net comp.sys.acorn.programmer:414 In message <4def6e1b$0$11158$e4fe514c@dreader31.news.xs4all.nl> Erik G wrote: > This is an internal compiler error. That means that there is a bug > somewhere in the compiler itself. [...] > The eventual solution to this problem has to be worked out by the makers > of the compiler. I suggest you send the error message report and > information on where to find the source file (and the header files that > are included) to them. For C compilers, it is common practice to send preprocessed sources (output of cc -E) when reporting bugs. That avoids having to mess about with header files, include paths, different versions of system header files, etc. It is easy enough to check whether the error still occurs when compiling the preprocessed source file (which is all the compiler proper sees anyway). -- Martin --------------------------------------------------------------------- Martin Wuerthner MW Software http://www.mw-software.com/ RISC OS Software for Design, Printing and Publishing ---------------------------------------------------------------------