X-Recipient: archive-cygwin@delorie.com
X-SWARE-Spam-Status: No, hits=-3.2 required=5.0 	tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: sourceware.org
Message-ID: <4A3C8A55.20104@cwilson.fastmail.fm>
Date: Sat, 20 Jun 2009 03:05:57 -0400
From: Charles Wilson <cygwin@cwilson.fastmail.fm>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.21) Gecko/20090302 Thunderbird/2.0.0.21 Mnenhy/0.7.6.666
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: UAC .manifest files
References: <4A25FA67.4050805@users.sourceforge.net> <20090603081102.GI23519@calimero.vinschen.de> <h074af$kjd$1@ger.gmane.org> <20090604082551.GB29270@calimero.vinschen.de> <20090604113038.GF21472@trikaliotis.net> <4A27C9DA.5020609@cwilson.fastmail.fm> <4A27E612.2030400@users.sourceforge.net> <4A27F23C.50508@gmail.com> <4A3A63C5.1030403@users.sourceforge.net> <4A3A8401.2050309@users.sourceforge.net> <4A3A8819.9030505@lysator.liu.se> <4A3A940E.4020206@users.sourceforge.net> <4A3C8682.1010208@lysator.liu.se>
In-Reply-To: <4A3C8682.1010208@lysator.liu.se>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

Peter Rosin wrote:
> ltwrappers are just replacing the old wrappers AFAIK, and those are
> indeed needed by the MSVC patches, so that premise has already changed.
> 
> If you can't be bothered to cooperate with those patches then I can
> switch to arguing that cccl (wrapper for MSVC) is supported by libtool.
> When you use cccl with a contemporary MSVC, MSVC will create the
> manifest for you. You should not overwrite the manifest generated
> by MSVC in that case.
> 
> So again, please special case this to only be active for gcc (and
> whatever else needs it).

Peter: I don't know why you're arguing with Yaakov; you really should be
talking to me.  I've already said I want to take this to the libtool
list and discuss it there, and you can be sure it won't go into
*libtool-master* until everybody is happy. I just wanted to make sure
the patch worked and didn't break any of the tests (Bzzt.  bad
formatting failed sh.test) before I posted it, on Yaakov's behalf, for
discussion on libtool-patches.

Now, today's cygwin-only libtool release did include Yaakov's patch, but
only for this reason: we're coming up on the cygwin-1.7 release and I
know that Yaakov has about 1500 packages to rebuild in the very near
future.  Anything to make that easier...  Plus, because I've decided to
start pushing again -- hard -- to get my existing patches into
libtool-master, I *know* I'll be rolling a new libtool release fairly
soon.  So, today's -4/-13 packages will have a pretty short shelf life.
If they cause a problem for you, don't use them... -3/-12 aren't going
anywhere, and you'll probably like -5/-14 better.

As an aside, it's a little ridiculous to badger Yaakov, or anybody else,
about cooperating with out-of-tree patches.  Now, it's not your fault
that they are still out of tree. Frankly, I have no idea why they
weren't merged months ago (same as certain OTHER patches I could
mention). But until they are merged, and MSVC is fully supported...well,
you know the score.

--
Chuck

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

