Sender:	vheyndri AT rug DOT ac DOT be
Message-Id:	<3510D96E.3E35@rug.ac.be>
Date:	Thu, 19 Mar 1998 09:38:06 +0100
From:	Vik Heyndrickx <Vik DOT Heyndrickx AT rug DOT ac DOT be>
Mime-Version:	1.0
To:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Cc:	Andris Pavenis <pavenis AT laima DOT acad DOT latnet DOT lv>, djgpp AT delorie DOT com
Subject:	Re: Rebuilding config.in in gcc-2.8.1
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 980317184045 DOT 19045J-100000 AT is>

Eli Zaretskii wrote:
> 
> On Tue, 17 Mar 1998, Andris Pavenis wrote:
> 
> > ---------  fragment from c:/djgpp/bin/autoheader  -------
> >
> > if test $# -eq 0; then
> >   tmpout=autoh$$
> >   trap "rm -f $tmpout; exit 1" 1 2 15
> >   exec > $tmpout
> > fi
> 
> I don't remember seeing this fragment.  Vik, did you include it in the
> excerpts that you posted?

Nope, but it seems that I should have. Sorry, about that.
 
> Does this mean that if Autoheader is run with an argument this problem is
> avoided?  Can you try?

I can, but I don't understand what you want me to do exactly (I don't
share the 2 years of experience in complicated scripts, I barely can
read one)
 
> Anyway, if the part of the script which mv'es $tmpout does that while
> output is still redirected to $tmpout, then this indeed will not work on
> non-Unix systems.  

I'm not so sure whether moving a file that is open is allowed on Unix
systems. Enfin, I don't know and considering i-nodes, it may work there.

> I think this should be changed in the ported Autoheader.  

So do I, but don't look at me. I might create a nuclear bomb out of
autoheader. (I'd bet the American goverment will intercept this email)

> Renaming or deleting files which are open by some program is
> nothing but trouble on MS-DOS/MS-Windows.

I don't blame M$ for this. It's more than sensible not to allow that.

-- 
 \ Vik /-_-_-_-_-_-_/   
  \___/ Heyndrickx /          
   \ /-_-_-_-_-_-_/

- Raw text -