Re: Fwd: Re: [patch]: Decouple cygwin building from in-tree mingw/w32api building

2012-10-24 Thread Corinna Vinschen
On Oct 23 17:48, Christopher Faylor wrote: On Tue, Oct 23, 2012 at 09:50:10PM +0100, Keith Marshall wrote: And just like Earnie's, the response he requested from me also bounced. Forwarded copy below: Original Message Subject: Re: [patch]: Decouple cygwin building from

Re: [patch]: Decouple cygwin building from in-tree mingw/w32api building

2012-10-24 Thread Yaakov (Cygwin/X)
On Mon, 2012-10-22 at 14:23 +0200, Corinna Vinschen wrote: If the original patch with the aforementioned changes is ok with everybody, I'd apply it asap and remove lsaauth/cyglsa64.dll, lsaauth/make-64bit-version-with-mingw-w64.sh, and utils/mingw. Revised patches for winsup/cygwin and

Re: [patch]: Decouple cygwin building from in-tree mingw/w32api building

2012-10-24 Thread Corinna Vinschen
On Oct 24 04:30, Yaakov (Cygwin/X) wrote: On Mon, 2012-10-22 at 14:23 +0200, Corinna Vinschen wrote: If the original patch with the aforementioned changes is ok with everybody, I'd apply it asap and remove lsaauth/cyglsa64.dll, lsaauth/make-64bit-version-with-mingw-w64.sh, and utils/mingw.

Re: [patch]: Decouple cygwin building from in-tree mingw/w32api building

2012-10-24 Thread Corinna Vinschen
On Oct 24 11:50, Corinna Vinschen wrote: On Oct 24 04:30, Yaakov (Cygwin/X) wrote: On Mon, 2012-10-22 at 14:23 +0200, Corinna Vinschen wrote: If the original patch with the aforementioned changes is ok with everybody, I'd apply it asap and remove lsaauth/cyglsa64.dll,

Re: [patch]: Decouple cygwin building from in-tree mingw/w32api building

2012-10-24 Thread Yaakov (Cygwin/X)
On Wed, 2012-10-24 at 12:01 +0200, Corinna Vinschen wrote: Checking in toplevel patches requires global checkin rights. I can apply the toplevel patch when you applied the rest. Other than that, toplevel patches also have to be kept aligned with the gcc repo. I'll make sure to inform

Re: [patch]: Decouple cygwin building from in-tree mingw/w32api building

2012-10-22 Thread Christopher Faylor
On Mon, Oct 22, 2012 at 10:29:13AM +0200, Corinna Vinschen wrote: On Oct 22 00:09, Christopher Faylor wrote: Yeah, since the changes to the configury separate Cygwin from mingw and w32api, staying in src/winsup is no problem at all. I always thought mingw is part of the src tree for gcc bootstrap

Re: [patch]: Decouple cygwin building from in-tree mingw/w32api building

2012-10-22 Thread Corinna Vinschen
Hi Yaakov, On Oct 21 16:39, Yaakov (Cygwin/X) wrote: On Fri, 2012-10-19 at 11:33 -0500, Yaakov (Cygwin/X) wrote: I'll include those changes and post a new patch then. Revised patches for toplevel, winsup, winsup/cygwin, winsup/lsaauth, and winsup/utils attached. Tested on Cygwin and F17

Re: [patch]: Decouple cygwin building from in-tree mingw/w32api building

2012-10-21 Thread Corinna Vinschen
On Oct 19 20:46, Corinna Vinschen wrote: On Oct 19 11:33, Yaakov (Cygwin/X) wrote: On Fri, 2012-10-19 at 11:21 +0200, Corinna Vinschen wrote: Other than that, I think it's good to go in after the 1.7.17 release. I'll try to do the release at some point between now and Monday. I'll

Re: [patch]: Decouple cygwin building from in-tree mingw/w32api building

2012-10-21 Thread Yaakov (Cygwin/X)
On Sun, 2012-10-21 at 13:33 +0200, Corinna Vinschen wrote: On second thought... considering that w32api is now Mingw64 based, and considering that building Cygwin with this Mingw64 built w32api works fine... what do you guys think about a once and for all approach? Is it really necessary to

Re: [patch]: Decouple cygwin building from in-tree mingw/w32api building

2012-10-21 Thread Christopher Faylor
On Sun, Oct 21, 2012 at 01:33:20PM +0200, Corinna Vinschen wrote: On Oct 19 20:46, Corinna Vinschen wrote: On Oct 19 11:33, Yaakov (Cygwin/X) wrote: On Fri, 2012-10-19 at 11:21 +0200, Corinna Vinschen wrote: Other than that, I think it's good to go in after the 1.7.17 release. I'll try to do the

Re: [patch]: Decouple cygwin building from in-tree mingw/w32api building

2012-10-21 Thread Christopher Faylor
On Sun, Oct 21, 2012 at 01:32:41PM -0500, Yaakov (Cygwin/X) wrote: On Sun, 2012-10-21 at 13:10 -0400, Christopher Faylor wrote: That said, is it time to ask the mingw.org stuff to relocate their CVS repo? I could tar up the affected CVS directories for them if so. What about some CVSROOT/modules

Re: [patch]: Decouple cygwin building from in-tree mingw/w32api building

2012-10-19 Thread Corinna Vinschen
On Oct 18 12:20, Yaakov (Cygwin/X) wrote: On Thu, 2012-10-18 at 10:34 +0200, Corinna Vinschen wrote: Any problem to move mingw64-i686-zlib into the distro? None; should I also move the other setup.exe prerequisites for i686-w64-mingw32? Would you also like x86_64 versions of any of those?

Re: [patch]: Decouple cygwin building from in-tree mingw/w32api building

2012-10-19 Thread Corinna Vinschen
On Oct 19 11:21, Corinna Vinschen wrote: Thanks. Looks good, I have problems with this patch. That should have been: Thanks. Looks good, I just have a few small problems with this patch. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project

Re: [patch]: Decouple cygwin building from in-tree mingw/w32api building

2012-10-19 Thread Yaakov (Cygwin/X)
On Fri, 2012-10-19 at 11:21 +0200, Corinna Vinschen wrote: On Oct 18 12:20, Yaakov (Cygwin/X) wrote: None; should I also move the other setup.exe prerequisites for i686-w64-mingw32? Would you also like x86_64 versions of any of those? If it's not asked too much, sure on both accounts!

Re: [patch]: Decouple cygwin building from in-tree mingw/w32api building

2012-10-18 Thread Corinna Vinschen
Hi Yaakov, On Oct 18 02:33, Yaakov (Cygwin/X) wrote: On Wed, 2012-10-17 at 15:32 -0400, Christopher Faylor wrote: But, anyway, nevermind. This shouldn't be a requirement for getting these changes checked in. I'm more concerned with just nuking the now-unneeded mingw script. Draft

Re: [patch]: Decouple cygwin building from in-tree mingw/w32api building

2012-10-18 Thread Kai Tietz
Hi Corinna, 2012/10/18 Corinna Vinschen: Hi Yaakov, On Oct 18 02:33, Yaakov (Cygwin/X) wrote: On Wed, 2012-10-17 at 15:32 -0400, Christopher Faylor wrote: But, anyway, nevermind. This shouldn't be a requirement for getting these changes checked in. I'm more concerned with just nuking the

Re: [patch]: Decouple cygwin building from in-tree mingw/w32api building

2012-10-18 Thread Corinna Vinschen
On Oct 18 17:57, Kai Tietz wrote: Hi Corinna, 2012/10/18 Corinna Vinschen: Hi Yaakov, On Oct 18 02:33, Yaakov (Cygwin/X) wrote: On Wed, 2012-10-17 at 15:32 -0400, Christopher Faylor wrote: But, anyway, nevermind. This shouldn't be a requirement for getting these changes checked

Re: [patch]: Decouple cygwin building from in-tree mingw/w32api building

2012-10-18 Thread Yaakov (Cygwin/X)
On Thu, 2012-10-18 at 10:34 +0200, Corinna Vinschen wrote: Any problem to move mingw64-i686-zlib into the distro? None; should I also move the other setup.exe prerequisites for i686-w64-mingw32? Would you also like x86_64 versions of any of those? The idea of the branch is to collect all

[patch]: Decouple cygwin building from in-tree mingw/w32api building

2012-10-17 Thread Kai Tietz
Hello everybody, This patch modifies the bits of build-process so that cygwin and mingw building is decoupled from each other. Additionally the patch decouples cygwin's build from the w32api of mingw.org. By this change it is now possible to build cygwin (and utilities) with mingw.org's and

Re: [patch]: Decouple cygwin building from in-tree mingw/w32api building

2012-10-17 Thread Corinna Vinschen
Hi Kai, On Oct 17 18:13, Kai Tietz wrote: Hello everybody, This patch modifies the bits of build-process so that cygwin and mingw building is decoupled from each other. Additionally the patch decouples cygwin's build from the w32api of mingw.org. By this change it is now possible to build

Re: [patch]: Decouple cygwin building from in-tree mingw/w32api building

2012-10-17 Thread Corinna Vinschen
On Oct 17 12:44, Christopher Faylor wrote: On Wed, Oct 17, 2012 at 06:13:18PM +0200, Kai Tietz wrote: -[ $dir = '/' ] dir='' +[ $dir = '/' ] dir=''; No need for a semicolon here. I have other comments but I wonder if it would just be best to scrap this script and assume that there is a