X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:references
	:reply-to:mime-version:content-type:content-transfer-encoding
	:in-reply-to; q=dns; s=default; b=VvyBQXk5mi/TqxgxicaxP2dLU4Ce0m
	jfm8YlXerQOSaL0waiXnXEER0rzYxfL3jsBmbMRGv9sBDwXjC7BzHE7yRei7yUzK
	0zqnKwJEJIDEWbmENeYR29L3TWzxwjNuDBUhjQW7E2KHnd52kyrGGUbaF74bLGOO
	LiOMHBn9dOcXI=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:date:message-id:references
	:reply-to:mime-version:content-type:content-transfer-encoding
	:in-reply-to; s=default; bh=7q1YZioGwkhLwSODUTY9qcVTKok=; b=RXzt
	EPbhlqfXiUHMMozg3ChQzTZa/1QxFndjvzhhqHUy7pONVSoozdNQcf4+O6GqzhfT
	Rb9I98I3EpXjAmJoQv1TtcKXLnSFaOVNO+iZ3oc4f0Ko90hAYOweXGAhNnpsZlBu
	ow+68oZLhC5/GZTZb0ff/ATqO/jcN4azDsE8bZg=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=0.7 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,FSL_HELO_BARE_IP_2,RCVD_IN_DNSWL_LOW,RCVD_NUMERIC_HELO,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=no version=3.3.2 spammy=Hx-languages-length:752, Fwd, H*f:sk:3c5c59d, H*i:sk:3c5c59d
X-HELO: plane.gmane.org
To: cygwin AT cygwin DOT com
From: =?UTF-8?Q?Ren=c3=a9_Berber?= <rene DOT berber AT gmail DOT com>
Subject: Re: Fwd: Re: Help debugging a dll issue
Date: Sat, 21 May 2016 22:56:21 -0500
Lines: 20
Message-ID: <nhralq$rmj$1@ger.gmane.org>
References: <1781b970-23ef-8e8b-ccbb-0e63d09eef2e AT cs DOT umass DOT edu> <3c5c59da-a72e-b756-6395-f134e6f34614 AT cs DOT umass DOT edu>
Reply-To: Do not reply <rene DOT berber AT gmail DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.19) Gecko/20081209 Lightning/0.9 Thunderbird/2.0.0.19 Mnenhy/0.7.6.0
In-Reply-To: <3c5c59da-a72e-b756-6395-f134e6f34614@cs.umass.edu>
X-IsSubscribed: yes

On 5/21/2016 10:15 PM, Eliot Moss wrote:

[snip]
>> You surely tried this already: strip --strip-unneeded or --strip-debug?
> 
> A helpful thought, but no, it did not occur to me.  Getting pypy to run
> that extra step in the middle of its build would involve hacking its
> process
> of generating a Makefile, while it already had __declspec handling for the
> Windows native build case, so it made sense to me to go that way for this
> application -- but I'll file that away for future use!

It wouldn't work, by the time you run strip the library is already
created with the wrong information... only if it happens to strip all
the bad symbols, very unlikely, it would apparently work.

Regards.
-- 
René Berber



--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple