Bugzilla Bug 38614

A while back I submitted an ebuild for my program Sussen.  I noticed it hadn't
been updated in a while.  Here are updated ebuilds.  

Note that Sussen no longer has anything to do with Nessus.  The software is
still under development though some features are missing or incomplete.   

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

Created an attachment (id=24028) [edit]
sussen-0.8.ebuild

Created an attachment (id=24029) [edit]
sussen-plugins

Created an attachment (id=24030) [edit]
sussen-sensor-0.3.ebuild

Created an attachment (id=24035) [edit]
sussen-0.8.ebuild

Added depend for sussen-plugins

Created an attachment (id=24036) [edit]
sussen-sensor-0.3.ebuild

Added depend on sussen-plugins

It would be really nice to see these updated to latest rev (sussen - 0.9
susses-plugins 0.4.1 and sussen-sensor - 0.4) and actually put in to portage. 
Thanks!

*** Bug 36310 has been marked as a duplicate of this bug. ***

Thanks netmon guys, version for core is 0.9, and for the extras is 0.4.

Created an attachment (id=46119) [edit]
sussen ebuild

Created an attachment (id=46120) [edit]
sussen-tests ebuild

Updating ebuilds for Sussen 0.10 release.

Any idea what causes this:

checking for ar... ar
checking for i686-pc-linux-gnu-ranlib... no
checking for ranlib... ranlib
checking for i686-pc-linux-gnu-strip... no
checking for strip... strip
checking for correct ltmain.sh version... no

*** Gentoo sanity check failed! ***
*** libtool.m4 and ltmain.sh have a version mismatch! ***
*** (libtool.m4 = 1.5.10, ltmain.sh = 1.5.2) ***

Please run:

  libtoolize --copy --force

if appropriate, please contact the maintainer of this
package (or your distribution) for help.

+ diefunc econf 447 1 'econf failed'
+ local funcname=econf lineno=447 exitcode=1
+ shift 3
+ echo

+ echo '!!! ERROR: net-analyzer/sussen-0.10 failed.'
!!! ERROR: net-analyzer/sussen-0.10 failed.
+ echo '!!! Function econf, Line 447, Exitcode 1'
!!! Function econf, Line 447, Exitcode 1
+ echo '!!! econf failed'
!!! econf failed
+ echo '!!! If you need support, post the topmost build error, NOT this status message.'
!!! If you need support, post the topmost build error, NOT this status message.
+ echo

+ exit 1
dan@frog sussen $ emerge info
Portage 2.0.51-r8 (default-linux/x86/2004.3, gcc-3.4.3, glibc-2.3.4.20040808-r1, 2.6.10-gentoo-r2 i686)
=================================================================
System uname: 2.6.10-gentoo-r2 i686 AMD Athlon(tm) XP 1900+
Gentoo Base System version 1.4.16
Python:              dev-lang/python-2.3.4 [2.3.4 (#1, Oct 24 2004, 08:06:09)]
distcc 2.16 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled]
ccache version 2.3 [enabled]
dev-lang/python:     2.3.4
sys-devel/autoconf:  2.59-r5
sys-devel/automake:  1.8.5-r1
sys-devel/binutils:  2.15.90.0.1.1-r3
sys-devel/libtool:   1.5.2-r7
virtual/os-headers:  2.6.8.1-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-pipe"
CHOST="i686-pc-linux-gnu"

I think it's just the libtool version.  I'm running 1.5.10-r2.  Maybe try
doing:

# echo 'sys-devel/libtool ~x86' > /etc/portage/package.keywords
# emerge libtool
# cd sussen-0.10
# ./configure
# make

Here is the rest of my emerge info, looks mostly the same:

Portage 2.0.51-r8 (default-linux/x86/2004.3, gcc-3.4.3,
glibc-2.3.4.20041102-r0, 2.6.10-gentoo-r4 i686)
=================================================================
System uname: 2.6.10-gentoo-r4 i686 Intel(R) Pentium(R) 4 CPU 2.80GHz
Gentoo Base System version 1.6.8
Python:              dev-lang/python-2.2.3-r5,dev-lang/python-2.3.4 [2.3.4 (#1,
Aug  4 2004, 19:32:58)]
ccache version 2.3 [enabled]
dev-lang/python:     2.2.3-r5, 2.3.4
sys-devel/autoconf:  2.59-r6, 2.13
sys-devel/automake:  1.8.5-r2, 1.5, 1.4_p6, 1.6.3, 1.7.9, 1.9.4
sys-devel/binutils:  2.15.92.0.2-r2
sys-devel/libtool:   1.5.10-r2
virtual/os-headers:  2.6.8.1-r2
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CFLAGS="-march=pentium4 -O2 -pipe"
CHOST="i686-pc-linux-gnu"

Fixed.