Mark Duling wrote:
Seems like I've seen this and adding -liconv to the configure environment
solved it. If my memory is correct, don't ask me why.
Mark
Mark,
Thanks for the suggestion. Based on a Google search I found and tried this:
./configure CFLAGS=-I${prefix}/include CPPFLAGS=-I${prefix}/include
LDFLAGS="-L${prefix}/lib -liconv"
Yet now I get a catastrophic failure much more quickly that just doesn't
make any sense:
~snip~
Configuring ntop according to your request(s):
./configure CFLAGS=-I/include CPPFLAGS=-I/include LDFLAGS=-L/lib -liconv
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking for gawk... (cached) mawk
checking for style of include used by make... GNU
checking for gcc... gcc
checking for C compiler default output file name... configure: error: C
compiler cannot create executables
See `config.log' for more details.
~snip~
Config.log:
~snip~
configure:2807: checking for C compiler default output file name
configure:2810: gcc -I/include -I/include -L/lib -liconv conftest.c >&5
/usr/bin/ld: cannot find -liconv
~snip~
Did I get something wrong on my command line? Is liconv something I also
need to install?
Thanks,
Eric Brander
_______________________________________________
Ntop mailing list
[email protected]
http://listgateway.unipi.it/mailman/listinfo/ntop
