Op 15 mrt. 2012 03:31 schreef K. Frank kfrank2...@gmail.com het
volgende:
Hello Jim and Kai and Ruben and Friends!
I see something similar to Jim's bug in tr1/random, but
not in random.
On Wed, Mar 14, 2012 at 2:22 AM, Jim Michaels jmich...@yahoo.com wrote:
/*
Author: Jim Michaels
...
It works correctly, because sizeof(int) == 4 and 1250
is too big for 32 bits. If you take the least significant four bytes
of that value, you get (what a surprise) exactly 445948416.
The three vars are expanded from short to int and multiplicated
(still into an int), then the result is
hey
in my quest of stack tracing, i'm trying another program which depends
on libbfd. But errr duting the link: undefined symbols
libintl_dgettext. using 'find', i can't see any *intl* file in my
mingw-w64 'tree'.
Vincent
Hi Vincent,
yes libintl.a isn't installed by binutils. You need to compile it and
install it manually. That libbfd is present isn't even intended from
our side, but binutils installs it automagically. You might be able
to avoid the dependency to libintl.a by disabling nls-support AFAIR
(but I
Using i686-w64-mingw32-gcc-4.7.0-3_rubenvb.7z to build from the
http://luajit.org/luajit.html repo I get a lua51.dll with a dependency on
libwinpthread-1.dll. Specifically, the lua51.dll imports the pthread_key_create
and pthread_getspecific symbols.
I don't get the libwinpthread dependency
Hi Jon,
2012/3/15 Jon jon.for...@gmail.com:
Using i686-w64-mingw32-gcc-4.7.0-3_rubenvb.7z to build from the
http://luajit.org/luajit.html repo I get a lua51.dll with a dependency on
libwinpthread-1.dll. Specifically, the lua51.dll imports the
pthread_key_create and pthread_getspecific
Using i686-w64-mingw32-gcc-4.7.0-3_rubenvb.7z to build from the
http://luajit.org/luajit.html repo I get a lua51.dll with a dependency on
libwinpthread-1.dll. Specifically, the lua51.dll imports the
pthread_key_create and pthread_getspecific symbols.
I don't get the libwinpthread
g++.exe: error: CreateProcess: No such file or directory
I always get this error when compiling programs using
c:\mingw-w32-bin_i686-mingw_2027\mingw\bin\g++.exe
to compile my programs.
up to now, I have been using
c:\mingw-w32-bin_i686-mingw_2027\bin\i686-w64-mingw32-g++.exe
I suppose
2012/3/16 Kai Tietz ktiet...@googlemail.com:
Yes, you are actual build a cross-compiler from i686-pc-mingw32 to
i686-w64-mingw32. It is a cross, as triplets are different!
2. building binutils:
--target=i686-w64-mingw32
--enable-targets=x86_64-w64-mingw32,i686-w64-mingw32
^^
I know how to submit a bug report for gcc (that would be easy), but I know
nothing about a gcc mailing list.
From: JonY jo...@users.sourceforge.net
To: mingw-w64-public@lists.sourceforge.net
Sent: Thursday, March 15, 2012 2:01 AM
Subject: Re:
10 matches
Mail list logo