[Bug 513819] mingw directory not visible as a wine DOS path

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=513819





--- Comment #6 from Paolo Bonzini <pbonzini at redhat.com>  2009-07-26 15:03:22 EDT ---
There are three problems:

1) when given --host, Autoconf tries to run a program to determine if you're
cross compiling.  If you have Wine installed the Windows executable are
registered with the kernel binfmt_misc module and then you're not
cross-compiling, or at least Autoconf doesn't think you are.

So glib will run the runtime tests that detect mismatches between the versions
in the include files and the actual library versions.  While I agree that
necessary runtime tests are evil, they can be useful when they are supported
because they are more precise that compile-only tests.  Indeed in my case it
detected that I was using the wrong pkg-config (bug 513825).

That's why it is ok to report this as a wine bug, also.  The bug doesn't happen
if Wine is not installed.

2) The reason GNU Smalltalk's build needs Wine is not needing runtime tests,
but rather that it needs to run itself to complete the build.  This is not
related to this bug.

> Wine's behaviour when executing programs which depend on other (cross-
> compiled) libraries is the same as would happen on real Windows environments. 
> That is: only the default paths and the current path are searched for
> libraries.

I know, but this bug applies to uninstalled binaries.  It is currently
impossible to run a quick-and-dirty glib/gtk program in Wine except by manually
adding c:\mingw\bin to the path.  (BTW, I stand corrected; adding c:\mingw\lib
is not required).

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.