Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!cadence!cadence.com!bammi From: bammi@acae127.cadence.com (Jwahar R. Bammi) Newsgroups: comp.sys.atari.st Subject: Re: GCC compile error Message-ID: Date: 20 May 91 15:24:18 GMT References: <9105082156.aa25310@Bonnie.ics.uci.edu> <5652@wucc.waseda.ac.jp> Sender: usenet@cadence.com (USENET News) Organization: Cadence Design Systems Lines: 34 In-Reply-To: ytsuji@wucc.waseda.ac.jp's message of 15 May 91 14:21:40 GMT the GCC-TOS library handles the '/' (automatically) and long file names(optionall), so "d:\tmp/cc100000.s" will map to the file "d:\tmp\cc100000.s". if you get errors such as cant find.... etc. there are two common problems (these should probably be added to the FAQ list) -- you extracted the gcc zoo archives with a old version of ZOO. that version of zoo extracts '-' in file names as '_' (dash as underscore). this causes problems when gcc.ttp tries to run say the preprocessor, which it cannot find, and complains that the file the preprocessor was supposed to produce is not found. the solution is to rename all files "gcc_XXX.ttp" to "gcc-XXX.ttp". (i dont know what versions of zoo are available on atari.archive, but zoo201.zoo does'nt have the problem.) -- another common problem is people not setting up the four environment variable GCCEXEC, GNUINC, GNULIB and TEMP correctly. -- a less frequent problem is gulam users not setting "set env_style mw" -- a slightly bigger problem is people not reading the docs in Documentation.zoo -- a more serious problem is people giving wrong advice on the net based on (unintelligent) guesses or showing quite obviously that they have'nt even bothered to read the README files, let alone the documentation, as the last two follow up's to the origonal posting clearly show. -- -- bang: uunet!cadence!bammi jwahar r. bammi domain: bammi@cadence.com GEnie: J.Bammi CIS: 71515,155