Date: Tue, 9 Sep 1997 13:53:44 +0200 (MET DST) From: Ivo Janssen Reply-To: Ivo Janssen To: Eli Zaretskii cc: djgpp AT delorie DOT com Subject: Re: sed problem: FIXED! In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Precedence: bulk On Tue, 9 Sep 1997, Eli Zaretskii wrote: > On Mon, 8 Sep 1997, Ivo Janssen wrote: > > > sed: garbled command s|^COMPILERS[ ]*=[ ]*\ > > > Write a simple program that just prints its arguments (by walking the > argv[] array), call it sed.exe, rename the real sed.exe, put the fake > sed.exe in the same place and run the script. Then look what > arguments did your sed get and see if you can guess what's the reason > of this snafu. If you cannot figure it out, post the results here. OK: This is what is wrong with my system setup (because that's what it is, not sed oir djgpp or whatever!)): I'm working here on a corporate LAN. Last week they changed something in the Netware logon scripts, thereby placing a new entry in my path: X:\BATCH. And guess what pre-historic version of sed is in directory X:\BATCH ....... AAAARRRRGGGGHHHH!!!! Oh well, guess we have a job offer for a new sysadmin very shortly (after we buried this one). Thanks to Eli Zaretskii, for the tip above. After that, I noticed that bash stillo complained, and ewasn't even calling my C:\djgpp\bin\sed.exe, but rather X:\batch\sed.exe. The latter one is dated 91/01/10 11:58. Don't know what version that is. Ivo Janssen --------------------+--------------------------------+-+ +---+ | IVO JANSSEN | ivo AT ricardis DOT tudelft DOT nl | | | | | Ricardishof 1/428 | janssen AT cardit DOT et DOT tudelft DOT nl | | |-+ | | 2614 JE Delft | http://www.et.tudelft.nl/~ivo/ | +->-| (|) | the Netherlands | Dept of Electrical Engineering | |-+ | | +31-15-2855973 | Delft University of Technology | | | +-------------------+--------------------------------+ --- --- Do you want to win $1000 by using you computer's idle time AND prove that 56-bit encryption isn't _that_ safe? Try http://rc5.distributed.net/