Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-ID: <001801bf1e90$62f042a0$27acdfd0@InspirePharm.Com> From: "Suhaib M. Siddiqi" To: References: <19991023161319 DOT 20604 DOT qmail AT www0w DOT netaddress DOT usa DOT net> <19991023232133 DOT B5735 AT cygnus DOT com> <3812F9AC DOT 78549EE8 AT ece DOT gatech DOT edu> <19991024093725 DOT A7861 AT cygnus DOT com> Subject: Re: X11R6.4 for Cygwin Release v1.0? (And thanks) Date: Sun, 24 Oct 1999 22:26:44 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2014.211 X-Mimeole: Produced By Microsoft MimeOLE V5.00.2014.211 Use X11 R6.x and lesstif marked with *-ss-dev.tar.gz. I think you should be OK. Suhaib ----- Original Message ----- From: Chris Faylor To: Charles S. Wilson Cc: Sent: Sunday, October 24, 1999 9:37 AM Subject: Re: X11R6.4 for Cygwin Release v1.0? (And thanks) > On Sun, Oct 24, 1999 at 08:21:00AM -0400, Charles S. Wilson wrote: > > > >> > >> The link errors that you were getting are due to the fact that *object* > >> files and *libraries* are not necessarily compatible. i don't know > >> about the STATUS_ACCESS_VIOLATION problem, however. > >> > > > >So *object* files and *libraries* developed using the following > >platforms are mutually incompatible? > > > >1) cygwin-b20.1 > >2) recent snapshots > >3) Cygwin CD 1.0 > >4) cygwin-b21 > > We guarantee that a recent cygwin1.dll will work with any program or DLL > which loads it. > > We do not guarantee that object files or libraries produced by a > previous version of cygwin/gcc will be usable with a new DLL or cygwin > stub library. In particular, we may decide to add an additional symbol > to the DLL/stub library for export. > > So, if your object file has been using the 'foo' routine from the stub > library and was essentially statically linking it into your program, > it will be confused by the fact that the 'foo' routine is now exported > by the DLL. That is apparently what is happening here. > > The solution is to recompile from source. > > I am not going to provide an exhaustive list of what's compatible with > what. However, it's likely that B20 object files are incompatible with > snapshots or the Cygwin CD. It's likely that files produced using > snapshots from the last couple of months will work with the Cygwin CD. > > In short, if it links, you're ok. If it doesn't, recompile. > > cgf > > -- > Want to unsubscribe from this list? > Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com > -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com