Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <00c301c2552a$4b0c4d40$0100a8c0@wdg.uk.ibm.com> From: "Max Bowsher" To: "Harig, Mark A." , References: Subject: Re: Calling all sed wizards! Need a little help with possible fix: Subtle permissions bug in interaction between Makefiles & libtool (Cygwin-specific) Date: Thu, 5 Sep 2002 23:18:02 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Harig, Mark A. wrote: >> >> Max Bowsher wrote: >>> I've located an awkward bug in the interaction between common-sense >>> Makefile rules and Cygwin libtool. >>> >>> The package I was building at the time was libiconv, but the issue >>> is common to any autoconf-libtool build system. >>> >>> The libiconv.la file is installed as data (i.e. 644) - which is >>> correct. However the Cygwin specific postinstall_cmds in libtool use >>> the same install command to install the DLL. This results in the DLL >>> being installed without execute permission (on ntsec systems), and >>> causes "The application failed to initialize properly (0xc0000022)." >>> errors from dependent exes. >>> > > Is there a reason not to create a patch that would fix the > problem in the source of the postinstall_cmds? The source of the postinstall_cmds is a human. Patching them can be difficult :-). Max. -- 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/