Can you check with keeping LD and CC before ./configure.
The changed one should look like
LD=${CROSS_COMPILE}ld CC=${CROSS_COMPILE}gcc CXX=${CROSS_COMPILE}g++
CFLAGS="-g3 -O0" --prefix=${FILESYSTEM_ROOT_DIR} ./configure
--host=m68k-linux-gnu --build=i686 --target=m68k-linux-gnu
--disable-embedde
Please note that I am using net-snmp-5.5, and the with-ld option is not
supported: Wish it was.
“
The Net-SNMP project uses the standard configure mechanism, so the usual
cross-compilation options are available - in particular --host and --target. It
is also possible to specify the compiler and
Hello,
How do I specify the right ld for the build to work ? I’m using linux and while
linking with a library that contains the calls from SNMP agent, it uses the
wrong link path : /usr/bin/ld
The configure line:
./configure LD=${CROSS_COMPILE}ld CC=${CROSS_COMPILE}gcc
CXX=${CROSS_COMPILE}g++
Hi again -(See attached file: lldpPortConfigTable.c)(same file with
more debug, and change below)
Long story (well, short stupid story), but I wasn't running with the
HANDLER change. Now it seems to work fine, except for the following:
Problem 1: When I tried to do a set for a row that doe
On 16 June 2010 15:23, Kathy McLeod wrote:
> In your previous note, you said to "Try tweaking the injection of the cache
> handler to use 'TABLE_HANDLER_NAME'
>
> In this note, you say, "If you insert the cache helper using
> 'TABLE_HELPER_NAME'
> so is it Handler or Helper?
HANDLER
>From the h
So far, I have not been able to reproduce this problem...
Thanks!
Date: Tue, 15 Jun 2010 17:41:27 +0200
Subject: Re: subagent core dump at startup
From: bvanass...@acm.org
To: lh_1...@hotmail.com
CC: net-snmp-users@lists.sourceforge.net
On Mon, Jun 14, 2010 at 8:53 PM, W Z wrote:
We use
Hi -
In your previous note, you said to "Try tweaking the injection of the cache
handler to use 'TABLE_HANDLER_NAME'
rather than 'TABLE_TDATA_NAME'."
In this note, you say, "If you insert the cache helper using
'TABLE_HELPER_NAME', then you end up
with
cache -> table -> container -> tdata
On 15 June 2010 21:46, Kathy McLeod wrote:
> I think your diagnosis is correct. It is setting up for the row and column
> in the old table and then when those rows are not in the new table, I get
> errors. This does not seem correct to me - isn't the point of reloading to
> have the latest and g
