Argus clients and flow-tools

[Carter Bullard]

Well, we do assume that its a “ .a “ file that we should be looking for if we don’t get any hints from an ft-config file.
Because we need ftlib.h to build against you may need source … be sure and check to see if these distros provide ftplib.h …
If they do, then the code that needs to be changed is in acsite.m4, in the routine AC_QOSIENT_FLOWTOOLS around line 477 …
It maybe a simple substitution to look for libft.so instead of libft.a … but I’m sure there is a better way …
Let me look out our RHEL systems to see if there is a simple approach …

If you get excited, checkout acsite.m4, make some changes, then run autoconf to get a new configure script …

Carter

> On Sep 11, 2017, at 4:04 PM, Mike Iglesias <iglesias at uci.edu> wrote:
> 
> On 09/11/2017 09:38 AM, Carter Bullard wrote:
>> Hey Mike,
>> The strategy was suppose to be that these OS’s were using an ft-config script in their distribution and we would pick it up that way.
>> If there is an ft-config script in the “ libft " directory, and we’re not finding it ... does “./configure —with-libft=/path/to/lib/ft/directory” work  ...
>> Do you have an ft-config file buried somewhere in your /usr, /usr/share, or /opt directories ????
>> Hope all is most excellent,
> 
> There is no ft-config file anywhere on the system, and the RPMs for Fedora and
> CentOS do not contain one.  If I knew what to put in it I could make one and
> simply building the Argus clients.
> 
> 
> Thanks,
> 
> Mike
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4045 bytes
Desc: not available
URL: <https://pairlist1.pair.net/pipermail/argus/attachments/20170911/6439b11a/attachment.bin>