Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!hplabs!otter.hpl.hp.com!hpltoad!ghiggins!gjh From: gjh@hplb.hpl.hp.com (Graham Higgins) Newsgroups: comp.sys.atari.st Subject: Gnu Blues Message-ID: Date: 6 Nov 90 21:11:20 GMT Sender: news@hplb.hpl.hp.com (Usenet News Administrator) Organization: Hewlett-Packard Laboratories, Bristol, UK. Lines: 25 Nntp-Posting-Host: ghiggins.hpl.hp.com I've been experiencing a replicable problem with GNU C as available on terminator. I thought I'd have a bash at "bash" which somewhat cryptically appeared on the archives. It needs the GNU fileutils stuff (ls, cp, etc), so I've been trying to compile them up on the (newly-expanded) ST. 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. 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. 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. Any ideas anyone? Gray (ever puzzled)