Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!

Full Text Bug Listing

No stable version available at the moment on amd64.

I installed sys-fs/inotify-tools-3.11 and have no problems.

cc-ing archs

On x86 it fails on make check

make[5]: Entering directory
`/var/tmp/paludis/sys-fs/inotify-tools-3.11/work/inotify-tools-3.11'
make[5]: Leaving directory
`/var/tmp/paludis/sys-fs/inotify-tools-3.11/work/inotify-tools-3.11'
event_to_str: test begin
event_to_str: test end
event_to_str_sep: test begin
event_to_str_sep: test end
str_to_event: test begin
str_to_event: test end
str_to_event_sep: test begin
str_to_event_sep: test end
basic_watch_info: test begin
basic_watch_info: test end
watch_limit: test begin
watch_limit: Warning, this test may take a while
test.c:271 Test 'watch_limit' failed: Actual (sbrk(0)): 136425472, Expected
(sbrk_ptr): 136384512
tst_inotifytools_snprintf: test begin
tst_inotifytools_snprintf: test end
Out of 145208 tests, 145207 succeeded and 1 failed.
FAIL: test
=====================================
1 of 1 tests failed
Please report to rohan@mcgovern.id.au
=====================================
make[4]: *** [check-TESTS] Error 1
make[4]: Leaving directory
`/var/tmp/paludis/sys-fs/inotify-tools-3.11/work/inotify-tools-3.11/libinotifytools/src'
make[3]: *** [check-am] Error 2
make[3]: Leaving directory
`/var/tmp/paludis/sys-fs/inotify-tools-3.11/work/inotify-tools-3.11/libinotifytools/src'
make[2]: *** [check-recursive] Error 1
make[2]: Leaving directory
`/var/tmp/paludis/sys-fs/inotify-tools-3.11/work/inotify-tools-3.11/libinotifytools/src'
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory
`/var/tmp/paludis/sys-fs/inotify-tools-3.11/work/inotify-tools-3.11/libinotifytools'
make: *** [check-recursive] Error 1

!!! ERROR in sys-fs/inotify-tools-3.11:
!!! In src_test at line 29
!!! make check failed


Paludis build information:
    Compiler:
        CXX:                   i686-pc-linux-gnu-g++ 4.1.2 (Gentoo 4.1.2)
        CXXFLAGS:              -O2 -march=pentium-m -fomit-frame-pointer -pipe
        LDFLAGS:               
        DATE:                  2007-11-06T15:48:32+0100

Package information:
        app-admin/eselect-compiler: (none)
        app-shells/bash:       3.2_p17
        dev-java/java-config:  1.3.7, 2.0.33-r1
        dev-lang/python:       2.4.4-r6
        dev-python/pycrypto:   2.0.1-r6
        dev-util/ccache:       (none)
        dev-util/confcache:    (none)
        sys-apps/baselayout:   1.12.9-r2
        sys-apps/sandbox:      1.2.18.1-r2
        sys-devel/autoconf:    2.13, 2.61-r1
        sys-devel/automake:    1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3,
1.9.6-r2, 1.10
        sys-devel/binutils:    2.18-r1
        sys-devel/gcc-config:  1.3.16
        sys-devel/libtool:     1.5.24
        virtual/os-headers:    2.6.22-r2

same for amd64, fails at make check,

test.c:271 Test 'watch_limit' failed: Actual (sbrk(0)): 8781824, Expected
(sbrk_ptr): 8757248

(In reply to comment #1)
> cc-ing archs
> 

un-cc-ing amd64, add us back when it's fixed

Wolfram, could you please look into the failures?

I have tried to contact Rohan, will let you know when I got his attention ;)

Wow, that was quicker than I hoped ;)
He will take care about it next weekend (maybe earlier).
Will keep you up2date.

--8<--
24 November 2007: inotify-tools 3.12 released. Changes:
* Fix: inability to free memory allocated by inotifytools, and bogus memory
  leak check (causing `make check' to fail on some systems).
* Fix: spurious warning when the `--format' option is given to inotifywait.
* Fix: inotifywait fails to watch newly created directories when recursively
  watching a symlink to a directory.
--8<--

3.12 is in CVS.

So, either you ignore the "make check" results, or you wait until you can
consider 3.12 for stable marking :)

amd64 stable

But.. entire src_compile() should be removed since it only does econf, emake
without arguments?

(In reply to comment #9)
> amd64 stable
> 
> But.. entire src_compile() should be removed since it only does econf, emake
> without arguments?

Yep, you're right.
Either I can do it, or x86 can do it when they touch the ebuild anyway ;)

x86 stable, so closing