Anonymous Monk has asked for the wisdom of the Perl Monks concerning the following question:

Dear Monks,
I work as a Perl programmer for about half a year (never studied, just served an apprenticeship) and it's my task to learn about Perl XS at present. I worked through example 4 on the perlxstut, step by step, but executing Makefile.PL gives me the error
Invalid CODE attribute: postamble at ./Makefile.PL line 44 BEGIN failed--compilation aborted at ./Makefile.PL line 49.
The Makefile code looks like this:
#!/usr/bin/perl use 5.008008; use ExtUtils::MakeMaker; # See lib/ExtUtils/MakeMaker.pm for details of how to influence # the contents of the Makefile that is written. WriteMakefile( NAME => 'Mytest2', VERSION_FROM => 'Mytest2.pm', # finds $VERSION PREREQ_PM => {}, # e.g., Module::Name => 1.1 ($] >= 5.005 ? ## Add these new keywords supported since 5.005 (ABSTRACT_FROM => 'lib/Mytest2.pm', # retrieve abstract from mo +dule AUTHOR => 'A. U. Thor <a.u.thor@a.galaxy.far.far.away>' +) : ()), LIBS => [''], # e.g., '-lm' DEFINE => '', # e.g., '-DHAVE_SOMETHING' INC => '-I.', # e.g., '-I. -I/usr/include/other' MYEXTLIB => 'mylib/libmylib$(LIB_EXT)', # Un-comment this if you add C files to link with later: # OBJECT => '$(O_FILES)', # link all the C files too ); if (eval {require ExtUtils::Constant; 1}) { # If you edit these definitions to change the constants used by this + module, # you will need to use the generated const-c.inc and const-xs.inc # files to replace their "fallback" counterparts before distributing + your # changes. my @names = (qw(TESTVAL)); ExtUtils::Constant::WriteConstants( NAME => 'Mytest2', NAMES => \@names, DEFAULT_TYPE => 'IV', C_FILE => 'const-c.inc', XS_FILE => 'const-xs.inc', ); } else { use File::Copy; use File::Spec; foreach my $file ('const-c.inc', 'const-xs.inc') { my $fallback = File::Spec->catfile('fallback', $file); copy ($fallback, $file) or die "Can't copy $fallback to $file: $!" +; } } sub MY:postamble { ' $(MYEXTLIB): mylib/Makefile cd mylib && $(MAKE) $(PASSTHRU) '; }
I don't get the problem and why he doesn't seem to like 'postamble'. Since I can't believe this is an error in the perldoc, I will be happy if someone tells me what I'm doing wrong.
Thanks in advance,

Michaela

Replies are listed 'Best First'.
Re: perlxstut - what am I doing wrong?
by ForgotPasswordAgain (Vicar) on Dec 10, 2007 at 11:16 UTC
    MY::postamble with two colons. And perldoc attributes for the meaning of the error.
      Thank you! In the german translation I read, the curly brackets were missing, so I got an "Invalid separator character" error.
      Everything's working fine now :)