Package: autogen
Version: 1:5.7.2-1
Severity: serious
Justification: no longer builds from source

autogen does not build on Alpha:
[...]
FAIL: license.test
[...]
===========================================
1 of 34 tests failed
Please report to [EMAIL PROTECTED]
===========================================

Full log at
http://buildd.debian.org/fetch.php?&pkg=autogen&ver=1%3A5.7.3-1&arch=alpha&stamp=1131841737&file=log&as=raw

The reason is that autogen segfaults on this example.

juist:/tmp/autogen-5.7.3/agen5/test/FAILURES# ../../autogen -b license --no-def 
-T license.tpl
Segmentation fault (core dumped)

The backtrace is not very helpful, unfortunately:

juist:/tmp/autogen-5.7.3/agen5/test/FAILURES# gdb ../../.libs/lt-autogen        
GNU gdb 6.3.90_20051119-debian
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "alpha-linux-gnu"...Using host libthread_db library 
"/lib/libthread_db.so.1".

(gdb) r -b license --no-def -T license.tpl
Starting program: /tmp/autogen-5.7.3/agen5/.libs/lt-autogen -b license --no-def 
-T license.tpl
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 27322)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 27322)]
0x0000020000008a68 in _dl_rtld_di_serinfo () from /lib/ld-linux.so.2
(gdb) bt
#0  0x0000020000008a68 in _dl_rtld_di_serinfo () from /lib/ld-linux.so.2
#1  0x0000020000008efc in _dl_rtld_di_serinfo () from /lib/ld-linux.so.2
#2  0x000002000000c540 in _dl_rtld_di_serinfo () from /lib/ld-linux.so.2
#3  0x000002000000c058 in _dl_rtld_di_serinfo () from /lib/ld-linux.so.2
#4  0x000000012001a9fc in ag_scm_license ()
#5  0x00000001200930b0 in ?? ()
warning: Hit heuristic-fence-post without finding enclosing function for 
address 0x1200930b0
This warning occurs if you are debugging a function without any symbols
(for example, in a stripped executable).  In that case, you may wish to
increase the size of the search with the `set heuristic-fence-post' command.

Otherwise, you told GDB there was a function where there isn't one, or
(more likely) you have encountered a bug in GDB.
#6  0x00000001200930b0 in ?? ()
warning: Hit heuristic-fence-post without finding enclosing function for 
address 0x1200930b0
Previous frame identical to this frame (corrupt stack?)
(gdb) 

It also fails with autogen 1:5.7.2-1 from sid:

[EMAIL 
PROTECTED]:/var/cache/pbuilder/build/5817/tmp/autogen-5.7.3/agen5/test/FAILURES#
 autogen -b license --no-def -T license.tpl
AutoGen aborting on signal 10 (Bus error) in state LOAD_TPL
processing template NULL file name
            on line 0
       for function pseudo-macro (-1)
zsh: abort (core dumped)  autogen -b license --no-def -T license.tpl

Interestingly, the package builds OK outside of pbuilder. The problem
seems to be somewhat volatile.


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: alpha
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.13.2
Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages autogen depends on:
ii  guile-1.6-libs                1.6.7-1.1  Main Guile libraries
ii  libc6.1                       2.3.5-8    GNU C Library: Shared libraries an
ii  libguile-ltdl-1               1.6.7-1.1  Guile's patched version of libtool
ii  libopts25                     1:5.7.2-1  automated option processing librar
ii  libopts25-dev                 1:5.7.2-1  automated option processing librar
ii  libqthreads-12                1.6.7-1.1  QuickThreads library for Guile
ii  libxml2                       2.6.22-2   GNOME XML library
ii  zlib1g                        1:1.2.3-8  compression library - runtime

autogen recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to