in reply to Re^3: Perl 5.10.1 RC1 released for testing
in thread Perl 5.10.1 RC1 released for testing

Yes, that helps building under ActivePerl/MinGW-5.1.4.1.ppd.
  • Comment on Re^4: Perl 5.10.1 RC1 released for testing

Replies are listed 'Best First'.
Re^5: Perl 5.10.1 RC1 released for testing
by syphilis (Archbishop) on Aug 08, 2009 at 15:04 UTC
    Yes, that helps building under ActivePerl/MinGW-5.1.4.1.ppd

    Which begs the question "Why does it make a difference ?" (I don't know the answer.)

    Cheers,
    Rob
      Me neither. I tried comparing (diff -ruN), and noticed binutils versions are different (but you knew that), but that doesn't explain it
      C:\strawberry\c\bin\addr2line.exe -v GNU addr2line 2.17.50 20060824 Copyright 2005 Free Software Foundation, Inc. This program is free software; you may redistribute it under the terms + of the GNU General Public License. This program has absolutely no warran +ty. C:\Perl\site\lib\auto\MinGW\bin\addr2line.exe -v GNU addr2line (GNU Binutils) 2.19.1 Copyright 2007 Free Software Foundation, Inc. This program is free software; you may redistribute it under the terms + of the GNU General Public License version 3 or (at your option) any later + version. This program has absolutely no warranty.
        ... and noticed binutils versions are different (but you knew that)...

        Yes ... I think I *did* know that at one stage, but then mistakenly brought up "mingw-runtime" in my earlier post.

        When Jan Dubois said (in that p5p thread):
        "I still don't understand how having -lmsvcrt in the link options could hurt though, even if it may be redundant"
        then I knew it was time for me to stop even thinking about it :-)

        More seriously, it would be nice to know if this is a MinGW bug or a perl bug. I'm inclined to think that it must be a MinGW bug because, as Jan said, it's hard to "understand how having -lmsvcrt in the link options could hurt". But I wouldn't like to file a bug report to the MinGW developers simply on the strength of this perl build failure ... and I know from past experience that I'm very good at misappropriating the blame :-)

        Cheers,
        Rob