Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!know!sdd.hp.com!caen!math.lsa.umich.edu!math.lsa.umich.edu!hyc
From: hyc@math.lsa.umich.edu (Howard Chu)
Newsgroups: comp.sys.atari.st
Subject: Re: GNUC + cs.uni-sb.de
Message-ID: <1990Nov19.224046.14728@math.lsa.umich.edu>
Date: 19 Nov 90 22:40:46 GMT
References: <GJH.90Nov15180640@ghiggins.hpl.hp.com> <1990Nov16.120053.1@simvax.labmed.umn.edu> <GJH.90Nov19120556@ghiggins.hpl.hp.com>
Sender: usenet@math.lsa.umich.edu
Distribution: comp
Organization: University of Michigan Math Dept., Ann Arbor
Lines: 30

In article <GJH.90Nov19120556@ghiggins.hpl.hp.com> gjh@hplb.hpl.hp.com (Graham Higgins) writes:
>++   > gcc: /tmp/cc1000000.cpp cannot find file.
>
>++   Query:  I notice that in your examples, there are 9 characters before the
>++   '.cpp' tag on the file.
>
>Sorry, heavy-handed typing, it should be /tmp/cc100000.cpp. It appears that
>the problem arises from GCC's interpretation of pathnames for GNUINC and
>a few little problems like requiring quotes surrounding 
>
>setenv GNUINC='c:\gnu\include'
>
>do the quotes remain for ENVIRON.PRG? If the environment variable is set
>by both ENVIRON.PRG and GULAM.PRG, which wins --- and when? 

If you run ENVIRON in your AUTO folder, every program you spawn from the
desktop will get a copy of the values you set with ENVIRON. When Gulam runs
and gets a setenv command, the changes that it makes are to the copy of
the environment that it received. In this copy, any setenv command will
completely replace whatever values it inherited from ENVIRON. If you've got
things working with ENVIRON, then you don't need to set them again in Gulam.

Please note - in Gulam, you leave out the '=' equals sign in the set[env]
commands. e.g.
	setenv GNUINC c:\gnu\include
--
  -- Howard Chu @ University of Michigan

Mac// - adv., q.v. MacToo, e.g.  McHave a McHappy McDay!
		McThanks, McYou MacToo!