libs, headers, and compilations
Christopher Chan
christopher.chan at bradbury.edu.hk
Mon Oct 11 03:49:41 UTC 2010
On Monday, October 11, 2010 11:00 AM, Verde Denim wrote:
>
>
> On Sun, Oct 10, 2010 at 10:39 PM, Verde Denim <tdldev at gmail.com
> <mailto:tdldev at gmail.com>> wrote:
>
>
>
> On Sun, Oct 10, 2010 at 10:29 PM, Christopher Chan
> <christopher.chan at bradbury.edu.hk
> <mailto:christopher.chan at bradbury.edu.hk>> wrote:
>
> Hi Jack,
>
> > > checking for linux/if_arp.h usability... no
> > > checking for linux/if_arp.h presence... yes
> > > configure: WARNING: linux/if_arp.h: present but cannot be
> compiled
> > > configure: WARNING: linux/if_arp.h: check for missing
> > prerequisite headers?
> > > configure: WARNING: linux/if_arp.h: see the Autoconf
> documentation
> > > configure: WARNING: linux/if_arp.h: section "Present But Cannot
> > Be Compiled"
> > > configure: WARNING: linux/if_arp.h: proceeding with the
> > preprocessor's
> > > result
> > > configure: WARNING: linux/if_arp.h: in the future, the
> compiler will
> > > take precedence
> > > checking for linux/if_arp.h... yes
>
> > Any thoughts on the other two warnings concerning wireless.h
> and if_arp.h?
>
> Just try running 'make dep' and then make to see if things will
> actually
> not compile. Google gave a hack that does not seem right to me
> so this
> warning could be a false warning for I found another post that just
> ignored the warnings.
>
> Ok. I ran make dep and then make and then make install. Same
> results. It compiles successfully, but still has those two warnings.
> I've been googling and searching through forums at bt, airodump and
> secjetlib and only found a single thread with 0 responses. Maybe
> your last comment about these being warnings that can be ignored are
> correct. I'll complete the setup and give the app a test run to be
> sure. Thanks much for the replies - I appreciate your feedback.
>
> Jack
>
>
> Update: Both console and web interfaces seem to work ok! I guess those
> warnings can be tabled for the moment. If it turns out they have a
> hiccup somewhere I'll keep digging and, if I find the solution, I'll
> post it here. The only glitch in their instructions is giving a link to
> setup mysql for the database and having that link go 404... I guess they
> want everyone to go to Postgres...
I have seen a post to make that compile error go away but I doubt that
you really want to muck around with a kernel header file. Better go
postgresql.
More information about the ubuntu-users
mailing list