• Bug#258988: gmime2.1_2.1.7-1(ia64/unstable): FTBFS: 'Scan failed'

    From Steve Langasek@1:229/2 to All on Fri Aug 13 11:00:27 2004
    From: [email protected]

    severity 258988 important
    thanks

    Starting program: /tmp/gmime2.1-2.1.7/docs/reference/.libs/lt-gmime-scan [Thread debugging using libthread_db enabled]
    [New Thread 16384 (LWP 19301)]

    Program received signal SIGSEGV, Segmentation fault.
    [Switching to Thread 16384 (LWP 19301)]
    g_type_test_flags (type=81520, flags=0) at gtype.c:423
    423 gtype.c: No such file or directory.
    in gtype.c

    I'd suggest finding a libtool person to help you debug this further.

    This is not a libtool problem -- the lt-gmime-scan binary is a simple
    ELF executable being built by the package, which is linked against
    libgobject.

    My guess is that this program, like so many others(!) that link against libgobject, is engaging in cast abuse that results in a truncated
    64-bit pointer.

    This doesn't look like a serious bug, though, as gmime2.1 has never
    built on ia64. If the problem turns out to be in another library (I
    don't see any references to g_type_test_flags in the gmime2.1 source),
    it may be a serious bug in that package.

    --
    Steve Langasek
    postmodern programmer

    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.2.5 (GNU/Linux)

    iD8DBQFBHHrnKN6ufymYLloRAiOgAJ49Hcmbovt4lygqYcJkGS8OU4lZBACgiOQR C7ruzLCqtXgNOLgdLEAJEl8=
    =GL4h
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)