Re: mods for compiling perl && perl common packages

[epeschko at den-mdev1 (Ed Peschko)]

> > Second, there are a couple of code snippets which don't seem to compile in
> > the File Security module, listed below.  The symbols seem to be defined in 
> > the winnt.h file in the VC++ distribution; how WinNT-savvy is GCC for EGCS?
> > Is it safe to use the definitions in the winnt.h file for compiling with GCC?
> 
> Ed, you're better off taking this discussion to gnu-win32 mailing list
> where most of the active contributors to this project hang out. MS's
> headers are full of MS extensions some of which GCC doesn't support and
> that causes some severe problems. There is work underway to add this

Well, not to be arbitrarily contrary, but why take the discussion of this list? 

I mean, you yourself say that it causes 'severe problems' - and one of my hopes 
for compiling perl w/GCC was to take microsoft out of the loop. And as you
say, most of the active contributors are on this list, so they are the ones
who would be able to fix the problem.

If I can't take M$ out of the loop with GCC on perl - which is primarily a 
unix tool with win32 ambitions - then what chance will it have against other 
applications originally written on win32?

So what VC++ extensions does gcc w/ecgs have problems with? And what work is 
being done to support them? And if I so happen to not be able to compile an
extension with GCC, can I mix and match VC++ libraries and GCC libraries?

Ed