:51 AM
To: Javier Torres
Cc: Dave Shield; [email protected]
Subject: Re: Compile issues
Javier Torres wrote:
> Ok,
> So when compiling under FC2 I had no issues. On configure I chose the
> following options:
> sudo ./configure --with-mib-modules=agentx --with-
Javier Torres wrote:
Ok,
So when compiling under FC2 I had no issues. On configure I chose the
following options:
sudo ./configure --with-mib-modules=agentx --with-perl-modules
Then I compiled on each platform. FC2 worked no issues and cygwin had
the following error:
How old is your Cygwin i
From: Dave Shield [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 19, 2006 11:14 AM
To: Javier Torres
Cc: [email protected]
Subject: RE: Compile issues
On Thu, 2006-01-19 at 10:56 -0500, Javier Torres wrote:
> I am seeing it on both systems, exact same error.
You're
ent: Thursday, January 19, 2006 11:14 AM
To: Javier Torres
Cc: [email protected]
Subject: RE: Compile issues
On Thu, 2006-01-19 at 10:56 -0500, Javier Torres wrote:
> I am seeing it on both systems, exact same error.
You're getting a warning about "winsock.h"
: Compile issues
On Wed, 2006-01-18 at 16:50 -0500, Javier Torres wrote:
> Hello,
> I am currently trying to compile version 5.2.1.1 on a FC2 machine and
> on cygwin.
Can you try with the latest release on that line (5.2.2) and see if you
get the same problems.
Also, are you seeing t
To: Javier Torres
Cc: [email protected]
Subject: RE: Compile issues
On Thu, 2006-01-19 at 10:56 -0500, Javier Torres wrote:
> I am seeing it on both systems, exact same error.
You're getting a warning about "winsock.h" being present (but not
compiling)
On Thu, 2006-01-19 at 10:56 -0500, Javier Torres wrote:
> I am seeing it on both systems, exact same error.
You're getting a warning about "winsock.h" being
present (but not compiling) on a Linux system?
Boggle!!!
> I will try with the
> latest today and let you know.
I'd also suggest that y
On Wed, 2006-01-18 at 16:50 -0500, Javier Torres wrote:
> Hello,
> I am currently trying to compile version 5.2.1.1 on a FC2 machine and
> on cygwin.
Can you try with the latest release on that line (5.2.2) and
see if you get the same problems.
Also, are you seeing these same errors on both O/S's
