From: cyg Simple <cygsimple@gmail.com>
To: cygwin@cygwin.com
Subject: Re: difference between cygwin32 and cygwin64 mounts breaks libtool
Date: Mon, 21 Nov 2016 08:26:00 -0000 [thread overview]
Message-ID: <aa662241-b0b6-ad01-694d-21388f38e59b@gmail.com> (raw)
In-Reply-To: <10970996.g4281J4DVJ@linuix.haible.de>
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
next prev parent reply other threads:[~2016-11-20 19:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-19 1:48 Bruno Haible
2016-11-21 8:26 ` cyg Simple [this message]
2016-11-21 16:57 ` Brian Inglis
2016-11-24 3:33 ` Bruno Haible
2016-11-24 10:47 ` Brian Inglis
2016-11-24 15:09 ` Brian Inglis
2016-11-24 16:25 ` Brian Inglis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aa662241-b0b6-ad01-694d-21388f38e59b@gmail.com \
--to=cygsimple@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).