Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 14 May 2022 02:54:43 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 263965] archivers/p5-Compress-Raw-Zlib: 2.104 reports undefined symbol "z_zlibVersion", possibly due to -DZ_PREFIX
Message-ID:  <bug-263965-7788@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D263965

            Bug ID: 263965
           Summary: archivers/p5-Compress-Raw-Zlib: 2.104 reports
                    undefined symbol "z_zlibVersion", possibly due to
                    -DZ_PREFIX
           Product: Ports & Packages
           Version: Latest
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: sunpoet@FreeBSD.org
          Reporter: greenreaper@hotmail.com
             Flags: maintainer-feedback?(sunpoet@FreeBSD.org)
          Assignee: sunpoet@FreeBSD.org

Created attachment 233905
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D233905&action=
=3Dedit
Patch to remove -DZ_PREFIX

After doing a portupgrade of this package on FreeBSD 11.4 (I know, we're in=
 the
progress of migrating... :-), munin-run apache_accesses gives

/usr/local/lib/perl5/site_perl/mach/5.32/auto/Compress/Raw/Zlib/Zlib.so:
Undefined symbol "z_zlibVersion"

The munin plugin in question runs a Perl script using LWP::UserAgent, which=
 may
need to handle zlib-compressed streams.

I think the addition of -DZ_PREFIX to DEFINES may have caused the issue; as
another developer noted, this is done in this version regardless of whether
BUILD_ZLIB is set to false, which is what FreeBSD does as well in a patch:
https://github.com/pmqs/Compress-Raw-Zlib/issues/8
"the system zlib will of course have the regular symbol names and not the
renamed versions."

I added the attached patch to end of the port's files/patch-config.in (bear=
ing
in mind that the last line of the existing patch is empty) and re-ran the
portupgrade, after which the munin plugin ran correctly.

I reported this upstream there, but figured I should mention it here as oth=
ers
may come across it as well. Not sure if it breaks anything, but it worked f=
or
me.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-263965-7788>