Re: [Mingw-w64-public] linking error: "*x* referenced in section `.text' of [...]: defined in discarded section `.text' of [...]"

On 7/5/12, Rune K. Svendsen wrote: > Hi list! > > I'm trying to build the Streamer part of the PeerStreamer open source > project (http://peerstreamer.org) using the gcc-mingw-w64 package on > Ubuntu 12.04 (gcc version 4.6.3). The building process goes fine. Some > warnings, but I think that's to

[Mingw-w64-public] undefined reference to `_Unwind_RaiseException' while building luajit

Hello, I'm on 64-bit Windows 7. I tried to build luajit using 2 compilers: Windows 7 SDK and MinGW GCC 4.7.2 (prerelease 20120702). Windows 7 SDK worked fine. But MinGW GCC 4.7.2 crashed: "CClib_debug.o" "CClib_jit.o" "CClib_ffi.o" "CClib_init.o" "DYNLINK lua51.dl

Re: [Mingw-w64-public] linking error: "*x* referenced in section `.text' of [...]: defined in discarded section `.text' of [...]"

On 07/06/2012 12:06 AM, JonY wrote: > On 7/6/2012 04:16, Rune K. Svendsen wrote: >> Hi list! >> >> I'm trying to build the Streamer part of the PeerStreamer open source >> project (http://peerstreamer.org) using the gcc-mingw-w64 package on >> Ubuntu 12.04 (gcc version 4.6.3). The building process

Re: [Mingw-w64-public] linking error: "*x* referenced in section `.text' of [...]: defined in discarded section `.text' of [...]"

On 7/6/2012 04:16, Rune K. Svendsen wrote: > Hi list! > > I'm trying to build the Streamer part of the PeerStreamer open source > project (http://peerstreamer.org) using the gcc-mingw-w64 package on > Ubuntu 12.04 (gcc version 4.6.3). The building process goes fine. Some > warnings, but I think

[Mingw-w64-public] linking error: "*x* referenced in section `.text' of [...]: defined in discarded section `.text' of [...]"

Hi list! I'm trying to build the Streamer part of the PeerStreamer open source project (http://peerstreamer.org) using the gcc-mingw-w64 package on Ubuntu 12.04 (gcc version 4.6.3). The building process goes fine. Some warnings, but I think that's to expect. When it gets to the final step of s

Re: [Mingw-w64-public] [PATCH] Move asprintf and vasprintf into libmingwex.a instead of being inline funcions in stdio.h

2012/7/5 Ray Donnelly : > Playing devil's advocate here... given that: > > libmingwex.a is only linked if someone passes > -D__USE_MINGW_ANSI_STDIO=1 and that > msvcrt doesn't implement asprintf or vasprintf, > > could we not just say that anyone who expects ms formatting in this > scenario is just

Re: [Mingw-w64-public] [PATCH] Move asprintf and vasprintf into libmingwex.a instead of being inline funcions in stdio.h

Playing devil's advocate here... given that: libmingwex.a is only linked if someone passes -D__USE_MINGW_ANSI_STDIO=1 and that msvcrt doesn't implement asprintf or vasprintf, could we not just say that anyone who expects ms formatting in this scenario is just mistaken? - and they'd get warnings f

Re: [Mingw-w64-public] [PATCH] Move asprintf and vasprintf into libmingwex.a instead of being inline funcions in stdio.h

2012/7/5 Ray Donnelly : > Thanks Kai, > > You decided against renaming __mingw_vasprintf to vasprintf (and same > for asprintf) then? > > Cheers, > > Ray. Yes, the issue is that __mingw_vasprintf assumes POSIX-formatter style. This could lead to troubles for ventures checking for vasprintf/asprin

Re: [Mingw-w64-public] [PATCH] Move asprintf and vasprintf into libmingwex.a instead of being inline funcions in stdio.h

Thanks Kai, You decided against renaming __mingw_vasprintf to vasprintf (and same for asprintf) then? Cheers, Ray. On Thu, Jul 5, 2012 at 12:59 PM, Kai Tietz wrote: > Hi, > > I disabled the stub-implemenation of asprintf and vasprintf. By this > gdb's build failure should be fixed and we avoi

Re: [Mingw-w64-public] [PATCH] Move asprintf and vasprintf into libmingwex.a instead of being inline funcions in stdio.h

Hi, I disabled the stub-implemenation of asprintf and vasprintf. By this gdb's build failure should be fixed and we avoid the MS-formatter vs. POSIX-formatter issue. Each venture either needs to implement its own variant, or it can still use the __mingw_vasprintf variant. Cheers, Kai -

Re: [Mingw-w64-public] Strange behavior of snwprintf() function

2012/7/4 xunxun: Thank you for reply. > Maybe someone can explain it here. Maybe... -- Regards, niXman ___ Dual-target(32 & 64 bit) MinGW compilers for 32 and 64 bit Windows: http://sourceforge.net/projects/mingwbuilds/ ---