gjh@hplb.hpl.hp.com (Graham Higgins) (05/31/91)
In article <9105082156.aa25310@Bonnie.ics.uci.edu>, bferrer@Bonnie.ICS.UCI.EDU says: > > After downloading the gcc compiler and getting very thing ready, I came >across another problem. When I type in gulam gcc -v hello.c, I get an error: > >can't find d:\tmp/cc100000.s > >or something like that. gcc created a file that has a slash in the filename >which does not exist how can i fix this error. Whilst apratt, entropy, bammi and davidli are all correct in observing that the GNU environment variables need setting correctly, I believe that this is *NOT* the case for this poster and that pointed references to "RTFR" may have been a little harsh. I got *exactly* the same problem --- but with *all* the enviroment variables correctly set --- boy, was I confused before I figured out what I'd done ... I had d/l'ed gcc139b.lzh from terminator and (deliberately neglecting to keep copies of the previous port) unarchived the replacement code straight into my c:/gnu directory, including the CRC-corrupted cc1, the corruption of which lharc reported, but it nevertheless wrote the file. The corruption was reported here, but a correction wasn't immediately available (no criticism intended). I never followed this up until recently, when I had occasion to test a gnumake port which resulted in the now-familiar "can't find c:/usr/tmp/cc100000.s" message If you use the original corrupted distribution (i.e. without replacing the gcc-cc1.ttp with the updated version from a.a.umich.edu), GCC reports that it is unable to find $TMP/cc100000.s --- because the corrupt cc1 has the -quiet flag automatically set, it crashes and exits quietly, never writing the .s file, hence the 'cannot find" error. I d/'ed the corrected distribution of cc1 from a.a.u.e and the problem vanished. I checked the posters' queries and they were both quoting problems with "$TEMP/cc100000.s", which should have tipped us off; "$TEMP/cc100000.cpp" ^ ^^^ (the first temp file to be written) is normally associated with environment variable problems. Having a missing .s file means that a .cpp file was found by cc1. Question: Does gcc139b.lzh on a.a.u.e contain the corrupted or uncorrupted gcc-cc1.ttp? It's not immediately obvious because both versions of cc1 are exactly the same byte size. Graham ====== ------------------------------------------------------------------ Graham Higgins | gjh%ghiggins@hpl.hp.co.uk Hewlett-Packard Labs | gjh%ghiggins@hplb.hpl.hp.com Filton Road, Stoke Gifford | gjh%hplb.csnet@csnet-relay.arpa Bristol, U.K. | ...!mcvax!ukc!hplb!gjh Tel: +44 272 799910 x24014 Fax: +44 272 790554 ------------------------------------------------------------------ Disclaimer: My opinions above are exactly that, mine and opinions. ------------------------------------------------------------------