Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Sat, 10 May 2003 12:54:20 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: cygipc (and PostgreSQL) XP problem resolved! Message-ID: <20030510105420.GE19367@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <3EBC8ED0 DOT 4040906 AT ece DOT gatech DOT edu> <005f01c316d1$4abc82b0$0a1c440a AT BRAMSCHE> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <005f01c316d1$4abc82b0$0a1c440a@BRAMSCHE> User-Agent: Mutt/1.4.1i On Sat, May 10, 2003 at 10:51:05AM +0200, Ralf Habacker wrote: > Charles Wilson wrote: > > > Conclusion: package maintainers that distribute shared libs need to > > recompile ASAP, so that dependent apps can be recompiled if needed. > > > > Caveat to the caveat: this analysis ONLY applies if the compiled object > > (DLL, static lib, executable, etc) actually USES one of the symbols > > whose typedef has changed. Currently, the list of affected packages is > > pretty small (zlib is one). > > > With qt I have a similar problem. The current release was build with > cygwin-1.3.20. Currently it is not possible to link a qt application with recent > cygwin release due to type problems. > > header - QTextStream::QTextStream( FILE *, int mode ) > > used - QTextStream::QTextStream(__sFILE64 *, int) Huh? That's correct. What's the exact problem with this? The application (or DLL) shouldn't worry about the actual implementation of FILE*. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/