Hola, Peter, thank you for the new snapshot , it is great :-D
I am having the same problem than Adrian Popa , regarding the compilation of PortTracker including in nfdump-snapshot-20070312 (http://sourceforge.net/mailarchive/message.php?msg_id=38351907). It is true that if you modify the flist.c as Adrian suggested (thank you Adrian) you compile PortTracker without problems, but i am worried that, as you suggested, if you have errors with the fts* calls your nfdump, although compiled , could have some inconsistencies. I have made a test with two machines, the one I have problems compiling PortTracker with (a 32 bits Red Hat Linux Enterprise) and another machine (a 64 bits Red Hat Linux Enterprise) with the same glibc rpm installed. In the 32 bits machine the problem is , although the fts.h is installed in /usr/include , when you do the nfdump configure fts.h can't be included because of this (according to the config.log) [output from configure] checking fts.h usability... no checking fts.h presence... no [...] config.log:configure:5732: checking fts.h presence config.log:/usr/include/fts.h:41:3: #error "<fts.h> cannot be used with -D_FILE_OFFSET_BITS==64" Compiling in the 64 bits machine i found no problems compiling neither nfsen nor PortTracker, and the fts.h is included without problems. Maybe there is something wrong in the configure file. Cheers, Chelo -- "Se puede admitir la fuerza bruta, pero la razón bruta es insoportable.". Oscar Wilde ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Nfsen-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nfsen-discuss
