https://bugzilla.redhat.com/show_bug.cgi?id=1589381
Bug ID: 1589381
Summary: perl-Cflow not actually linked to flow-tools since -17
Product: Fedora EPEL
Version: epel7
Component: perl-Cflow
Severity: low
Assignee: orion(a)nwra.com
Reporter: redhat(a)adiemus.org
QA Contact: extras-qa(a)fedoraproject.org
CC: orion(a)nwra.com, perl-devel(a)lists.fedoraproject.org
Created attachment 1449269
-->
https://bugzilla.redhat.com/attachment.cgi?id=1449269&action=edit
Basic spec file patch to restore the necessary CCFLAGS/LIBS for linking to
flow-tools
Description of problem:
perl-Cflow isn't actually linked against flow-tools (libft) and doesn't seem to
have been since release -17. It works in the EPEL6 version (-11)
In -17, it seems the spec file was changed such that the Makefile creation line
changed from:
[Working, 1.053-11]
%{__perl} Makefile.PL INSTALLDIRS=vendor OPTIMIZE="$RPM_OPT_FLAGS" \
CCFLAGS='-DOSU' LIBS='-lft'
[Broken, 1.053-32]
%{__perl} Makefile.PL INSTALLDIRS=vendor OPTIMIZE="$RPM_OPT_FLAGS"
where the manual set of CCFLAGS and LIBS was removed. The problem is, the
upstream source won't detect and build against flow-tools otherwise. (It's
autodetection logic expects perl-Cflow to be inside the build tree for
flow-tools itself)
Restoring the CCFLAGS/LIBS override in the spec file results in a build that
works as expected. (Consistent with the EPEL6 build)
Version-Release number of selected component (if applicable):
perl-Cflow-1.053-32.el7.x86_64
How reproducible:
Always
Steps to Reproduce:
1. yum -y install flow-tools perl-Cflow
2. Run flow-capture to gather some netflow data into flow files
3. flowdumper -v ft-v05.whatever
Actual results:
$ flowdumper -v ft-v05.2018-06-08.144801-0500
ft-v05.2018-06-08.144801-0500: Invalid index in cflowd flow file: 0xCF100103!
Version 5 flow-export is required with *all* fields being saved.
Expected results:
$ flowdumper -v ft-v05.2018-06-08.144801-0500
FLOW
index: 0xc7ffff
router: 127.0.0.1
<snip>
Additional info:
I've attached a very basic diff of the spec file, incremented to -33, that
makes the change suggested above.
--
You are receiving this mail because:
You are on the CC list for the bug.