p5-Cflow and flow-tools

[Frank J. Laszlo]

There is a knob for this in my ports. It appears to set the appropriate 
options explicitly in the Makefile. Like this:

.if defined(WITH_FLOW_TOOLS)
LIB_DEPENDS+=   ${LOCALBASE}/lib/libft.a:${PORTSDIR}/net-mgmt/flow-tools

CFLAGS+=        -I${LOCALBASE}/include -DOSU
CONFIGURE_ARGS+=        \
        "LDDLFLAGS= -shared -L${LOCALBASE}/lib -lft -lz" \
        "INC= -I${LOCALBASE}/include" "LDLOADLIBS= -L${LOCALBASE}/lib 
-lft -lz"
.endif

Which should override the Makefile.PL mechanism for finding the location 
of flowtools. Please cvsup your ports and verify this. if in fact it is 
not working how it should, I will be glad to write a patch for it. Hope 
this helps.

Regards,
    Frank Laszlo


Charles Sprickman wrote:

> Howdy,
>
> I don't see a specific maintainer, so I'll send this here...
>
> p5-Cflow has support for using flow-tools output rather than cflowd 
> output, and flow-tools is the recommended netflow collection tool 
> these days.
>
> There's a section of Makefile.PL where the package checks to see if 
> it's being built inside the flow-tools hierarchy.  It does not check 
> the standard /usr/local/lib, /usr/local/include paths.  But if you 
> edit Makefile.PL to look like this:
>
> sub find_flow_tools {
>    my($ver, $dir);
>    my($libdir, $incdir);
>    if (-f '/usr/local/lib/libft.a') {
>       $dir = '/usr/local/lib';
>       $incdir = "-I/usr/local/include";
>       $libdir = "-L$dir";
>    }
>
> It builds fine and links in the flow-tools stuff.  This is needed if 
> you want to say, run flowscan and you run flow-tools.
>
> I don't know enough about ports to fix this, but it seems the port's 
> Makefile could offer this as an option...
>
> Charles
> _______________________________________________
> freebsd-ports at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"