cyrus-imapd fails with use of undeclared identifier

[hbsimon (Horst Simon)]

info:build IMAP.xs:127:17: error: use of undeclared identifier 'sv_undef'

cyrus-imapd fails during the build

:info:build   rv = newSVsv(&sv_undef);

:info:build IMAP.xs:395:13: error: use of undeclared identifier 'sv_no'
:info:build           ST(0) = &sv_no;
:info:build                    ^

I am using OS/X Maverick 10.9.4 with Xcode Version 5.1.1 (581008) and latest command line tools. I am too have attached the log file main.log for this error.

[jmroot (Joshua Root)]

Looks like the exact same problem as #43112. Which would mean r123368 broke it.

[ryandesign (Ryan Carsten Schmidt)]

As I said in #43112, the maintainer should look into updating the port. The changelog shows that compatibility with perl 5.14 (and presumably later) was added in cyrus-imapd 2.4.8. I'll look into it now...

[mf2k (Frank Schima)]

Sorry about that, this is what happens when maintainers do not respond. Reverted in r124858.

[hbsimon (Horst Simon)]

The build is still failing even, after after removing and re-installing macports.

:info:build IMAP.xs:127:17: error: use of undeclared identifier 'sv_undef'
:info:build   rv = newSVsv(&sv_undef);
:info:build                 ^

and

:info:build IMAP.xs:395:13: error: use of undeclared identifier 'sv_no'
:info:build           ST(0) = &sv_no;
:info:build                    ^

[hbsimon (Horst Simon)]

After I changed the symbolic link for perl from perl5.16 to perl5.12 in /opt/local/bin the build worked, but I got an activation error as follow:

Error: org.macports.activate for port cyrus-imapd returned: Image error: /opt/local/share/man/man8/master.8.gz is being used by the active postfix port.
Please deactivate this port first, or use 'port -f activate cyrus-imapd' to force the activation.

Force activation worked, but haven't tested functionality and don't know if it fails after changing the link back to perl5.16, or if other ports are failing if I don't change it back.

[mf2k (Frank Schima)]

That's a quirk of the perl5 port. Realistically all of the ports requiring perl should be using the same perl as your active perl5 port. This is why we are trying to unify them to perl 5.16 and soon to perl 5.20 after that.

[dbevans (David B. Evans)]

Updated to version 2.4.17 using perl5.16 in r129759.