Bitwise operations may be your best choice. There are no 24-, 6-, or 26-bit types in unpack's formats, and vec demands its chunks be a power of two bits wide and aligned. Here is one way to do it, unpacking to three ints and doing the bit operations. 

$fh->read(my $buf, 12);
my ($var1, $var2, @raw) = unpack 's s L2' $buf;
my ($var3,$var4) = map { ($_ >> 8, $_ & 0xff) } $raw[0];
my ($var5,$var6) = map { ($_ >> 26, $_ & 0x3fffffff) } $raw[1];

[download]
That's not quite as unportable as it looks, but it's still on the edge.

Update: Differs from Stevie-O's by bit order of the C struct. I'm not sure which is correct, so I'd bet on his. Adjust to what works :-)

After Compline,
Zaxo

In reply to Re: Unpacking struct by Zaxo
in thread Unpacking struct by Anonymous Monk

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.