Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Message-ID: <39918E3A.469B1230@ece.gatech.edu> Date: Wed, 09 Aug 2000 13:00:42 -0400 From: Charles Wilson X-Mailer: Mozilla 4.7 [en] (X11; U; SunOS 5.7 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: GRENON Richard CC: cygwin@sourceware.cygnus.com Subject: Re: Problems with Libtiff, Libpng References: <39911A7A.D5611ABA@onera.fr> <39916B03.E4EED9AC@ece.gatech.edu> <39917A45.7F09F1F6@onera.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit GRENON Richard wrote: > In the OpenDX case, no custom libpng.dll was included in the package so > it should use the Cygwin 'official' one. Could it be a problem for other > applications if I keep libpng-1.0.6 with my recent Cygwin 1.1.4 update > instead of latest libpng-1.0.8 ? Until now, I did only home work with > some simple fortran codes, OpenDX and an old personal Unix X11 graphic > code. Everything seems to work well (except some Win98 crashes with X11) > and as I am not on a network and don't need any Cygwin advanced feature > I would like to maintain this installation "as is" for a long time. I see no problem with that. *So far*, no other packages have been released that depend on libpng -- so it shouldn't really matter WHAT version you have. The changes from -1.0.6 to -1.0.8 were: 1) revert a change that had caused a compatibility problem --> doesn't apply because you have no apps (other than OpenDX) that depend on libpng 2) fix a bunch of problems w.r.t. assembly language acceleration --> doesn't apply because neither my 1.0.6 libpng package nor my 1.0.8 package included any of the assembly stuff. 3) Other minor fixes. So, if what you have is working, stay with it. For now. --Chuck -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com