This is the mail archive of the
mailing list for the Cygwin project.
Re: difference between cygwin32 and cygwin64 mounts breaks libtool
- From: Brian Inglis <Brian dot Inglis at SystematicSw dot ab dot ca>
- To: cygwin at cygwin dot com
- Date: Mon, 21 Nov 2016 06:40:35 -0700
- Subject: Re: difference between cygwin32 and cygwin64 mounts breaks libtool
- Authentication-results: sourceware.org; auth=none
- References: <10970996.g4281J4DVJ@linuix.haible.de> <email@example.com>
- Reply-to: Brian dot Inglis at SystematicSw dot ab dot ca
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:
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple