Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

Phred (5358)


Fred is a Perl and PostgreSQL geek. He has made some very small contributions to a few cpan modules and mod_perl.

Journal of Phred (5358)

Sunday November 12, 2006
05:54 AM

Compiling Perl on x86_64

[ #31581 ]

Been playing with an opteron box (hp dl145g2) the past few days. I built Perl 5.8.8 on it today from source. You can't just go flying through the 'sh Configure' like you can with x86. You have to specify /usr/lib64 as an additional library path (important!), and I added the optimization flags '-march=opteron -mcpu=opteron -mtune=opteron -fpic -pipe -fomit-frame-pointer'. Most of those are just for fun, but -fpic seems to be important, as Dynaloader broke and whined about needing it when building mod_perl2.

So far quite a bit of fun - damn fast cpu - but Centos 4.4 doesn't have the correct sata driver fix in the kernel (you need at least 2.6.10), and my own kernel builds have been failing. I've given up on Centos (it was fun while it lasted) and gone back to Gentoo. A longer install initially, but at least I know that it won't leave me stranded in a dead end trying to get everything working. Ah the joys of Linux - at least my macbook hasn't been giving me any grief :)

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • You can't just go flying through the 'sh Configure' like you can with x86.

    It's notable (and frustrating) that none of the Linux vendors who sell and support x86_64, and ship Perl on it, have sent any patches upstream for Configure, so that we can incorporate whatever change they feel is the most appropriate to solve these problems. They're the experts on Linux on x86_64, not us.

  • Nicholas++.

    I have always wondered how we (perl maintainers) most of the time needed/need to go and hunt down the people at various UNIX/Linux people and hold them upside down and shake until they submit their changes back to us. It would be so much easier for *them* to feed the changes back so that they don't need to maintain them.

    There are some notable exceptions: e.g. OpenBSD, Solaris, Mac OS X, where the people have been very good, proactive and communicated back (and forth) with the perl maintainers.
  • Once you have things working with x86_64, please do send a note to of the changes you needed.
    • Will do Jarkko, thanks for the feedback. I didn't have to do too much different, but I've cut my teeth on a few x86_64 headaches before, so some of it may seem obvious to me. I remember it was a lot harder the first time I used 64bit.
      • Well, *64-bit* as such has of course worked with Perl for, oh, more than six years now :-)