c:\strawberry\c\bin\../lib/gcc/i686-w64-mingw32/4.6.3/include/c++/streambuf:571:7: error: expected ')' before '*' token

Yes, that's as far as I got with 1.61, too.
I think it means that streambuf is being parsed as a C file instead of as the C++ file that it is.
But I don't know why that is happening or what to do about it. I do see one invocation of 'gcc' in the generated Makefile: 
.c.i:
    gcc -E -c $(PASTHRU_INC) $(INC) \
    $(CCFLAGS) $(OPTIMIZE) \
    $(PERLTYPE) $(MPOLLUTE) $(DEFINE_VERSION) \
    $(XS_DEFINE_VERSION) $(CCCDLFLAGS) "-I$(PERL_INC)" $(PASTHRU_DEFIN
+E) $(DEFINE) $*.c > $*.i

[download]
But I see nothing in the build output to indicate that's causing the problem. (Still, perhaps that's something that could be investigated further.)

I think you're quite right that there's nothing wrong with the taglib library, and that the problem is Audio::TagLib.
I think it's a pity that Audio::TagLib has chosen to build against the libtag C++ library, instead of against the libtag_c C library.
At least I presume libtag_c is a C library - and that I'd therefore have a good chance of being able to work around any problems in the offchance that it didn't build straight out of the box.

Cheers,
Rob

In reply to Re^2: Audio::TagLib and Strawberry Perl by syphilis
in thread Audio::TagLib and Strawberry Perl 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.