Does anyone build statically linked xsubs on MSWin32?
I have found three problems with the Makefile.aperl created by MakeMaker 4.48:
1. $Config::Config{libperl} is not used to set macros so macros which
should be defined perl56.lib end up being defined libperl.lib.
2. MAP_STATIC (and some other stuff having to do with extralibs) is
expanded on the Command line so that when using ActiveState perl the
command line gets too big, and NMAKE.EXE bombs.
3. perlmain.c will not compile using M$ Visual C++.
4. Many extralibs.ld do not exist (and are most likely of no use anyway)
but MakeMaker makes the link dependent on them as if there needs to be an
extralibs.ld for every *.lib found.
Could it be that no one builds statically linked xsubs on MSWin32 because a
perl built with libc.lib and without the /MD switch is brain damaged? Or is
it that a perl built with libc.lib and without the /MD switch brain damaged
because no one is interested in statically linked xsubs on MSWin32?
The answer to this is very important to me.
Thanks
Richard Kandarian
http://www.lanl.gov/cgi-bin/fonelink.pl/085598
Any opinions stated in this message are mine and not expressed on behalf of
any other individual or entity unless explicitly noted otherwise. As for
the links at the very end, my opinion is that they are interesting.
UNIX is software. M$ Windows is hardware implemented in software.
When M$ says 'embrace and extend', what does that bring to mind?
A huge boa constrictor?
Save the world from M$ tyranny - embrace and extend LINUX before M$ does.
http://www.fourmilab.to/documents/top10.html
http://www.prospect.org/print/V11/16/ackerman-b.html
http://www.theatlantic.com/issues/2000/12/fallows.htm
