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:from:subject:reply-to:references:to:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=hUo/WhzScM36zmpY
	+Hc+rvCYsPBBcq/d9G9N/KrEm5x3jwi6S2XBxJ3MPMP7Ic805F5VP2oaEEf+3CWS
	16VlATsRzM9eYpKQbrWsTZR1dgCz4Oy2hP0IhHa3NgxSWgn1/WeFqtCJYQSAx7sF
	/jv8KfmwPpEefde0Aj+ZXJqJq7Q=
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:from:subject:reply-to:references:to:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=KfwMseYlsEG3Evm7QCwqRe
	QrsVE=; b=JohZyuvv9MJ6McRj6kjxnS+5orcDu6X5ugTstIpMiO5SYax2P+PLqP
	G65dg5Ig33L4WnUQvFxOIjg5pIdzCw7Nzln0m45MApENvjY6ou9ttC0w9yLIrXWh
	Vi2ks16Z48sEbazcvqp1OYKRwRZ21OjqalRerYR9xv3Yqa5JC2iCI=
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.1 required=5.0 tests=AWL,BAYES_05,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=Hx-spam-relays-external:64.59.136.138, H*RU:64.59.136.138, H*r:sk:smtp-ou, Hx-languages-length:1931
X-HELO:	smtp-out-so.shaw.ca
X-Authority-Analysis:	v=2.2 cv=cNuQihWN c=1 sm=1 tr=0 a=WqCeCkldcEjBO3QZneQsCg==:117 a=WqCeCkldcEjBO3QZneQsCg==:17 a=IkcTkHD0fZMA:10 a=mDV3o1hIAAAA:8 a=2s-GxLEdIo7POmFlcxIA:9 a=QEXdDO2ut3YA:10 a=iERKDgpyax4A:10 a=Ia2khKC2McwA:10 a=_FVE-zBwftR9WsbkzFJk:22
From:	Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Subject:	Re: difference between cygwin32 and cygwin64 mounts breaks libtool
Reply-To:	Brian DOT Inglis AT SystematicSw DOT ab DOT ca
References:	<10970996 DOT g4281J4DVJ AT linuix DOT haible DOT de> <aa662241-b0b6-ad01-694d-21388f38e59b AT gmail DOT com>
To:	cygwin AT cygwin DOT com
Message-ID:	<48f922a7-ef19-3f67-7be3-122c5ae31f40@SystematicSw.ab.ca>
Date:	Mon, 21 Nov 2016 06:40:35 -0700
User-Agent:	Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.5.0
MIME-Version:	1.0
In-Reply-To:	<aa662241-b0b6-ad01-694d-21388f38e59b@gmail.com>
X-CMAE-Envelope:	MS4wfKZjlz+U+OqNDKQeLwjvK7JK6YzrEELr7nLD4yvKyWOsLpP05m5ArZDVp7gBuvNiTJOjfyXOVhWyPj8eMFlwM9M+p1qOvbW5zLhoM8gNKWwV+YrZYVll 3+BXkfnCjUHr11H8m7PZYiOif3QMJvapORevo/e3QvDMJ67G/S3S9V+nD7C03W4HkmRdfHZferBfBg==
X-IsSubscribed:	yes

On 2016-11-20 12:01, cyg Simple wrote:
> On 11/18/2016 7:15 PM, Bruno Haible wrote:
>> When a user has installed cygwin64 and the cross-compilation environment
>> for compiling to 32-bit cygwin (i686-pc-cygwin-gcc et al.), then
>> building (with --host=i686-pc-cygwin) a package that creates a shared
>> library and a program that uses this shared library - in different
>> source directories - makes use of libtool features: The uninstalled program
>> (i.e. the program in the build tree) is a wrapper program (built by libtool)
>> that sets up PATH so that the real program should find the (uninstalled)
>> shared library before invoking the real program.
>> This works when building outside of C:\cygwin64 (for example, in
>> C:\Users\bruno), but it does not work when building inside C:\cygwin64
>> (for example, in C:\cygwin64\home = /home). In this case, the uninstalled
>> program exits with exit code 127. When this uninstalled program is run
>> in a cmd.exe window, it prints a diagnostic message that mentions which
>> shared library it could not find.
> This is a long standing collision and I don't think you'll be able to
> get it to work as you want.  You might want to discuss with libtool list.
>> Is there a way to configure the mounts of the 32-bit cygwin subsystem
>> and the mounts of the 64-bit cygwin so that this will work also in /home?
> Short answer is no.  You're best scenario might be to have differing
> /home paths and symlink the common files in one of them.  Otherwise
> you're likely to end up with PATH that is overlapping and that doesn't work.

Have you got LT_CYGPATH pointing to cygwin32 cygpath as described (or implied) in:
https://www.gnu.org/software/libtool/manual/html_node/Cygwin_002fWindows-File-Name-Conversion.html#Cygwin_002fWindows-File-Name-Conversion

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

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

- Raw text -