Date: Sat, 10 Mar 2001 19:56:32 +0200
From: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender: halo1 AT zahav DOT net DOT il
To: "Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be>
Message-Id: <1190-Sat10Mar2001195632+0200-eliz@is.elta.co.il>
X-Mailer: Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.6
CC: djgpp-workers AT delorie DOT com
In-reply-to: <CAEGKOHJKAAFPKOCLHDIOEGCCBAA.tim.van.holder@pandora.be>
Subject: Re: stubify and Windows ME
References:  <CAEGKOHJKAAFPKOCLHDIOEGCCBAA DOT tim DOT van DOT holder AT pandora DOT be>
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> From: "Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be>
> Date: Thu, 8 Mar 2001 18:43:31 +0100
> 
> > > Maybe the executable was open (possibly running in another window)?
> > 
> > He says that the executable was never created in the first place
> > (because of the problem with stubify).
> Well, I was unable to get EINVAL with stubify -v foo.

Sigh...  I _hate_ such mysteries!

The problem is, this isn't the first users who reports similar
problems with Windows ME.  So there _is_ some problem there.

Is your stubify the stock one from djdev203.zip, btw?

> I suggest you ask the person in question to try again, and post
>  a) the exact input file used
>  b) the specs file
>  c) the exact output produced by gcc

I already did that.  The info I posted here was based on his
responses.

Thanks for testing this, anyway.