On Mon, Nov 14, 2011 at 4:47 PM, Dave Love <[email protected]> wrote: > Anyhow, as I understand it, it won't work with Cygwin -- I think there > will be something about it in the old list archive.
The first publicly (at least to the SGE dev list) known Cygwin port was done at the beginning of 2003 by a guy call Ian Chesal, who used to work for Altera Toronto (I know a few guys there, but I have not met Ian in person). I contacted Ian privately in 2003, and he told me that Grid Engine worked with a few minor issues. I think most of the q* commands worked in his port. Then Andy said that the license of Cygwin is not too compatible with Sun's internal license standard, and he told us that the SFU port was in the works, and basically that effort was stalled since then. Related note: A quick Google "Ian Chesal Altera" and found this: http://www.cyclecomputing.com/news/news/166-newhires > I guess it should be possible to port to Cygwin and have > it behave similarly to Unix-like systems. I just finished the Cygwin port from where I left off. I got everything except authuser, qmon, qmake compiled & linked. The basic commands (eg. loadcheck & checkuser) work, qmaster fails to start because my windows hostname resolution is messed up. I think I've spent more time of googling Windows host name resolution info & debugging process, AND rebooting than getting Grid Engine compiled under Cygwin. :-( > I'd guess the issues would be with a shared filesystem and > whatever interactions are necessary with the native system for account > management etc. which may or may not be readily accessible via Cygwin. >From time to time we have Grid Engine users who mention that they have SGE submission side commands compiled under Cygwin. I think the bigger issues are on the execution side. I also worked on porting SGE onto Windows natively a few months ago until I needed to place it on the back burner because I had other more important and/or interesting things to work on. Philippe, if you can wait for a few more days, I will clean up my Cygwin changes and release them (and see if Dave is interested in getting some of those into his fork). I will see if we can get the native porting effort going soon. > It might be that effort for a Cygwin port would be best used adopting > GNU autotools for the build, which should give Cygwin support > more-or-less for free, but that's quite a lot of work. Yup, autotools would be great, but it is quite a lot of work for nothing (feature-wise). >> I believe that Windows 7 is problematic > > Do you have any details? > >> but XP is possible. Not tried >> either. AIUI Univa are working on a native Windows port of the Grid >> Engine execd > > What does that mean? Just not using whatever the POSIX layer is > currently called? I am on Win7, I think Cygwin itself has no problem handling Win7. Most/All commands just run on Cygwin, and Cygwin handles the Windows version differences for us. Rayson >> as part of their commercial offering. > ^^^^^^^^^^ > proprietary > _______________________________________________ > SGE-discuss mailing list > [email protected] > https://arc.liv.ac.uk/mailman/listinfo/sge-discuss > _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
