Iftop ./configure errors

  • WoAnerges
  • Born
  • Born
  • WoAnerges
  • Posts: 2

Post 3+ Months Ago

Hey guys,

I'm having problems installing iftop.
Could you, please, help me out?

Thanks!

Code: [ Select ]
iftop-1.0pre2]# ./configure
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking target system type... x86_64-unknown-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking sys/ioctl.h usability... yes
checking sys/ioctl.h presence... yes
checking for sys/ioctl.h... yes
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking sys/sockio.h usability... no
checking sys/sockio.h presence... no
checking for sys/sockio.h... no
checking for unistd.h... (cached) yes
checking for an ANSI C-conforming const... yes
checking for size_t... yes
checking whether time.h and sys/time.h may both be included... yes
checking sys/dlpi.h usability... no
checking sys/dlpi.h presence... no
checking for sys/dlpi.h... no
checking for regcomp... yes
checking for select... yes
checking for strdup... yes
checking for strerror... yes
checking for strspn... yes
checking for library containing socket... none required
checking for library containing log... -lm
checking for gethostbyname... yes
checking for library containing inet_aton... none required
checking for library containing inet_pton... none required
checking for inet_aton... yes
checking for inet_pton... yes
checking size of u_int8_t... unknown type
checking size of u_int16_t... unknown type
checking size of u_int32_t... unknown type
checking for stdint.h... (cached) yes
checking for library containing getnameinfo... none required
checking for library containing gethostbyaddr_r... none required
checking how to call gethostbyaddr_r... 8 args, int return
checking gethostbyaddr_r usability... yes
checking where to find pcap.h... /include
checking for pcap_open_live in -lpcap... yes
checking pcap.h usability... yes
checking pcap.h presence... yes
checking for pcap.h... yes
checking for a curses library containing mvchgat... -lncursesw
checking POSIX threads compilation... CFLAGS= and LIBS=-lpthread
checking POSIX threads usability... configure: error: it fails. We probably guessed the wrong CFLAGS.
  1. iftop-1.0pre2]# ./configure
  2. checking build system type... x86_64-unknown-linux-gnu
  3. checking host system type... x86_64-unknown-linux-gnu
  4. checking target system type... x86_64-unknown-linux-gnu
  5. checking for a BSD-compatible install... /usr/bin/install -c
  6. checking whether build environment is sane... yes
  7. checking for gawk... gawk
  8. checking whether make sets $(MAKE)... yes
  9. checking for gcc... gcc
  10. checking for C compiler default output file name... a.out
  11. checking whether the C compiler works... yes
  12. checking whether we are cross compiling... no
  13. checking for suffix of executables...
  14. checking for suffix of object files... o
  15. checking whether we are using the GNU C compiler... yes
  16. checking whether gcc accepts -g... yes
  17. checking for gcc option to accept ISO C89... none needed
  18. checking for style of include used by make... GNU
  19. checking dependency style of gcc... gcc3
  20. checking how to run the C preprocessor... gcc -E
  21. checking for grep that handles long lines and -e... /bin/grep
  22. checking for egrep... /bin/grep -E
  23. checking for ANSI C header files... yes
  24. checking for sys/types.h... yes
  25. checking for sys/stat.h... yes
  26. checking for stdlib.h... yes
  27. checking for string.h... yes
  28. checking for memory.h... yes
  29. checking for strings.h... yes
  30. checking for inttypes.h... yes
  31. checking for stdint.h... yes
  32. checking for unistd.h... yes
  33. checking sys/ioctl.h usability... yes
  34. checking sys/ioctl.h presence... yes
  35. checking for sys/ioctl.h... yes
  36. checking sys/time.h usability... yes
  37. checking sys/time.h presence... yes
  38. checking for sys/time.h... yes
  39. checking sys/sockio.h usability... no
  40. checking sys/sockio.h presence... no
  41. checking for sys/sockio.h... no
  42. checking for unistd.h... (cached) yes
  43. checking for an ANSI C-conforming const... yes
  44. checking for size_t... yes
  45. checking whether time.h and sys/time.h may both be included... yes
  46. checking sys/dlpi.h usability... no
  47. checking sys/dlpi.h presence... no
  48. checking for sys/dlpi.h... no
  49. checking for regcomp... yes
  50. checking for select... yes
  51. checking for strdup... yes
  52. checking for strerror... yes
  53. checking for strspn... yes
  54. checking for library containing socket... none required
  55. checking for library containing log... -lm
  56. checking for gethostbyname... yes
  57. checking for library containing inet_aton... none required
  58. checking for library containing inet_pton... none required
  59. checking for inet_aton... yes
  60. checking for inet_pton... yes
  61. checking size of u_int8_t... unknown type
  62. checking size of u_int16_t... unknown type
  63. checking size of u_int32_t... unknown type
  64. checking for stdint.h... (cached) yes
  65. checking for library containing getnameinfo... none required
  66. checking for library containing gethostbyaddr_r... none required
  67. checking how to call gethostbyaddr_r... 8 args, int return
  68. checking gethostbyaddr_r usability... yes
  69. checking where to find pcap.h... /include
  70. checking for pcap_open_live in -lpcap... yes
  71. checking pcap.h usability... yes
  72. checking pcap.h presence... yes
  73. checking for pcap.h... yes
  74. checking for a curses library containing mvchgat... -lncursesw
  75. checking POSIX threads compilation... CFLAGS= and LIBS=-lpthread
  76. checking POSIX threads usability... configure: error: it fails. We probably guessed the wrong CFLAGS.
  • Anonymous
  • Bot
  • No Avatar
  • Posts: ?
  • Loc: Ozzuland
  • Status: Online

Post 3+ Months Ago

  • WoAnerges
  • Born
  • Born
  • WoAnerges
  • Posts: 2

Post 3+ Months Ago

I've found an answer:
webhostingtalk p=1817349&postcount=3


choon wrote:
Actually it required:
libpcap
libcurses
which we can read it at ex-parrot com/~pdw/iftop/
Using up2date to install the required packages:
Quote:
up2date libpcap ncurses ncurses-devel
  • this213
  • Guru
  • Guru
  • User avatar
  • Posts: 1260
  • Loc: ./

Post 3+ Months Ago

an iftop rpm exists in the repos - you shouldn't be installing from source on an rpm-based distro. I'm guessing you have some reason for compiling it yourself so here's a src.rpm for EL5:

http://rpmfind.net/linux/RPM/dag/redhat ... .i386.html
  • Zealous
  • Guru
  • Guru
  • User avatar
  • Posts: 1244
  • Loc: Sydney

Post 3+ Months Ago

this213 wrote:
I'm guessing you have some reason for compiling it yourself so here's a src.rpm for EL5:

http://rpmfind.net/linux/RPM/dag/redhat ... .i386.html


is it not better to make a fresh compile on a server?

Just curious what the difference would be affecting the server?
  • this213
  • Guru
  • Guru
  • User avatar
  • Posts: 1260
  • Loc: ./

Post 3+ Months Ago

it's fine to compile your own rpms on the server, you may see some optimization from it - but you should be creating rpms and not installing from source. If you do install packages from source, you won't want to use up2date/yum anymore on that system as it'll likely wipe out or change things your packages talk to which could do anything from make your packages act weird, not work, or completely bork your system depending on what's involved.
  • Zealous
  • Guru
  • Guru
  • User avatar
  • Posts: 1244
  • Loc: Sydney

Post 3+ Months Ago

this213 wrote:
it's fine to compile your own rpms on the server, you may see some optimization from it - but you should be creating rpms and not installing from source. If you do install packages from source, you won't want to use up2date/yum anymore on that system as it'll likely wipe out or change things your packages talk to which could do anything from make your packages act weird, not work, or completely bork your system depending on what's involved.


interesting, i have not been able to get ffmpeg to work with my clipbucket site for a while for HD encoding and so been wondering if it has been installed incorrectly. i mite need to look into that. cheers

Post Information

  • Total Posts in this topic: 6 posts
  • Users browsing this forum: No registered users and 37 guests
  • You cannot post new topics in this forum
  • You cannot reply to topics in this forum
  • You cannot edit your posts in this forum
  • You cannot delete your posts in this forum
  • You cannot post attachments in this forum
 
cron
 

© 1998-2014. Ozzu® is a registered trademark of Unmelted, LLC.