X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f From: "Robbie Hatley" Newsgroups: comp.os.msdos.djgpp References: <1175025372 DOT 220047 DOT 169080 AT o5g2000hsb DOT googlegroups DOT com> Subject: Re: "Make" works at home, fails at work. Lines: 53 Organization: Tustin Free Zone X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1807 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1896 Message-ID: <3qFOh.977$5e2.23@newssvr11.news.prodigy.net> NNTP-Posting-Host: 69.231.38.234 X-Complaints-To: abuse AT prodigy DOT net X-Trace: newssvr11.news.prodigy.net 1175134975 ST000 69.231.38.234 (Wed, 28 Mar 2007 22:22:55 EDT) NNTP-Posting-Date: Wed, 28 Mar 2007 22:22:55 EDT X-UserInfo1: O AT XQBW_D@RRS@^LYMRKNOPDA[X_LPO AT FFA_J]Q]KEYUNDQUCCNSUAACY AT L[ZX__HGFD]JBJNSFXTOOGA_VWY^_HG AT FW_HUTHOH]TBPGCO\P^PLP^@[GLHUK AT WLECKFVL^TYG[@RMWQXIWM[SDDYWNLG_G[_BWUCHFY_Y AT AS@Q[B\APPF AT DCZM_PG_VSCPQZM Date: Thu, 29 Mar 2007 02:22:55 GMT To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Ok, I finally solved this problem, with a little help from "rugxulo". This gets interesting, and really is on-topic for this group, even though it doesn't seem so at first; bear with me. In response to my query yesterday in which I said make works at home but not at work, replied: > (However, why it supposedly works on one Win2k machine and not another > is weird. Is there a SHELL define in your makefile or default rules? > Is bash running or your shell defined as bash somehow on one and not > another?) Indirectly, that hit the nail on the head. It got me to thinking that this was actually a command-processor problem, not a Gnu-Make problem. So I tried running an AWK script: same problem, can't run commands. I tried running some older DOS apps, and got even more bizarre results: "Invalid COMMAND.COM Cannot Load COMMAND System Halted". So I googled "Invalid COMMAND.COM Cannot Load COMMAND System Halted" which sent me to this Microsoft knowlege-base artical: http://support.microsoft.com/kb/282064 Which explained that systems that have been converted from Win-m.e. to Win-2K can have a bogus line in the this file: C:\Windows\System32\autoexec.nt that sets comspec to "command.com" when it should actually be "cmd.exe". When I fixed that, the problem went away. So when running DJGPP tools on machines that were upgraded from Win-m.e. to Win-2000, always do this: 1. Erase the "comspec" line from the file "C:\Windows\System32\autoexec.nt". (Some systems will have "WINNT" -- or something else -- as the Windows directory.) 2. Fire-up C:\WINDOWS\SYSTEM32\regedt32.exe and edit "HKLM\System\CurrentControlSet\Control\Session Manager". 3. Delete the "COMSPEC" value. 4. Make a new "COMSPEC" of type REG_EXPAND_SZ, with value "%systemroot%\system32\cmd.exe". OTHERWISE, many DJGPP tools will fail or crash on such machines. As I found out the hard way. -- Cheers, Robbie Hatley lone wolf intj aatt pac bell dott net