Re: [AOLSERVER] Any demand for AOLserver 3.4.2 for Win32?
I'll try to get one going, I'm finishing up a class on C++ that uses MS VC++ and I might be able to apply that knowledge to the Win32 build especially when it comes to getting those %*#Q$! extra modules like nscgi and nsssl built. For AOLserver 4.x, can anyone please try out building it with the current Cygwin? Kris -- Kriston Rehberg America Online, Inc.
Re: [AOLSERVER] Any demand for AOLserver 3.4.2 for Win32?
On 2001.12.18, Kriston Rehberg [EMAIL PROTECTED] wrote: I'll try to get one going, I'm finishing up a class on C++ that uses MS VC++ and I might be able to apply that knowledge to the Win32 build especially when it comes to getting those %*#Q$! extra modules like nscgi and nsssl built. Heh. nscgi builds under Win32, it just doesn't actually execute CGI's. At least, on my Win98 SE setup here, trying to execute a simple .bat CGI hung the box hard and required a reset-switch warm boot. Thread problems, I'm guessing. (Probably needs to use CreateProcess() or ShellExecuteEx() under Win32 ...) For AOLserver 4.x, can anyone please try out building it with the current Cygwin? Did that already. No joy. Perhaps Larry's comment may solve the problem though: On 2001.12.18, Larry W. Virden [EMAIL PROTECTED] wrote: Note that I believe that Tcl itself doesn't compile using the Cygwin compiler - you need the Mingw32 compiler with the flag saying that you want it to run under Cygwin I think - details are over in comp.lang.tcl I guess I'll have to install Mingw32 and try it out. However, I still ask: won't the performance loss of running under Cygwin make running AOLserver under Cygwin unattractive? -- Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70)
Re: [AOLSERVER] Any demand for AOLserver 3.4.2 for Win32?
Was the decision to drop Win32 support on AOLServer 4.0 a political one or a technical one? It seems as though there are some demand for Win32 support and as AOLServer gains momentum, why limit its reach by not supporting Win32 systems? (not trying to rant) -Original Message- From: AOLserver Discussion [mailto:[EMAIL PROTECTED]]On Behalf Of Dossy Sent: Tuesday, December 18, 2001 7:17 AM To: [EMAIL PROTECTED] Subject: Re: [AOLSERVER] Any demand for AOLserver 3.4.2 for Win32? On 2001.12.18, Kriston Rehberg [EMAIL PROTECTED] wrote: I'll try to get one going, I'm finishing up a class on C++ that uses MS VC++ and I might be able to apply that knowledge to the Win32 build especially when it comes to getting those %*#Q$! extra modules like nscgi and nsssl built. Heh. nscgi builds under Win32, it just doesn't actually execute CGI's. At least, on my Win98 SE setup here, trying to execute a simple .bat CGI hung the box hard and required a reset-switch warm boot. Thread problems, I'm guessing. (Probably needs to use CreateProcess() or ShellExecuteEx() under Win32 ...) For AOLserver 4.x, can anyone please try out building it with the current Cygwin? Did that already. No joy. Perhaps Larry's comment may solve the problem though: On 2001.12.18, Larry W. Virden [EMAIL PROTECTED] wrote: Note that I believe that Tcl itself doesn't compile using the Cygwin compiler - you need the Mingw32 compiler with the flag saying that you want it to run under Cygwin I think - details are over in comp.lang.tcl I guess I'll have to install Mingw32 and try it out. However, I still ask: won't the performance loss of running under Cygwin make running AOLserver under Cygwin unattractive? -- Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70)
Re: [AOLSERVER] Any demand for AOLserver 3.4.2 for Win32?
Cygwin has limited support for Posix threads. You can check the Cygwin FAQ at http://cygwin.com/faq/faq.html to see which functions are missing. Several of the functions that AOLserver 4.x uses aren't in the DLL yet, making any port at this time difficult. In response to Dossy's question, I don't think many people run production servers under Cygwin. My guess is that most Windows AOLserver users are trying to duplicate a part of their site on their laptop, or they want to experiment with OpenACS without installing Linux, etc. For that sort of non-production application, the overhead introduced by Cygwin isn't a concern. I believe the Visual Studio project files for AOLserver 3.4 have some problems. (Incorrect paths to files, bad settings for debugging, etc.) That may be why some people are reluctant to build the core from source even if they have all of the tools and want to build modules. You could perhaps zip up the lib files in a separate download for those people? Of course, I ended up having to build from source anyway to incorporate some of the ADP patches that are on SourceForge. I've been using a patched version of 4b1 on Windows 2000, and the nscgi module is working for me. I checked it out of the AOLserver repository with -D 2001-11-04. My personal experience has been that 4b1 is as stable on Win2k as 3.4 is. Building the source is a pain, but I have notes that I will share if you are willing to attempt it. My work was related to an OpenACS 4 installation, so some of the patches aren't strictly necessary just to get AOLserver running. I think the nscgi in http://acs-misc.sourceforge.net/ns_rel_beta2.html works as well, if you can't / don't want to build from source. Jamie At 11:01 PM 12/17/2001 -0500, Dossy wrote: On 2001.12.17, Tom Poindexter [EMAIL PROTECTED] wrote: Perhaps a few modules too, postgres and nsodbc for starters. I'll leave that as an exercise to the reader, at least initially. If it is as simple as 'configure; make' with Cygwin, then knowing that would be helpful too. No, it isn't. Perhaps in 4.0 when Win32 support is dropped I might consider a porting effort to make 4.0 run under Cygwin, but IMHO the overhead of Cygwin just makes the idea so unattractive. Do people seriously run production servers under Cygwin? *shudder* On 2001.12.17, Ramin Naimi [EMAIL PROTECTED] wrote: Since you asked, I installed the 3.4.2 version (win32) and found there were a number of binaries missing (such as nscgi.dll). Also, is there a new ASxx-win32-install which includes the source, in particular the VC workspace and projects? You mean 3.4, not 3.4.2 version -- there IS no binary distribution of 3.4.2. Yes, nscgi.dll was missing because nscgi under Win32 in AOLserver 3.4 seems to be completely broken (at least for the very, very cursory testing I did). I felt it wasn't worth including if it wasn't working for even the most simplest CGI tests. On 2001.12.17, Wojciech Kocjan [EMAIL PROTECTED] wrote: Maybe you should also put a distro with .lib files for easier module recompilation :) Why bloat the binary distribution with unnecessary files? If you're going to compile modules, then you've got a compiler. Then, just build AOLserver from source. Why should I bother packaging up the .lib files, then? The binary install should only have enough in it for people who are only running a binary install. If you're going to compile from source, then just compile everything from source. I once tried compiling nshello with MSVC++ and gave up... Sorry to hear that. -- Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70)
Re: [AOLSERVER] Any demand for AOLserver 3.4.2 for Win32?
It was a technical one. Making it win32-capable added a lot of code noise and Jim D. asked the group at one of the chat sessions if there was any reason not to drop win32 support, at least for 4.x. He wanted to focus on cleaning up and improving the codebase and not spend a even more time on win32 portability issues, especially with regards to threading. /s. Was the decision to drop Win32 support on AOLServer 4.0 a political one or a technical one? Was the decision to drop Win32 support on AOLServer 4.0 a political one or a technical one? It seems as though there are some demand for Win32 support and as AOLServer gains momentum, why limit its reach by not supporting Win32 systems? (not trying to rant) -Original Message- From: AOLserver Discussion [mailto:[EMAIL PROTECTED]]On Behalf Of Dossy Sent: Tuesday, December 18, 2001 7:17 AM To: [EMAIL PROTECTED] Subject: Re: [AOLSERVER] Any demand for AOLserver 3.4.2 for Win32? On 2001.12.18, Kriston Rehberg [EMAIL PROTECTED] wrote: I'll try to get one going, I'm finishing up a class on C++ that uses MS VC++ and I might be able to apply that knowledge to the Win32 build especially when it comes to getting those %*#Q$! extra modules like nscgi and nsssl built. Heh. nscgi builds under Win32, it just doesn't actually execute CGI's. At least, on my Win98 SE setup here, trying to execute a simple .bat CGI hung the box hard and required a reset-switch warm boot. Thread problems, I'm guessing. (Probably needs to use CreateProcess() or ShellExecuteEx() under Win32 ...) For AOLserver 4.x, can anyone please try out building it with the current Cygwin? Did that already. No joy. Perhaps Larry's comment may solve the problem though: On 2001.12.18, Larry W. Virden [EMAIL PROTECTED] wrote: Note that I believe that Tcl itself doesn't compile using the Cygwin compiler - you need the Mingw32 compiler with the flag saying that you want it to run under Cygwin I think - details are over in comp.lang.tcl I guess I'll have to install Mingw32 and try it out. However, I still ask: won't the performance loss of running under Cygwin make running AOLserver under Cygwin unattractive? -- Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70)
