Re: [Mingw-w64-public] Where's make (specifically, x86_64-w64-mingw32-make.exe)?

2011-03-25 Thread Paul Leder
On 25/03/2011 02:32, Suresh Govindachar wrote: > Hello, > > Inside mingw-w64-1.0-bin_i686-mingw_20110318.zip, I was expecting to find > "x86_64-w64-mingw32-make.exe" but there isn't any such file. What can one > use for make? Use the host system (Linux/whatever) make. You don't need a cross-make

Re: [Mingw-w64-public] __FUNCTION__ macro

2011-03-22 Thread Paul Leder
On 22/03/2011 11:46, Тихомиров Валентин wrote: > The convenient tracing construction > #define LOG(LogTypeString,format,...) printf("%s[" __FUNCTION__ "] > "format, LogTypeString, __VA_ARGS__) > fails with error: expected ')' before '__FUNCTION__' > Is it ok? It's not a macro; it just looks like o

[Mingw-w64-public] Strategies for dealing with Unix-style files on Windows

2011-03-20 Thread Paul Leder
I'd like to handle Unix-style as well as DOS-style line endings on the MinGW version of my code. Does anyone have any thoughts on this? The problem is that I'd prefer to open input files in text mode. When your open a NL-only file in text mode, however, fpos/fseek don't work on the file. If you

Re: [Mingw-w64-public] [Mingw-users] Conflicting libstdc++-6.dll requirements, and licensing

2011-03-16 Thread Paul Leder
On 16/03/2011 20:37, Chris Wilson wrote: > In general it's not possible to mix objects compiled with different C++ > compilers in the same executable. Usually this is due to the lack of ABI > standardisation, resulting in each compiler using a different ABI. That > may not be the case here, but th

Re: [Mingw-w64-public] [Mingw-users] Conflicting libstdc++-6.dll requirements, and licensing

2011-03-14 Thread Paul Leder
On 11/03/2011 13:17, Earnie wrote: > An ugly workaround to the real problem is to put program A in a > directory with its libstdc++-6.dll and put program B in another > directory with its libstdc++-6.dll and then add the directories to PATH. This doesn't work, although I don't yet understand why.

Re: [Mingw-w64-public] Debugger limitations?

2011-02-11 Thread Paul Leder
Executable is 32-bit, and Cygwin/gdb is 32-bit. The gdb is the current version from Cygwin, which is 6.8.0. The Cygwin gcc is 3.4.4. I compiled with a Linux binary distribution which I downloaded last week (I don't have access to that machine at the moment, but the gcc version is ~4.5.2). Sou

[Mingw-w64-public] Debugger limitations?

2011-02-10 Thread Paul Leder
Should I expect any problems when running gdb/insight on Cygwin, debugging cross-compiled binaries? I'm cross-compiling on Linux (-g -O0), and copying the binaries to Cygwin, together with the same source tree that I used on Linux. When I run insight on Cygwin, the initial window displays only

Re: [Mingw-w64-public] Cross-compile with autoconf

2011-02-10 Thread Paul Leder
Thanks Vincent/Jon - I got it working with just --host. -Paul -- The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 25

[Mingw-w64-public] Cross-compile with autoconf

2011-02-08 Thread Paul Leder
Sorry if this is slightly off-topic - I'm trying to build a standard Linux autoconf project for Windows using mingw-w32-1.0-bin_i686-linux. Does anyone happen to know what 'configure' invocation I should use for this? Are '--build' and '--host' sufficient, or do I have to point at local include