Hi Monks, I am facing a problem with execution of a system command on Linux. As part of our product, we are shipping perl 5.8.8 v5.8.8 built for i686-linux. Now, i'm trying to execute, `uname -m` via perl script on i686- 32 bit linux machines, x86_64 linux machines and ia64 linux machines. The output i am getting for that command executed, is correct for i686 and x86_64, however it is wrong for ia64 machines. `uname -m` on a ia64 bit machine using the perl that we ship, gives the output as, "i686" in place of "ia64". I am thinking, if this could be a problem with the distributions of perl for various architectures. I don't have a solution on resolving this. I may even have to ship a new version of perl for ia64 machine. Is there anyway i can make the existing shipped perl do the job of getting the right output..??

In reply to Perl Distribution differences for i686/x86_64 and ia64 over Linux. by sriharsha

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.