From: cgf AT bbc DOT com (Christopher Faylor)
Subject: Re: building cygwin.dll
18 Mar 1998 06:57:57 -0800
Message-ID: <Eq0rF4.2r9.cygnus.cygwin32.developers@bbc.com>
References: <3 DOT 0 DOT 5 DOT 32 DOT 19980316131724 DOT 0095a770 AT pop DOT ma DOT ultranet DOT com>
Reply-To: cgf AT bbc DOT com
To: cygwin32-developers AT cygnus DOT com

In article <3 DOT 0 DOT 5 DOT 32 DOT 19980316131724 DOT 0095a770 AT pop DOT ma DOT ultranet DOT com>,
Larry Hall  <lhall AT rfk DOT com> wrote:
>Hi all,
>
>Anyone else had trouble using a locally built cygwin.dll since moving to 
>either the b19.1 source or the "developer's" source that Geoff published 
>last week.  Whenever I try either of these two source code bases, I find
>that the DLL that gets generated is invalid.  If I try to start bash with
>the new DLL, I get a message box stating:
>
>bash.exe - Bad Image
>
>The application or DLL in d:\usr\H-i386-cygwin32\bin\cygwinb19.dll is not a
>valid Windows NT image.  Please check this against your installation diskette.
>
>If I return to a DLL that I built previous to the code base change (yes I 
>built this one too), the DLL works fine and I get no complaints from any
>tools.  The DLL I build simply patches in a couple of Sergey's latest
>changes and one from me that fixes console colors.  Anybody else see this?

I haven't seen this, but I am using Mumit's EGCS release to build stuff.
Maybe that's the difference.
-- 
http://www.bbc.com/	cgf AT bbc DOT com			"Strange how unreal
VMS=>UNIX Solutions	Boston Business Computing	 the real can be."