Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!uakari.primate.wisc.edu!crdgw1!uunet!mcsun!unido!sbsvax!roeder From: roeder@robin.cs.uni-sb.de (Edgar Roeder) Newsgroups: comp.sys.atari.st Subject: Re: Gnu Blues Message-ID: Date: 9 Nov 90 18:11:16 GMT References: Sender: news@sbsvax.cs.uni-sb.de Organization: Universitaet des Saarlandes, Saarbruecken (Germany) Lines: 39 In-reply-to: gjh@hplb.hpl.hp.com's message of 6 Nov 90 21:11:20 GMT In article gjh@hplb.hpl.hp.com (Graham Higgins) writes: > gcc-as started to barf on a number of files, I got gcc to drop .s versions > and looked carefully, only to find a number of statements of the form ... > stab "e:\include\strings.h" > which was parsed (correctly) by gcc-as escape-i and escape-s. What I can't > figure out is why this particular include appears, as no other one does. I don't know which version of gcc is on terminator, but the versions derived from Jwahar Bammi's port should understand slashes (/) instead of (\) as the directory delimiter. > Anyway, I'm still getting "Bogon Alerts" from the compiler, even when I > double-backslash the paths. What concerns me is that this is standard GNU > distribution fileutils, GNU C shouldn't have a problem compiling it. O.K., > whether it runs or not is another thing, but it should compile up OK. These bogon-alerts come from a bug in the linker when you link with symbol table included (they use a wrong comparision function that cannot distinguish all three possible arrangements of the input-params). If you link with -s (no symbols), these bogon alerts should go away. BTW. I have compiled the fileutils with almost no changes (except in the Makefile). > I started to consider whether the GNU C port had some problem (after > playing around with GNUINC = this-n-that for a while. It made no > positive difference. You could of course put strings.h in the current directory, so it would't need any directory delimiter in the above .stab entry. > Any ideas anyone? > Gray (ever puzzled) You could try the gcc version and library at cs.uni-sb.de. Hope this helps! - Edgar