Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-Epoch: 1045361240
X-Sasl-enc: fAWhwdmgrUGuu8fJol/GbQ
Message-ID: <3E4EF1EB.3090807@ece.gatech.edu>
Date: Sat, 15 Feb 2003 21:05:31 -0500
From: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: forward incompatibility?
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

patch-2.5.8-3 requires the new symbol strerror_r, which is not provided 
by cygwin-1.3.19; it was added in 1.3.20.  Therefore, if you've updated 
'patch' but not 'cygwin', you get a missing symbol popup.

I'm not complaining; this is not abnormal behavior.  We guarantee 
backward compatibility, not forward -- and this is a *forward* 
compatibility issue.  I just don't remember a warning in the 
patch-2.5.8-3 announcement that upgrading patch *requires* upgrading cygwin.

Not that I check forward compatibility, every time I release a new 
package, either...

--Chuck


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/