Having a single Wintel around pisses me off for the X''th time

No matter what I do, it seems to be impossible to *live* with Windows as a system for getting things done.


This in particular pisses me off at the moment

>cl hi.c            --- simple hello world test
Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 15.00.30729.01 for 80x86
Copyright (C) Microsoft Corporation.  All rights reserved.

hi.c
Microsoft (R) Incremental Linker Version 9.00.30729.01
Copyright (C) Microsoft Corporation.  All rights reserved.

P:\TexLive\perltl\lib,P:\TexLive\perltl\site\lib,P:/Devel/Languages/Perl/site/lib,P:/Devel/Languages/Perl/lib,.
LINK : fatal error LNK1104: cannot open file 'P:\TexLive\perltl\lib,P:\TexLive\perltl\site\lib,P:/Devel/Languages/Perl/site/lib,P:/Devel/Languages/Perl/lib,.'

No matter what abuse I subject the environment settings to, it is impossible to compile anything from the fucking command line. The directories specified appear to be a fusion of TexLive added PERL5LIB values and the "usual" for the installed Perl. Building things using the IDE and a conventional project, does not have such errors; likely because it 'replaces' nmake so to speak. Needless to say, this machine must have both Perl and TexLive installed, or I will raise more mayhem then playing DooM II:Hell Revealed on Nightmare!

This kind of error causes a bit of a problem when trying to build software that only supplies Makefiles for MSVC+nmake, rather then project files for the IDE.


I've used Microsofts operating systems since early MS-DOS and have cursed it every fucking year. I've used FreeBSD since 2006 and smile joyfully every year!



For the love of FORTRAN, why is it I can never find commercial software that I do not want to hex edit into the 8th level of DooM?




footnote: the number in the subject was meant to be python26s best estimate of 1024 ** 56725691612; so cool watching this been-nothing-but-trouble-since-year-one PC burn up resources calculating this randomly chosen number!!! Even more joy, was seeing the thing pop a MemoryError before it could conclude the operation, somehow I think this fits well; the amount of times this computer has pissed me off may as well approach ∞ for all intents and purposes.