Re: difference between cygwin32 and cygwin64 mounts breaks libtool

[Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>]

On 2016-11-23 10:09, Bruno Haible wrote:
> Brian Inglis wrote in https://cygwin.com/ml/cygwin/2016-11/msg00259.html:
>> Have you got LT_CYGPATH pointing to cygwin32 cygpath
> Thanks for the suggestion, but alas:
> - There is no cygwin32 cygpath in
> /usr/i686-pc-cygwin/sys-root/usr/bin.
> - Letting LT_CYGPATH point to /usr/bin/cygpath.exe or
> C:\cygwin64\usr\bin\cygpath.exe does not change the symptom or fix
> the problem.

If you want to run 32 bit code, you need to install cygwin32 in a
different directory e.g. c:/cygwin32/ and point LT_CYGPATH to
/proc/cygdrive/c/cygwin32/bin/cygpath. That is how you can use
cygwin32 cygwin1.dll, and access its 32 bit mount table, which was
part of your original question, and run 32 bit builds.

As the libtool docs explain, Cygwin64 cygpath is used to produce
the canonical Windows file name, then that is converted with
Cygwin32 cygpath to a POSIX filename in that environment.
You can not just magically run Cygwin32 code under Cygwin64
without the cygwin32 runtime dll(s) linked to the WoW dlls.

You could also run a straight build in that cygwin32 environment
without cross-compilation, using the same cygport build file as
64 bit. You are using cygport to simplify your Cygwin builds,
right?

In Linux environments, cygwin32 has to be installed under Wine,
and everything adapted to run Cygwin32 code under Wine, as
explained in the libtool docs mentioned:
https://www.gnu.org/software/libtool/manual/html_node/Cygwin_002fWindows-File-Name-Conversion.html#Cygwin_002fWindows-File-Name-Conversion
The alternative the docs say is to move the binaries to a
Cygwin32 environment for testing.

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