in reply to Re: Does XCode 4 break Perl?
in thread Does XCode 4 break Perl?

Your version of perl is most likely compiled with GCC, as that has been the standard compiler on Macs up until now. If you compile and XS module using the new LLVM compiler, then it is unlikely to link correctly with perl that was compiled on a different compiler.
You're right about there being a new compiler: gccversion='4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2335.9). But I did mention that I also tried rebuilding perl. Since it was in a fresh tree, the modules had to be recompiled as well.

The error I'm seeing looks like an ordinary syntax error, that's what's so baffling. After adding 'use Fcntl; use POSIX qw(ENOSYS EXDEV);' at the beginning of IO/AIO.pm, I got an error about a symbol that was only defined by IO::AIO: READDIR_DIRS_FIRST, so it looks the export mechanism might have gotten screwed up. I'm out of my depth here. And this is the only module I've seen having this problem so far, so it's mysterious to me.

And I'm not sure if this is going to be solved in a timely fashion since the module author is anti-bugtracker.

Replies are listed 'Best First'.
Re^3: Does XCode 4 break Perl?
by Anonymous Monk on Apr 01, 2011 at 09:00 UTC
    The error I'm seeing looks like an ordinary syntax error, that's what's so baffling

    Please copy/paste the error message

[reply]
      It's in my original message.
[reply]
        Doh

        O_RDONLY is supposed to come from Fcntl 

        $ perl -MFcntl=O_RDONLY -le  " print +O_RDONLY "
0

        [download]
        If you don't use Fcntl, there is no O_RDONLY constant
[reply]
[d/l]

In Section Seekers of Perl Wisdom