List::MoreUtils required List::MoreUtils::XS so I tried to install that first

Aaah, yes - the problem is with List-MoreUtils-XS-0.428 and not List-MoreUtils-0.428.

I think List-MoreUtils will work quite well without List-MoreUtils-XS, so that's an option you might take.
It would simply mean that, for some of the functions, you'll be using the slower pure-perl version instead of the XS version.

According to my memory (which may be flawed), I've not seen that "handshake" error issued in relation to generated .c files before.
It's an error that I associate with .xs files.

It's also puzzling that the LeakTrace.c file, generated during the Test-LeakTrace-0.16 build, does not suffer the same error.
Both XS.c and LeakTrace.c were generated from their respective xs files by ExtUtils::ParseXS.
Each of those .c files begin with a comment that tells you what generated them. I guess you could take a look at those comments and verify that they were both generated by the same version of ExtUtils::ParseXS.

My main hunch is that, between 5.20 and 5.30, some change has occurred that gcc-3.4.5 can't handle - but I certainly don't rule out the possibility that it's because of something else.
Maybe try posting to p5p mailing list. Someone there might have an idea on what you can do to overcome the error.
If it were me, I'd be upgrading gcc to a more recent version of gcc if there's an option to do that. Even gcc-4.6.3 is still building modern perls (up to and including current blead 5.33.0) flawlessly on my debian wheezy system.

Cheers,
Rob

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.