[Mingw-w64-public] Sbuild update 5.0.1

2014-05-07 Thread LRN
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 S[mart|tupid] build[1] got a major update = About = sbuild is a set of scripts that build various free software packages for Windows from the source, starting with a GCC toolchain (cross-compiled) and MSYS2 core (cross-compiled), and ending with vari

Re: [Mingw-w64-public] Where is the latest msys(2) download?

2014-05-07 Thread Ray Donnelly
>>> >>> On Wed, May 7, 2014 at 9:38 PM, Alexpux wrote: >>> >>>> >>>> 07 мая 2014 г., в 22:31, Baruch Burstein >>>> написал(а): >>>> >>>> 32-bit: >>>> msys2-base-i686-20140507.tar.xz<http://s

Re: [Mingw-w64-public] Where is the latest msys(2) download?

2014-05-07 Thread Baruch Burstein
t 9:44 PM, Baruch Burstein wrote: > >> Thank you. >> >> >> On Wed, May 7, 2014 at 9:38 PM, Alexpux wrote: >> >>> >>> 07 мая 2014 г., в 22:31, Baruch Burstein >>> написал(а): >>> >>> 32-bit: >>> msys2-b

Re: [Mingw-w64-public] Where is the latest msys(2) download?

2014-05-07 Thread Alexpux
исал(а): > > 32-bit:msys2-base-i686-20140507.tar.xz > > 64-bit:msys2-base-x86_64-20140507.tar.xz > > Also you need read https://sourceforge.net/p/msys2/wiki/MSYS2%20installation/ > > Regards, > Alexey. >> &

Re: [Mingw-w64-public] Where is the latest msys(2) download?

2014-05-07 Thread Baruch Burstein
: >> >> 32-bit: >> msys2-base-i686-20140507.tar.xz<http://sourceforge.net/projects/msys2/files/Base/i686/msys2-base-i686-20140507.tar.xz/download> >> >> 64-bit: >> msys2-base-x86_64-20140507.tar.xz<http://sourceforge.net/projects/msys2/files/Ba

Re: [Mingw-w64-public] Where is the latest msys(2) download?

2014-05-07 Thread Baruch Burstein
Thank you. On Wed, May 7, 2014 at 9:38 PM, Alexpux wrote: > > 07 мая 2014 г., в 22:31, Baruch Burstein > написал(а): > > 32-bit: > msys2-base-i686-20140507.tar.xz<http://sourceforge.net/projects/msys2/files/Base/i686/msys2-base-i686-20140507.tar.xz/download> >

Re: [Mingw-w64-public] Where is the latest msys(2) download?

2014-05-07 Thread Alexpux
07 мая 2014 г., в 22:31, Baruch Burstein написал(а): 32-bit:msys2-base-i686-20140507.tar.xz 64-bit:msys2-base-x86_64-20140507.tar.xz Also you need read https://sourceforge.net/p/msys2/wiki/MSYS2%20installation/ Regards, Alexey. > > > -- > ˙uʍop-ǝpısdn sı ɹoʇıuoɯ ɹno

[Mingw-w64-public] Where is the latest msys(2) download?

2014-05-07 Thread Baruch Burstein
-- ˙uʍop-ǝpısdn sı ɹoʇıuoɯ ɹnoʎ 'sıɥʇ pɐǝɹ uɐɔ noʎ ɟı -- Is your legacy SCM system holding you back? Join Perforce May 7 to find out: • 3 signs your SCM is hindering your productivity • Requirements for releasing software

Re: [Mingw-w64-public] [PATCH] Don't use __stdcall on ARM

2014-05-07 Thread Kai Tietz
2014-05-07 14:11 GMT+02:00 Corinna Vinschen : > On May 7 00:59, Kai Tietz wrote: >> Yes, magic wording here is that compiler accepts it and ignores it. >> So it means not in headers. > > Sorry, but I don't get this. So per MSDN, x64 and ARM are identical > with respect to __stdcall. > > If so, wh

Re: [Mingw-w64-public] problems with _ftime import using non standard msv runtimes

2014-05-07 Thread Carl Kleffner
Hi, I want to bring this problem up again and want to ask for adding a patch for winpthreads. using two patches: (1) gcc/libgomp/config/mingw32/time.c diff -rupN a/gcc-4.8.2/libgomp/config/mingw32/time.c b/gcc-4.8.2/libgomp/config/mingw32/time.c --- a/gcc-4.8.2/libgomp/config/mingw32/time.c

Re: [Mingw-w64-public] Unattended install with mingw-builds-install.exe

2014-05-07 Thread niXman
Paul Henri 2014-04-29 20:48: > Hi niXman, Hi, > 1) Can you please provide the script .ci used to build > mingw-install.exe Next week I upload the project for this installer. > 2) In the current state, is that it is possible that CreateInstall > allow to > add another URL repository.txt file as

Re: [Mingw-w64-public] [PATCH] Don't use __stdcall on ARM

2014-05-07 Thread Corinna Vinschen
On May 7 00:59, Kai Tietz wrote: > Yes, magic wording here is that compiler accepts it and ignores it. > So it means not in headers. Sorry, but I don't get this. So per MSDN, x64 and ARM are identical with respect to __stdcall. If so, why is it the right thing to #define __stdcall for x64, b