[Mingw-w64-public] libstdc++ complaining about ::scanf

2011-11-14 Thread Alen Skondro
Hi all, I'm having these errors for the latest trunk of gcc4.7. (mingw64 is latest trunk) /h/FSF/POWERTOOLS/obj-gcc/./gcc/xgcc -shared-libgcc -B/h/FSF/POWERTOOLS/obj-gcc/./gcc -nostdinc++ -L/h/FSF/POWERTOOLS/obj-gcc/i686-w64-mingw32/libstdc++-v3/src -L/h/FSF/POWERTOOLS/obj-gcc/i6 86-w64-mingw32/l

[Mingw-w64-public] compiling glew library with mingw64 32bit...

2011-10-25 Thread Alen Skondro
Hello guys, I'm trying to compile the glew library against the mingw64 library. While linking I get this errors - What library am I missing? i686-w64-mingw32-gcc -c -O2 -Wall -W -Iinclude -o src/glewinfo.o src/glewinfo.c i686-w64-mingw32-gcc -O2 -Wall -W -Iinclude -o bin/glewinfo.exe src/glewi

Re: [Mingw-w64-public] dynamic linking with libstdc++ - gcc-4.6.2 branch

2011-09-28 Thread Alen Skondro
On Wed, Sep 28, 2011 at 5:24 PM, Ruben Van Boxem wrote: > 2011/9/28 Alen Skondro > >> >> >> On Wed, Sep 28, 2011 at 12:44 AM, JonY wrote: >> >>> On 9/28/2011 05:44, Alen Skondro wrote: >>> > Hello, >>> > >>> > I have

Re: [Mingw-w64-public] dynamic linking with libstdc++ - gcc-4.6.2 branch

2011-09-28 Thread Alen Skondro
On Wed, Sep 28, 2011 at 12:44 AM, JonY wrote: > On 9/28/2011 05:44, Alen Skondro wrote: > > Hello, > > > > I have issues with linking dynamically with libstdc++. > > Static linking works. > > > > gcc is configured with ../gcc/configure --disable-multilib

[Mingw-w64-public] dynamic linking with libstdc++ - gcc-4.6.2 branch

2011-09-27 Thread Alen Skondro
Hello, I have issues with linking dynamically with libstdc++. Static linking works. gcc is configured with ../gcc/configure --disable-multilib --prefix=/d/pwgcc-native --disable-nls --target=i686-w64-mingw32 --host=i686-w64-mingw32 --enable-languages=c,c++,lto --enable-fully-dynamic-strings libs

Re: [Mingw-w64-public] strange error when including windows.h with gcc 4.6.2

2011-08-08 Thread Alen Skondro
On Mon, Aug 1, 2011 at 11:54 PM, Alen Skondro wrote: > possible break for me is r4279. > > > On Mon, Aug 1, 2011 at 11:45 PM, Alen Skondro wrote: > >> Hello guys, >> >> I have this strange error. It didn't happen a month ago. >> >> In file in

Re: [Mingw-w64-public] strange error when including windows.h with gcc 4.6.2

2011-08-01 Thread Alen Skondro
possible break for me is r4279. On Mon, Aug 1, 2011 at 11:45 PM, Alen Skondro wrote: > Hello guys, > > I have this strange error. It didn't happen a month ago. > > In file included from > d:\pwgcc-native\bin\../lib/gcc/i686-w64-mingw32/4.6.2/../../../../i686-w64-mingw32/

[Mingw-w64-public] strange error when including windows.h with gcc 4.6.2

2011-08-01 Thread Alen Skondro
Hello guys, I have this strange error. It didn't happen a month ago. In file included from d:\pwgcc-native\bin\../lib/gcc/i686-w64-mingw32/4.6.2/../../../../i686-w64-mingw32/include/objbase.h:151:0, from d:\pwgcc-native\bin\../lib/gcc/i686-w64-mingw32/4.6.2/../../../../i686-w64-m

Re: [Mingw-w64-public] gcc 4.6 cross with multilib enabled

2011-07-08 Thread Alen Skondro
bfd/ > > Kai > > 2011/7/8 JonY : > > On 7/8/2011 13:26, Kai Tietz wrote: > >> 2011/7/8 JonY : > >>> On 7/8/2011 04:56, Alen Skondro wrote: > >>>> Hello, > >>>> > >>>> I'm stuck again. > >>>> >

[Mingw-w64-public] gcc 4.6 cross with multilib enabled

2011-07-07 Thread Alen Skondro
Hello, I'm stuck again. After successfully building gcc 4.6 targeting only i686-w64-mingw32 I'm getting errors while creating a cross compiler for multilib target (i686-w64-mingw32 + x86_64-w64-mingw32). binutils is configure like this: = $../binutils/configure --target=i686

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

2011-07-07 Thread Alen Skondro
On Thu, Jul 7, 2011 at 3:20 AM, JonY wrote: > On 7/7/2011 02:49, Alen Skondro wrote: > > > > I recompiled binutils again and set the bin dir "d:/pwgcc/bin" to PATH. > > > > now I get this error in ./i686-w64-mingw32/libgcc: > > > > ... > &

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

2011-07-06 Thread Alen Skondro
On Wed, Jul 6, 2011 at 3:35 PM, JonY wrote: > 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. > > > > > >

[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] _monstartup missing gcc 4.6

2011-04-04 Thread Alen Skondro
y workaround :) thanks again! > > >> >> >> Regards, >> >> Kai >> >> >> >> 2011/4/4 Alen Skondro askon...@gmail.com>: >> >> > On Mon, Apr 4, 2011 at 9:31 PM, Kai Tietz ktiet...@googlemail.com> >> > wrote: >> >>

[Mingw-w64-public] _monstartup missing gcc 4.6

2011-04-04 Thread Alen Skondro
Hello, I've built my own gcc toolchain (4.6.1) targeting i686-w64-mingw32 and so far everything worked fine until I decided to use the profile functionality. When compiling with -p -pg, linker reports undefined references to _monstartup. I looked in ming64 CRT and found out that _monstartup is de