On Mon, Jun 23, 2014 at 12:42:59AM -0700, Russ Allbery wrote:
> Damyan Ivanov <d...@debian.org> writes:
>
> > Perhaps. But I think the fix is not in perl but in xchat-gnome.
>
> > It seems PL_memory_wrap and Perl_croak_nocontext were moved to libperl
> > in 5.20, so the test library needs to link with that. Adding
> > $(perl -MExtUtils::Embed -e ldopts)
> > to the compiler flags makes it pass. And xchat-gnome configuration
> > looks like this:
>
> > checking for perl... /usr/bin/perl
> > checking for Perl header files... found
> > checking for Perl library... found
> > …
> > checking for perl... /usr/bin/perl
> > checking for perl >= 5.8.1... 5.20.0
> > checking for XML::Parser... ok
> > …
> > checking which plugins to build... autoaway notification url_scraper
> > sound-notification net-monitor notify-osd perl python tcl
> > …
> > config.status: creating plugins/perl/Makefile
>
> > Attached is the patch to xchat-gnome.
>
> > Not yet reassigning to allow a sanity check on my conclusions :)
>
> Your patch looks correct to me. It looks like this Autoconf probe was
> relying on those functions being implemented as macros? I'm not sure how
> the probe program could otherwise be successfully linked without including
> the linker options.
Thanks for looking at this.
The probe doesn't actually use anything from the headers, it just
includes them:
#include <XSUB.h>
#include <EXTERN.h>
#include <perl.h>
int main() { return 0; }
It's not clear to me that this should require libperl linkage?
--
Niko Tyni nt...@debian.org
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
