From: Hans-Bernhard Broeker Newsgroups: comp.os.msdos.djgpp Subject: Re: cant get rhide to compile Date: 26 Apr 2001 12:55:46 GMT Organization: Aachen University of Technology (RWTH) Lines: 38 Message-ID: <9c95si$q2v$1@nets3.rz.RWTH-Aachen.DE> References: <3AE7F2E5 DOT 99133F6A AT ma DOT tum DOT de> NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de X-Trace: nets3.rz.RWTH-Aachen.DE 988289746 26719 137.226.32.75 (26 Apr 2001 12:55:46 GMT) X-Complaints-To: abuse AT rwth-aachen DOT de NNTP-Posting-Date: 26 Apr 2001 12:55:46 GMT Originator: broeker@ To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Waldemar Schultz wrote: [...] > there was an environment variable named CFLAGS set, > which was needed by an other compiler I used. Which again proves the old rule true: *Don't* mix up setups for several compilers. There are bound to be lots of problems like this. One compiler using the 'cpp' of the other, the wrong 'make' being first in the path, environment variables required by one, but lethal to the other --- all that stuff, and possibly more. If you have more than a single compiler installed, you have to isolate them from each other. Use setup batch files that modify the environment of a running DOS shell for a particular compiler. Don't put any modification one of them needs into autoexec.bat itself --- put them into bcc.bat, gcc.bat and whatever else. If you're running in raw DOS, it's very handy to also create 'end_gcc.bat' and friends, so you can switch around between different compiler setups at any time, without rebooting the box. All these batch files should be in a central directory (c:\batches, e.g.), which is in the default PATH set by autoexec.bat. If you use Win9x, prepare copies of the DOS-Box link on the desktop, and change their 'startup batch file' to execute the setup. That way, you can click and have a "DJGPP DOS window" or a "Borland C++ DOS window" and so on. On my box at home, I have no less than 12 C compilers (3 versions of DJGPP, RSXNTDJ, Borland versin 2, 3, 4, 5.5 and C++ builder 1, MinGW32 and Cygwin, Bloodshed DevC++, and may be there's a LCC-win32 still hiding somewhere, too) --- without such tricks, that'd be absolutely impossible to manage. -- Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de) Even if all the snow were burnt, ashes would remain.