Re: [Mingw-w64-public] [wincrypt.h] Missing: MS_ENH_RSA_AES_PROV_XP

2011-07-06 Thread Ozkan Sezer
On Wed, Jul 6, 2011 at 8:48 AM, Alon Bar-Lev alon.bar...@gmail.com wrote: Oh... I can provide the exact syntax from wincrypt.h: Please don't. On Wed, Jul 6, 2011 at 12:03 AM, Ozkan Sezer seze...@gmail.com wrote: On Tue, Jul 5, 2011 at 11:41 PM, Alon Bar-Lev alon.bar...@gmail.com wrote:

Re: [Mingw-w64-public] [Mingw-users] GMP windows64 porting effort

2011-07-06 Thread Torbjorn Granlund
claimed it was there). You should have more luck with this snapshot: ftp://gmplib.org/pub/snapshot/gmp-5.0.90-20110706.tar.bz2 No asm files to be found. Good. I'm on Vista64 and I use a 64-bit compiler that was built by the mingw64 team as one of the automated builds. It's

Re: [Mingw-w64-public] [Mingw-users] GMP windows64 porting effort

2011-07-06 Thread Torbjorn Granlund
JonY jo...@users.sourceforge.net writes: GMP is misusing the --host option for detecting CPU optimization levels I don't think it is doing that. It used -O2 for all CPUs, I think. (Why not just use --with-arch=XXX?). Can anybody explain why is it doing something like that? I am not sure

Re: [Mingw-w64-public] [Mingw-users] Fwd: building gcc

2011-07-06 Thread Bj Raz
On Tue, Jul 5, 2011 at 1:37 PM, JonY jo...@users.sourceforge.net wrote: On 7/6/2011 01:25, Bj Raz wrote: No, I'm on linux, building an environment that will make a another envronment that I will use on Windows. In that case, try strace to see why it isn't starting. I thought you don't

Re: [Mingw-w64-public] [Mingw-users] GMP windows64 porting effort

2011-07-06 Thread JonY
On 7/6/2011 14:45, Torbjorn Granlund wrote: JonY writes: GMP is misusing the --host option for detecting CPU optimization levels I don't think it is doing that. It used -O2 for all CPUs, I think. I mean for ASM codes, adding -O2 implicitly isn't an issue. (Why not just use

Re: [Mingw-w64-public] [Mingw-users] Fwd: building gcc

2011-07-06 Thread JonY
On 7/6/2011 16:57, Bj Raz wrote: I'm not building with glibc, I'm using msvc in my build. So I can compiler Windows '.exe's' on linux. Which regardless of the ranlib error the c compiler works fine when I use it. though I'd prefer not having the ranlib error. Cause when I start to try and

Re: [Mingw-w64-public] [Mingw-users] GMP windows64 porting effort

2011-07-06 Thread Sisyphus
- Original Message - From: Torbjorn Granlund Oops, one patch had been omitted (although the change log claimed it was there). You should have more luck with this snapshot: ftp://gmplib.org/pub/snapshot/gmp-5.0.90-20110706.tar.bz2 Yes, that's better - all tests pass. Here's

Re: [Mingw-w64-public] [Mingw-users] GMP windows64 porting effort

2011-07-06 Thread Ruben Van Boxem
2011/7/6 Sisyphus sisyph...@optusnet.com.au: - Original Message - From: Torbjorn Granlund Oops, one patch had been omitted (although the change log claimed it was there).  You should have more luck with this snapshot:      ftp://gmplib.org/pub/snapshot/gmp-5.0.90-20110706.tar.bz2

[Mingw-w64-public] building cross gcc 4.6 for target i686-w64-mingw32

2011-07-06 Thread Alen Skondro
I'm having problems creating a cross compiler (host=i686-pc-mingw32 --target=i686-w64-mingw32) I use the mingw console on windows. The following error occures while building ./i686-w64-mingw32/libgcc (config.log): configure:3039: $? = 1 configure:3055: /d/DATA/FSF/POWERTOOLS/obj-gcc/./gcc/xgcc

Re: [Mingw-w64-public] building cross gcc 4.6 for target i686-w64-mingw32

2011-07-06 Thread JonY
On 7/6/2011 21:02, Alen Skondro wrote: I'm having problems creating a cross compiler (host=i686-pc-mingw32 --target=i686-w64-mingw32) I use the mingw console on windows. The following error occures while building ./i686-w64-mingw32/libgcc (config.log): configure:3039: $? = 1

[Mingw-w64-public] GCC 4.6.2 (prerelease) rubenvb Personal Build, now with Clang addon!

2011-07-06 Thread Ruben Van Boxem
Hi, I have just finished my first GCC 4.6.2 (prerelease) personal build. I have a lot of exciting new things this time, so please, keep reading: - GCC 4.6.1 has been released, so gcc -v now reports 4.6.2 (prerelease), hence the version bump in my packages - I have updated to the newest