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
Hi Daniel,
On Sun, 06 Oct 2013 10:50:41 -0700, Daniel Goldman wrote:
> > I haven't tried them, but those packages should be usable with a
> > mingw-w64 cross-compiler by unpacking them into your sysroot-prefix
> > (e.g. /usr/x86_64-w64-mingw32/sys-root/mingw/).
>
> 1) I don't find /usr/x86_64
-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:
Thank you and Alexey for help. Two questions for anyone:
> I haven't tried them, but those packages should be usable with a
> mingw-w64 cross-compiler by unpacking them into your sysroot-prefix
> (e.g. /usr/x86_64-w64-mingw32/sys-root/mingw/).
1) I don't find /usr/x86_64-w64-mingw32/sys-root/m
On 10/6/2013 21:18, K. Frank wrote:
>Program received signal SIGSEGV, Segmentation fault.
>0x6cf36a5c in strtoflt128 () from .\mingw64\bin\libquadmath-0.dll
>
> (This is running on 64-bit windows 7.)
Only when debug symbols are missing, strtoflt128 is probably the last
symbol seen
Hello Rob and Jon Y!
I see the same thing.
On Sun, Oct 6, 2013 at 9:00 AM, JonY wrote:
> On 10/6/2013 20:31, sisyph...@optusnet.com.au wrote:
>> Hi,
>>
>> Here's the simple demo:
>>
>> /***
>> #include
>>
>> int main (void) {
>> __float128 r;
>> r = expq(2.0Q);
>>
On 10/6/2013 20:31, sisyph...@optusnet.com.au wrote:
> Hi,
>
> Here's the simple demo:
>
> /***
> #include
>
> int main (void) {
> __float128 r;
> r = expq(2.0Q);
> return 0;
> }
>
> ***/
>
> With recent MinGW64 ports of gcc, that program
Hi,
Here's the simple demo:
/***
#include
int main (void) {
__float128 r;
r = expq(2.0Q);
return 0;
}
***/
With recent MinGW64 ports of gcc, that program builds ok, but running it
results in a crash.
Seems to happen with 4.6.3, 4.7.0 and
10 matches
Mail list logo