On 11/18/2016 7:15 PM, Bruno Haible wrote: > Hi, > > Short summary: > ============== > > 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. > Short question: > =============== > > 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. -- cyg Simple -- 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
