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
Date: Thu, 10 Jul 2003 15:44:51 -0400
From: Christopher Faylor <cgf-idd AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: development under 1.5.0 ?s
Message-ID: <20030710194451.GA9757@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <Pine DOT GSO DOT 4 DOT 56 DOT 0307101415530 DOT 1846 AT eos>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.GSO.4.56.0307101415530.1846@eos>
User-Agent: Mutt/1.4.1i

On Thu, Jul 10, 2003 at 02:33:09PM -0500, Brian Ford wrote:
>Could Corinna, or someone else knowledgeable, help me clear up some
>issues with respect to development under 1.5.0?  If I should just
>wait for the (forth coming?) posting to cygwin-apps, just say so.
>Thanks.

If you want to use 1.5.0, the safest thing to do is recompile everything
with the current headers and libraries.  Anything which uses off_t, uid_t,
gid_t, blkcnt_t, dev_t, or ino_t is affected.  This obviously includes
structures such as 'struct stat' which use these types.

IMO, this falls into the better safe than sorry rule.  Things should work
fine with old headers and old libraries.  If you want to move to the
new system, it is safer to rebuild everything.

Obviously, once you move to 1.5.0, you won't be able to go back, but
that's not really any different than most cygwin releases.

cgf

--
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/