Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com Date: Wed, 13 Jun 2001 12:17:30 -0400 From: Christopher Faylor To: cygwin-apps AT cygwin DOT com Subject: Re: ask for delivering cygwin 1.1.8 with kde 1.1.2 Message-ID: <20010613121730.B7791@redhat.com> Reply-To: cygwin-apps AT cygwin DOT com Mail-Followup-To: cygwin-apps AT cygwin DOT com References: <000901c0f3f4$413954e0$6e032bb7 AT BRAMSCHE> <011801c0f3f8$7f2034f0$0200a8c0 AT lifelesswks> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <011801c0f3f8$7f2034f0$0200a8c0@lifelesswks>; from robert.collins@itdomain.com.au on Wed, Jun 13, 2001 at 09:03:36PM +1000 On Wed, Jun 13, 2001 at 09:03:36PM +1000, Robert Collins wrote: >>2. applications or linbs linked with cygwin 1.3.2 like ncurses >>reference a pointer "check_for_executable" used by the method >>path_conv::exec_state(). This isn't available under cygwin 1.1.8. So >>if one application or lib is linked with cygwin 1.3.2 it will never >>runs under cygwin 1.1.8. Especially in deep nested applications like >>kde this wilkl produced much support problems. >> >>It is not possible to put this var into the structure pointed by the >>impure_ptr (or somewhere else) to prevent such incompatibility ? > >It's only incompatible if you are running a compiled-on-cygwin-1.3.2 >binary on a cygwin-1.1.8 system. That's like running a glibc 2.2 >compiled binary ona glibc 2.1 system. There's no reason to expect that >to work. Personally I don't think that the cygwin list should have to >compile ncurses for 1.1.8, once 1.3.2 is released. Remember: backwards >compatability means running old binaries still works with newer >Cygwin's, not newer binaries work on old cygwin's. Still if the cause >of that symbols use can be hidden, I see no problem with you providing >a patch. The check_for_executable global is actually not used in 1.3.2. This was a 1.3.1 thing. It should eventually disappear. There is no need for a patch. cgf