Following your instructions I get:

./perl_libyaml.h:16:10: fatal error: yaml.h: No such file or directory
 #include <yaml.h>
          ^~~~~~~~
compilation terminated.

[download]

Which I get past by adding "INC" => "-I../LibYAML/include/", to the Makefile.PL. The tests then fail with things like:

#   Failed test 'require YAML::XS;Can't load '/home/marto/code/yaml-li
+byaml-pm/YAML-LibYAML-0.77/blib/arch/auto/YAML/XS/LibYAML/LibYAML.so'
+ for module YAML::XS::LibYAML: /home/marto/code/yaml-libyaml-pm/YAML-
+LibYAML-0.77/blib/arch/auto/YAML/XS/LibYAML/LibYAML.so: undefined sym
+bol: yaml_sequence_start_event_initialize at /usr/lib/i386-linux-gnu/
+perl/5.26/DynaLoader.pm line 187

[download]

I'll do some more digging in the morning.

In reply to Re: Separating source files in YAML::XS by marto
in thread Separating source files in YAML::XS by tinita

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.