[Mingw-w64-public] Recent commit

2012-10-28 Thread Алексей Павлов
Hi! After recent commit about lib32/libsapi.a I have error with building mingw-w64 from trunk: dlltool --as-flags=--32 -m i386 -k --as=as --output-lib lib32/libcabinet.a --input-def ../../mingw-sources/mingw-w64-crt/lib32/cabinet.def make[1]: *** No rule to make target `lib32/libsapi.a', needed

Re: [Mingw-w64-public] RFC: How shall we plan releases of new major versions?

2012-10-28 Thread NightStrike
On Sat, Oct 27, 2012 at 11:49 AM, Erik van Pienbroek wrote: > To sum it up I would like to propose the following: > * Publish unstable releases (from the trunk branch) periodically > (this can be time based) Are you volunteering for this? Right now, we only have one release manager. We're a s

Re: [Mingw-w64-public] RFC: How shall we plan releases of new major versions?

2012-10-28 Thread Kai Tietz
JonY, please sent patch upstream to gcc's and libstdc++'s ML. Add me CC and please mention that I ok'ed patch on IRC. I won't be able to reply next week myself. Cheers, Kai 2012/10/28 JonY : > On 10/28/2012 21:16, Kai Tietz wrote: >> 2012/10/28 Erik van Pienbroek : >>> JonY schreef op zo 28-10

Re: [Mingw-w64-public] RFC: How shall we plan releases of new major versions?

2012-10-28 Thread JonY
On 10/28/2012 21:16, Kai Tietz wrote: > 2012/10/28 Erik van Pienbroek : >> JonY schreef op zo 28-10-2012 om 19:08 [+0800]: >>> On 10/28/2012 18:33, Erik van Pienbroek wrote: JonY schreef op zo 28-10-2012 om 10:42 [+0800]: > Does that include several large C++ programs? I need to test a pat

Re: [Mingw-w64-public] RFC: How shall we plan releases of new major versions?

2012-10-28 Thread Kai Tietz
2012/10/28 Erik van Pienbroek : > JonY schreef op zo 28-10-2012 om 19:08 [+0800]: >> On 10/28/2012 18:33, Erik van Pienbroek wrote: >> > JonY schreef op zo 28-10-2012 om 10:42 [+0800]: >> >> Does that include several large C++ programs? I need to test a patch for >> >> trunk headers. >> >> >> >> If

Re: [Mingw-w64-public] RFC: How shall we plan releases of new major versions?

2012-10-28 Thread Erik van Pienbroek
JonY schreef op zo 28-10-2012 om 19:08 [+0800]: > On 10/28/2012 18:33, Erik van Pienbroek wrote: > > JonY schreef op zo 28-10-2012 om 10:42 [+0800]: > >> Does that include several large C++ programs? I need to test a patch for > >> trunk headers. > >> > >> If so, I can push in the less invasive cha

Re: [Mingw-w64-public] RFC: How shall we plan releases of new major versions?

2012-10-28 Thread JonY
On 10/28/2012 18:33, Erik van Pienbroek wrote: > JonY schreef op zo 28-10-2012 om 10:42 [+0800]: >> Does that include several large C++ programs? I need to test a patch for >> trunk headers. >> >> If so, I can push in the less invasive change and hopefully it should >> not affect any builds. > > Y

Re: [Mingw-w64-public] RFC: How shall we plan releases of new major versions?

2012-10-28 Thread Erik van Pienbroek
JonY schreef op zo 28-10-2012 om 10:42 [+0800]: > Does that include several large C++ programs? I need to test a patch for > trunk headers. > > If so, I can push in the less invasive change and hopefully it should > not affect any builds. Yes, we also provide various large C++ libraries, like for

Re: [Mingw-w64-public] RFC: How shall we plan releases of new major

2012-10-28 Thread Peter Schaefer
Am 10/27/2012 1:33 PM, Corinna Vinschen wrote: (just 2c from a mingw-w64 user) > I'm still puzzled, though, why providing source code is such a hassle, > apparently. After all, this is called open source for a reason. It's not a hassle per se, but at least a bit unexpected that just by using mi