Re: [netlabs #596] .XS build process needs to be more portable

[Aldo Calpini]

Jeffrey Goff (via RT) wrote:
 I've just patched lib/Parrot/Makefile.PL to check for a Win32 platform,
 and if so, use .obj for the default object extension. However I did it
 simply by checking $^O for 'Win'. This is probably not as portable as it
 could be, but a quick look through ExtUtils::MakeMaker didn't reveal a
 variable that could be used for determining the proper extension.

I guess this is not portable, in fact. the Cygwin build under Win32 uses
.o extension as Unix does. but this seems to give a reasonable answer:

# perl -MConfig -e print $Config{_o};
.obj


cheers,
Aldo

__END__
$_=q,just perl,,s, , another ,,s,$, hacker,,print;

[netlabs #596] .XS build process needs to be more portable

[via RT]

# New Ticket Created by  Jeffrey Goff 
# Please include the string:  [netlabs #596]
# in the subject line of all future correspondence about this issue. 
# URL: http://bugs6.perl.org/rt2/Ticket/Display.html?id=596 


I've just patched lib/Parrot/Makefile.PL to check for a Win32 platform,
and if so, use .obj for the default object extension. However I did it
simply by checking $^O for 'Win'. This is probably not as portable as it
could be, but a quick look through ExtUtils::MakeMaker didn't reveal a
variable that could be used for determining the proper extension.

The possible problem in lib/Parrot/PakFile2.xs is slightly different,
and is a 5.6.1 issue. Modifying Perl_croak(foo) to Perl_croak(aTHX_
foo) works on both UNIX and Win32, but I'm not sure if that's the
correct approach, and if we're simply tickling a bug in the appropriate
Win32 build. This isn't a major bug, it just needs to be looked at by
someone with more experience in this area than I have.
--
Jeff [EMAIL PROTECTED]