>>7
Try to type something original instead of your mall informed and retarded copy pastas.
Deployment of C software requires especially complicated system of Make, ./configure, Autoconf, Automake and M4 macros (in addition to C preprocessor), with numerous other external tools, like perl, flex and yacc, generating "probes" against compilation environment.
This is retarded. Flex (lexical analyzer) and yacc (parser generator) are for creating compilers. It hasn't anything to do with deployment.
You don't have to use make, configure, automake, m4 and other tools for "deployment". You can choose other tools, which are easier to use.
C code and tools produce programs that are inaccessible to outside world and cannot be inspected during runtime. Once compiled C programs are static, difficult access and upgrade and have horrible ABI, through #include files, instead of robust module system, like the symbol package system of Common Lisp.
This is also crap. You can monitor almost everything in a C program. You only need to include the symbols for debugging.
And there is no ABI, because C is used as system programming language, thus accessing a variety of features of completely different kernels, with their own calling conventions, memory addressing etc. It doesn't make sense to say a pointer has to be 32 bits on all systems. It doesn't even make sense to say a pointer points to a memory address.