severity 405991 important
thanks

On Sun, Jan 07, 2007 at 08:04:19PM +0100, Julien Danjou wrote:
> There was a problem while autobuilding your package:
> > Automatic build of lua-expat_1.0.2-2 on nasya by sbuild/sparc 0.50
> > Build started at 20070107-1956
> ...
> > pre-app-dynamic-test-hook
> > ********************** app dynamic **************************
> > libtool --silent --tag=CC --mode=execute -dlopen liblua5.1-expat.la ldd 
> > ./.libs/app
> >     liblua5.1.so.0 => /usr/lib/liblua5.1.so.0 (0x700f8000)
> >     liblua5.1-expat.so.0 => 
> > /build/buildd/lua-expat-1.0.2/.libs/liblua5.1-expat.so.0 (0x70000000)
> >     libc.so.6 => /lib/libc.so.6 (0x7012c000)
> >     libm.so.6 => /lib/libm.so.6 (0x70018000)
> >     libdl.so.2 => /lib/libdl.so.2 (0x700ac000)
> >     libexpat.so.1 => /usr/lib/libexpat.so.1 (0x70260000)
> >     /lib/ld-linux.so.2 (0x700cc000)
> >     libpthread.so.0 => /lib/libpthread.so.0 (0x70284000)
> > libtool --silent --tag=CC --mode=execute -dlopen liblua5.1-expat.la ./app 
> > tests/test.lua
> > app.c: tests/test.lua:10: attempt to index global 'lxp' (a nil value)
> > make[2]: *** [test-app-dynamic] Error 1
> > make[2]: Leaving directory `/build/buildd/lua-expat-1.0.2'
> > make[1]: *** [test] Error 1
> > make[1]: Leaving directory `/build/buildd/lua-expat-1.0.2'
> > make: *** [debian/stamp-makefile-check] Error 2
> > ******************************************************************************
> > Build finished at 20070107-1957
> > FAILED [dpkg-buildpackage died]

I can't reproduce this failure on i386 or amd64 in etch or sid, so I don't
think there is an RC bug in lua-expat.  However, if lua doesn't work right
on sparc, that could point to an RC bug in lua itself, so this warrants
further investigation.

Thanks,
-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
[EMAIL PROTECTED]                                   http://www.debian.org/


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

Reply via email to