-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07.10.2013 05:29, Daniel Goldman wrote:
> LRN - Thanks for the help. Things are working better now.
>
> "echo | [] -E -v -" (ran from windows xp "command window")
> did help (some
> portions shown):
>
> Target: i686-w64-mingw32
> Configured with
Op 7-okt.-2013 03:30 schreef "Daniel Goldman" :
>
> LRN - Thanks for the help. Things are working better now.
>
> "echo | [] -E -v -" (ran from windows xp "command
window") did help (some
> portions shown):
>
> Target: i686-w64-mingw32
> Configured with: ../../../src/gcc-4.8.1/configure --host=i686
LRN - Thanks for the help. Things are working better now.
"echo | [] -E -v -" (ran from windows xp "command window") did
help (some
portions shown):
Target: i686-w64-mingw32
Configured with: ../../../src/gcc-4.8.1/configure --host=i686-w64-mingw32
--build=i686-w64-mingw32 --target=i686-w64-min
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06.10.2013 22:39, Daniel Goldman wrote:
> Context - I posted previously about compiling (or cross-compiling) a C curses
> program.
>
> I'm confused by the mingw-w64 directory structure and names. It seems well
> thought and
> organized, probably
Context - I posted previously about compiling (or cross-compiling) a C curses
program.
I'm confused by the mingw-w64 directory structure and names. It seems well
thought and
organized, probably self-obvious to the developers. But I don't "get it" as a
user.
*** On windows xp computer:
