Front page | perl.perl5.porters |
Postings from January 2008
On 30/01/2008, Jan Dubois <jand@activestate.com> wrote: > On Wed, 30 Jan 2008, Robert May wrote: > > > > Further research turns up the '-mms-bitfields' option for (mingw > > only?) gcc, which causes it to use the same alignment as Microsoft's > > compilers. I can confirm that using this option at least fixes my > > immediate problem[1]. It might be a better option for 5.10.x to patch > > ActivePerl::Config to add this flag? I'll generate a patch and attach > > it to the ActiveState Bug report for this item. > > Awesome. Yes, this is much better than having to hack op.h to > conditionally add filler bytes. So, in the meantime, can anyone suggest a mechanism for testing whether the perl that is running my Makefile.PL was compiled with a Microsoft compiler, given that if gcc is being used the Config.pm values will already have been re-set (with ExtUtils::FakeConfig, ActivePerl::Config, or similar). I can't just blindly add -mms-bitfields' if the compiler is gcc, as that would break compatibility with gcc-built perls (Strawberry perl ...), and I don't only want to find ActiveState Perl builds - and I need it to work back to 5.6.1 Or am I stuck with putting a big warning in the README (which won't stop the bug reports). Thanks for any insight. Rob.Thread Previous | Thread Next