Ralf Wildenhues wrote:
> | +Wine exited with a successful status
>
> Does anybody know how I can avoid this from within wine?
I don't think there's an option to disable it, but since that comes from
the winelauncher script (normally installed as /usr/bin/wine) you can
simply comment out the 'ech
Peter Rosin wrote:
> Ah, ok. That's bad. The misleading name i586-mingw32msvc-gcc caught
> me. Again. What in the world is "msvc" doing in there?
I believe this is to denote that it defaults to the MSVCRT runtime, as
opposed to the very old CRTDLL one, which the MinGW toolchain still
provides com
Ralf Wildenhues wrote:
> Oh well; if somebody digs out the auto-import semantics from the list
> archives/manuals, feel free to add a note to export.at so that the next
> person won't be confused again. (Extra score for putting it in the new
> w32 chapter. ;-)
The first issue here is that the a
Ralf Wildenhues wrote:
> I'm actually not sure whether _GLOBAL__F[ID]_.* can appear on w32.
> Do you know? They should happen with C++ code using constructors
> and destructors IIRC.
Yes they do occur, although not matching that regexp. For one, they
will have two leading underscores before the
Ralf Wildenhues wrote:
> Did GCC change since then, or is this system-dependent?
Interesting. I'd be curious to see if powerpc-ibm-aix5.3.0.0-c++filt
recognises the FI/FD encoding, and if so then it would be reasonable to
conclude that this is in fact system-dependent or otherwise an internal
im
