static libraries

2009-02-20 Thread Alexey Pushkin
Hi, why don't many mingw32-xxx packages provide static (non-dll) versions of libraries ? For example no libz.a in mingw32-zlib. No libxerces-c.a in mingw32-xerces. Static linking makes a lot of sense with mingw. Unlike MSVC, Mingw (by default) links in msvcrt.dll which is *always* present in

Re: static libraries

2009-02-20 Thread Alexey Pushkin
Michael Cronenworth wrote: Original Message Subject: static libraries From: Alexey Pushkin alexey.push...@mererand.com To: fedora-mingw@lists.fedoraproject.org Date: 02/20/2009 09:13 AM Static linking makes a lot of sense with mingw. Yes, but it should be optional

Re: static libraries

2009-02-20 Thread Alexey Pushkin
Hi, +1 for having both shared and static MinGW libraries. The main reason why they're banned from Fedora is because of security issues. On Win32 this doesn't really make any sense as there is no central package manager which can update libraries. At the moment, software developers need

Re: static libraries

2009-02-20 Thread Alexey Pushkin
Richard W.M. Jones wrote: On Fri, Feb 20, 2009 at 06:13:28PM +0300, Alexey Pushkin wrote: [...] The general Fedora policy is to package up dynamic libraries in preference to static libraries, and this is the policy we have pursued. You'll have to take up any issues with Fedora (good luck

Re: static libraries

2009-02-20 Thread Alexey Pushkin
Richard W.M. Jones wrote: On Fri, Feb 20, 2009 at 07:04:23PM +0300, Alexey Pushkin wrote: Richard W.M. Jones wrote: The general Fedora policy is to package up dynamic libraries in preference to static libraries, and this is the policy we have pursued. You'll have to take up any issues

Re: static libraries

2009-02-20 Thread Alexey Pushkin
Richard W.M. Jones wrote: Let's just recap the facts, in case there was confusion about it ... (1) The default remains to provide dynamic libraries. There's no discussion on this point, because even if I thought it was a good idea to change (which I don't), Fedora policy would prevent it.

Re: Debugging information in MinGW packages

2009-02-25 Thread Alexey Pushkin
Richard W.M. Jones wrote: On Wed, Feb 25, 2009 at 01:53:23PM +, Daniel P. Berrange wrote: Last time we tried, a cross compiled GDB crashed burned. So unless someone can demonstrate a usuable WINE/Win32 debugger that can use the gcc generated debugging info, then we should not build with

Re: Debugging information in MinGW packages

2009-02-25 Thread Alexey Pushkin
Daniel P. Berrange wrote: On Wed, Feb 25, 2009 at 05:10:45PM +, Richard W.M. Jones wrote: On Wed, Feb 25, 2009 at 01:53:23PM +, Daniel P. Berrange wrote: Last time we tried, a cross compiled GDB crashed burned. So unless someone can demonstrate a usuable WINE/Win32 debugger that can

Re: Posix support in mingw..

2009-03-07 Thread Alexey Pushkin
roy basavaraju wrote: Hi, Thanks for your valuable suggestions.. i am working an application, which needs to read user_id(uid), group_id(gid). for this i need posix headers grp.h pwd.h. So my issue is if i replace these header files with any of the gnu libraries which supports in

Re: mingw defines __MSVCRT_VERSION__

2009-03-19 Thread Alexey Pushkin
Just define __MSVCRT_VERSION__=0x0601 and that'll work for you. I never tried win2k, but on WinXP and others msvcrt.dll does have all the xxx64() functions that require __MSVCRT_VERSION__ = 0x0601 Farkas Levente wrote: hi, while we try to compile gstreamer we got and error error: storage

Re: mingw defines __MSVCRT_VERSION__

2009-03-19 Thread Alexey Pushkin
Kevin Kofler wrote: Farkas Levente wrote: may be it's not the right place to ask and would be better to move to mingw mailing list, but it's the right version? ie. the current runtime really not support __MSVCRT_VERSION__ = 0x0601? thanks. No, it's just that the default version is 0x0600