Re^2: Name conflict between MinGW C++ standard library header and Perl development header

And the *other* thing you could try is to wait for better advice ;-)

Naw, I like this advice. I almost posted something similar, because I have also found that it is sometimes useful to #undef away a macro conflict in these situations. It's a good suggestion (unless it doesn't work). I hesitated in posting the thought because I figured someone would have a better idea. ;)

Dave

Comment on Re^2: Name conflict between MinGW C++ standard library header and Perl development header Download Code

Replies are listed 'Best First'.
Re^3: Name conflict between MinGW C++ standard library header and Perl development header by syphilis (Archbishop) on Nov 11, 2014 at 07:24 UTC
Is the idea of loading the genoeye headers before loading the perl headers likely to be helpful ? It certainly breaks the conventional way of doing things (and I don't think I've ever tried it), but it's probably the safest solution ...... if it works. Cheers, Rob	[reply]
Re^4: Name conflict between MinGW C++ standard library header and Perl development header by llancet (Friar) on Nov 11, 2014 at 10:37 UTC
Death and dirty hack are unavoidable:)	[reply]