https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68427
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to wam from comment #3) > comment 1: How do I go about doing that (posting preprocessed source file) ? It's explained at the link you should have read before creating a bug: https://gcc.gnu.org/bugs/ > The tarball I uploaded just has 2 text files showing the output of my effort > to compile the code, & the code in its own tarball. Yes I know, I used the same commands as you showed in your file, and it compiled successfully. > comment 2: The code was ANSI-C for about 15 years (from ~1995 on), then > converted to C++ by simply renaming it to gauss.cpp & overloading the names > of the various gauss functions. It is otherwise legal ANSI C code. But that's irrelevant. It's *not* ANSI C code if you've used overloaded functions, and you're compiling it as C++ anyway so it's besides the point. C and C++ are different languages, just because something used to be valid C doesn't mean failing to compile as C++ indicates a compiler bug. > As to the > makefile, I used GCC 4.8.5, pkg-installed, i.e. compiled up by the FreeBSD > folks & retreived by me from their repo. I compiled the GCC5.2.1 up myself, > adding Graphite support (recently accomodated by the GCC maintainer(s)). I > did nothing to the makefile myself. I originally posted this to the > FreeBSD-toolchain list & was advised to repost it here. When you compile it, > are you using FreeBSD 9.3R to do so, or another implementation ? I only tried on GNU/Linux. The errors shown in your file are not platform-specific, they suggest a header file was missing or something like that.
