Hi Ray,
Thanks. Meanwhile, the build was finished OK. It's a very nice build script.
Beside the MSYS2/gcc paths, these issues took some time to figure out,
maybe could be added to the README:
1 The develop branch should be checked out to get the gcc-4.9.1 script.
(checking out non master is not
On Thu, Oct 2, 2014 at 10:59 PM, Yaron Keren wrote:
> Well, something went wrong with MSYS2. I uninstalled MSYS2 and reinstalled,
> now libmangle compiles and build goes on. Odd. I did encounter a problem
> before with MSYS2 while doing pacman -Syu, there were errors and the upgrade
> wasn't compl
Well, something went wrong with MSYS2. I uninstalled MSYS2 and reinstalled,
now libmangle compiles and build goes on. Odd. I did encounter a problem
before with MSYS2 while doing pacman -Syu, there were errors and the
upgrade wasn't complete. Maybe that's releated. This time I did not pacman
-Syu.
Hi,
I am trying to build mingw-w64. I followed all steps from the README and
git clone https://github.com/niXman/mingw-builds/ --branch develop
./build --mode=gcc-4.9.1 --buildroot=/c/mingw491 --rt-version=v3 --rev=1
--bootstrap --jobs=2 --threads=posix --exceptions=dwarf --arch=i686
--bin-compr
On 10/2/2014 20:45, Dongsheng Song wrote:
> The daily build report errors on the commit:
>
> /home/cauchy/cross/i686-windows-gcc-4.9/i686-w64-mingw32/include/winbase.h:999:
> multiple definition of `InterlockedIncrement64'
> /home/cauchy/obj/i686-w64-mingw32-gcc-4.9/gcc/./gcc/crtbegin.o:cygming-cr
The daily build report errors on the commit:
/home/cauchy/cross/i686-windows-gcc-4.9/i686-w64-mingw32/include/winbase.h:999:
multiple definition of `InterlockedIncrement64'
/home/cauchy/obj/i686-w64-mingw32-gcc-4.9/gcc/./gcc/crtbegin.o:cygming-crtbegin.c:(.text+0x200):
first defined here
emutls_s.
JonY 2014-10-02 02:11:
> On 9/28/2014 14:44, lh_mouse wrote:
>> mingw-w64-libraries/winpthread/src/spinlock.c:66
>> int initrv = pthread_spin_init (lock,
>> PTHREAD_PROCESS_PRIVATE);
>>
>> There is no corresponding pthread_spin_destroy() for this lock, hence
>> its memory leaks.
>>
>
