Fixed.

With 6.4.1. I edited drivers/intel/Makefile and commented out line 10 
(referencing the e1000).

We were using a snapshot of the 6.2 0-stable branch, taken 30th March 2016. 
This doesn't build on Santiago 6.8, even with the makefile mod.

So all but two of our machines are 6.4.1, and the last two 6.2.0-stable 
machines will be updated soon.

A.

--
Andrew Howard
[email protected]

----- Reply message -----
From: "Andrew Howard" <[email protected]>
To: <[email protected]>
Subject: PF_RING build errors on RHEL Santiago 6.8
Date: Wed, Jan 11, 2017 18:34

Sorry that should read 4.2 not 4 2, so our kernel is older than yours.
A


--
Andrew Howard
[email protected]




----- Reply message -----
From: "Andrew Howard" <[email protected]>
To: <[email protected]>
Subject: PF_RING build errors on RHEL Santiago 6.8
Date: Wed, Jan 11, 2017 18:13



Hi Alfredo,

Thanks for the quick reply, and forgive the forum threading mishap. My phone 
seems confused.

We're running 2.6.32-642.4 2.el6.x86_64

I'll see what can be done to patch up to your 642.11.1 level.

We downloaded the tar.gz source from 
github.com/ntop/PF_RING/releases/tag/v6.4.1.

Regards,
A.

--
Andrew Howard
[email protected]




----- Reply message -----
From: "Andrew Howard" <[email protected]>
To: <[email protected]>
Subject: PF_RING build errors on RHEL Santiago 6.8
Date: Wed, Jan 11, 2017 17:39



Hi all,

When trying to build release 6.4.1 I see "implicit declaration of function 
vlan_tx_tag_present" at line 3401 of 
drivers/intel/e1000e/e1000e-3.2.7.1-zc/src/kcompat.h

Some research suggests this problem has affected other products from other 
vendors.

Suggestions for things to try would be welcome. Plan B is to reimage four 
machines with 6.7, but we'd prefer not too if possible.

(We already have PF_RING 6.2.0 running happily on two RHEL 6.7 machines).

Thoughts welcome.

Regards,
A.
--
Andrew Howard
[email protected]
_______________________________________________
Ntop mailing list
[email protected]
http://listgateway.unipi.it/mailman/listinfo/ntop

Reply via email to