Main Stories
Slash Boxes

Slash Open Source Project

Slashcode Log In

Log In

[ Create a new account ]

Article Poll

Poll I found this article to be
Very Helpful
Not Helpful
Not Very Helpful
[ Results | Polls ]
Comments:0 | Votes:5

That horse is not quite dead yet... Slash on Windows

posted by Krow on 02:26 PM February 3rd, 2003   Printer-friendly   Email story
I've been asked to look into CMS's and discussion forum systems for my company, and naturally my favorite website came to mind. When I looked into the documentation and the older posts here, I realized it would not be quite as simple as I hoped to set up a proof-of-concept system, as I'm limited to Win2K as a server OS.

Luckily, I found one post that claimed to have managed it. I followed the documentation by Geo detailing how to install Apache, MySQL, and mod_perl, and all went well. Of course, almost every Perl module listed has been upgraded since the writing, and many of the versions Geo used are no longer available, but I decided to make a go of it anyway.

While I'm new to installing Slash, I know my way around the various Windows platforms and Perl, and I was pretty sure I would be able to handle it. Of course, I misjudged my own abilities, and I get stuck at an unmentioned step - nmake test / nmake install for slash. I get some interesting errors, listed below... would anyone have any ideas as to how to proceed (moving away from Windows is not an option - stow the flamethrowers)?

F:\VisualStudio\VC98\include\malloc.h(106) : error C2059: syntax error : '('
F:\VisualStudio\VC98\include\malloc.h(107) : error C2059: syntax error : '('
F:\VisualStudio\VC98\include\malloc.h(108) : error C2059: syntax error : '('
E:/Perl/site/lib/auto/Apache/include/include\os.h( 149) : warning C4005: 'lstat' : macro redefinition
E:\Perl\lib\CORE\XSUB.h(313) : see previous definition of 'lstat'
F:\VisualStudio\VC98\include\signal.h(102) : error C2059: syntax error : '('
NMAKE : fatal error U1077: 'C:\WINNT\system32\cmd.exe' : return code '0x2' Stop.
NMAKE : fatal error U1077: 'C:\WINNT\system32\cmd.exe' : return code '0x2' Stop.
NMAKE : fatal error U1077: 'C:\WINNT\system32\cmd.exe' : return code '0x2' Stop.
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login
Loading... please wait.
  • I'm limited to Win2K as a server OS.

    Statements like this trouble me. It's been a long time since I've had to deal with such OS bigotry directly. But maybe, given that I don't know how deep and thorough this 'limitation' is, there's a way around it...

    Why not run Linux inside VMWare on your 2000 box? (We used to do this in the opposite direction when we had Windows exclusively based apps that needed to be put on the Internet and I wasn't brave enough to put a Windows box directly on the Internet.) The last time I checked Suse and a few other distributions were available from VMWare [] pre-installed into a virtual machine.

    As for the errors you're getting, it looks like your C compiler can't even parse it's own header files. Very sad really. You might want to find a mailing list that deals with Micro$sloth's compiler to see if someone has a trick for coaxing it into sanity. (And you paid extra on top of your OS for the privilege of using such a compiler!)

    • Keep in mind that their are companies where you have to deal with policies that limit what you are allowed to run (for good or bad...).

      You can't grep a dead tree.
      • I understand that in a removed way. It's just so far from the reality I've dealt with for a while that it's very hard not to mock it. I tried to tone down that aspect of the post, but I probably could have been gentler.

        This guys problems are just so reminescent of trying to port apps to strange broken commercial UNIX's with exorbitantly expensive tools and support. Xenix's lack of proper signal handling and TI UNIX's lack of sockets come to mind quite easily over a decade later. Xenix's compiler barfed on its own includes. This led to rewriting those we used so that progress could inch forward. It became clear quite quickly that those who couldn't read the writing on the wall and recognize the insanity of trying to make modern tcp/ip apps function reliably on these boxes were doomed to an uphill climb that might never end.

        The whole "you must use this one tool and nothing else" philosophy is utterly laughable when you consider it in slightly different contexts. I've never heard a construction foreman say "no power tools". If he did you can bet the guys would sneak in before he showed up and use them for as long as they could to get things done in a sane amount of time. Of course, this is why Linux (or BSD) gets into many orgs through the back door. Or in a virtual machine....