Date:	Tue, 9 Sep 1997 14:19:18 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To:	Ivo Janssen <ivo AT ricardis DOT tudelft DOT nl>
cc:	djgpp AT delorie DOT com
Subject:	Re: sed problem
In-Reply-To:	<Pine.LNX.3.95.970908105452.7929A-100000@ricardis.ricardis.tudelft.nl>
Message-ID:	<Pine.SUN.3.91.970909141838.7143C-100000@is>
MIME-Version:	1.0

On Mon, 8 Sep 1997, Ivo Janssen wrote:

> sed: garbled command s|^COMPILERS[      ]*=[    ]*\
> 
> Original lines in configure
>  sed -e "s|^SUBDIRS[     ]*=.*$|SUBDIRS = $subdirs|" \     
>      -e "s|^LANGUAGES[   ]*=[    ]*\(.*\)$|LANGUAGES = \1 $all_languages|" \
>      -e "s|^COMPILERS[   ]*=[    ]*\(.*\)$|COMPILERS = \1 $all_compilers|" \
>      -e "s|^LANG_MAKEFILES[      ]*=.*$|LANG_MAKEFILES = $all_lang_makefiles|" \     
>      -e "s|^LANG_STAGESTUFF[     ]*=.*$|LANG_STAGESTUFF = $all_stagestuff|" \    
>      -e "s|^LANG_DIFF_EXCLUDES[  ]*=.*$|LANG_DIFF_EXCLUDES = $all_diff_excludes|" \
>      Makefile.tem > Makefile.xx

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.

One possible problem is that your TMPDIR is on a full disk or
something.  But that's a wild guess.

> Any other ideas? I'm using sed-1.18 from DJGPPv2.01
> I noticed there is a newer sed (sed-2.05), but not for DJGPP...

Don't use 2.05, it's broken in some cases, is much slower than 1.18,
and needs ludicrous amounts of memory for some not-so-complex
scripts.  In any case, your problem is something specific to DJGPP and
your system setup, not a bug in Sed.

- Raw text -