[ARGUS] argus 2.0.6 on Fedora Core 2

slif at bellsouth.net slif at bellsouth.net
Wed Jul 21 13:26:50 EDT 2004


Steve McInerney wrote:

>Hi Carter,
>
>one additional trivial problem in the install of argus-2.0.6.fixes.1, as
>can be seen below:
>
>/usr/bin/install -c -m 0644 ./man/man5/rarc.5 /usr/local/man/man5/rarc.5
>/usr/bin/install: cannot stat `./man/man5/rarc.5': No such file or directory
>make: *** [install] Error 1
>
>I assume that this one was missed in the split to clients?
>Definately Not a Biggie.
>
>
>- Steve
>
>>FWIW, I was independently trying to compile on some FC2 boxes with the
>>same problem in the last hour - should read the list more frequently.
>>Sigh.
>>
>>Grabbing the latest libpcap sources had the same problem. It _appears_ to
>>my ignorant eyes that the change is actually in the libpcap sources. If
>>that helps?
>>
>>
>>- Steve
>>
>>>Hey Mike,
>>>   Thanks, we'll need to add the test to the ./configure
>>>script.  Its not that big of a deal, but not a trivial
>>>fix.  I'll try to get it into argus for the 2.0.7
>>>development thread.  So, just a political reaction
>>>to the name change:
>>>
>>>   "what a bunch of morons".
>>>
>>>Carter
>>>
>>>
>>>-----Original Message-----
>>>From: owner-argus-info at lists.andrew.cmu.edu
>>>[mailto:owner-argus-info at lists.andrew.cmu.edu] On Behalf Of Mike
>>>Iglesias
>>>Sent: Thursday, July 15, 2004 1:31 PM
>>>To: argus-info at lists.andrew.cmu.edu
>>>Subject: [ARGUS] argus 2.0.6 on Fedora Core 2
>>>
>>>When I tried to compile argus 2.0.6 on Fedora Core 2 (which uses the
>>>2.6.x kernel series), common/gencode.c failed to compile because it
>>>could not find the include file /usr/include/net/bpf.h.  It turnes out
>>>that in FC2 (at least), the file has been renamed to
>>>/usr/include/pcap-bpf.h.  I don't have a FC1 system handy to check if
>>>it was renamed there as well.
>>>
>>>I'm not sure what has to be done to the configure script to fix this.
>>>Here's a diff of what I did to gencode.c to fix this.  I have not tested
>>>it yet to see if it works, but it compiles now.
>>>
>>>--- gencode.c.dist      2004-02-23 07:00:36.000000000 -0800
>>>+++ gencode.c   2004-07-15 10:24:48.956200744 -0700
>>>@@ -59,7 +59,8 @@
>>> #include <stdlib.h>
>>> #include <syslog.h>
>>>
>>>-#include <net/bpf.h>
>>>+/*#include <net/bpf.h>*/
>>>+#include <pcap-bpf.h>
>>>
>>> #include <argus_out.h>
>>> #include <argus_filter.h>
>>>
>>>
>>>Mike Iglesias                          Email:
>>>iglesias at draco.acs.uci.edu
>>>University of California, Irvine       phone:       949-824-6926
>>>Network & Academic Computing Services  FAX:         949-824-2069
>>>
>>>
>>>
>>>
>>
>
>
>
>
slif at bellsouth.net wrote 07/01/2004 05:28 AM:

>Hello,
>I'm using the fixes.1 sources and running on a later Redhat-like
>Linux system.  I've built RPM packages for the server and the clients.
>
>Here is how I did that. Let me know if this is useful.
>
>  1. Download the source tarballs from the web site.
>  2. Unpack them.
>  3. Move xx.fixes.1 to xx, for xx in {argus,argus-client}.
>  4. patch -p0 < client.patch ; patch -p0 < server.patch
>  5. tar czf argus-2.0.6.tar.gz `find argus-2.0.6 -type f`
>  6. tar czf argus-clients-2.0.6.tar.gz `find argus-clients.2.0.6 -type f`
>  7. rpmbuild -tb argus-2.0.6.tar.gz > build.out 2>&1
>  8. rpmbuild -tb argus-clients-2.0.6.tar.gz > build2.out 2>&1
>
Hi,
I had posted fixes for these problems on July 1 to this list,
and included changes to RPM "spec" files, so that one may build
RPM package for clients, for example.  I chose to use prefix=/usr,
but note that there are some problems getting the project's Makefiles
to use that value. So, you might have better success defining prefix
to be the traditional /usr/local.

I was using FC2 at the time, but apparently I didn't make that point clear.
I believe the changes I've supplied will work with RedHat 8/9 as well,
but have not tried them there.

At July 1, I wasn't aware of the location+name change of net/bpf.h to pcap-bpf.h.
Having the sources for clients available, I just copied include/net/bpf.h
to the argus-2.0.6-fixes.1/include/net, and that allowed the build to succeed.

Besides Steve's recent FAQ changes, are there any other patches
which can be applied to the argus-2.0.6-fixes.1 or argus-clients-2.0.6-fixes.1
source tarballs to bring a user's source into agreement with
current developments ?

Thanks!
-Mike Slifcak

-------------- next part --------------
A non-text attachment was scrubbed...
Name: linux-build-patches.tar.gz
Type: application/gzip
Size: 4152 bytes
Desc: not available
URL: <https://pairlist1.pair.net/pipermail/argus/attachments/20040721/eac1ca0d/attachment.gz>


More information about the argus mailing list