Your message dated Sat, 23 Aug 2008 19:50:17 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Re: pwlib-titan needs to be binNMU'd on sparc
has caused the Debian Bug report #475601,
regarding openh323-titan_1.19.1~dfsg-4(sparc/unstable): FTBFS: segfaults during 
build on on sparc
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
475601: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=475601
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: openh323-titan
Version: 1.19.1~dfsg-4
Severity: serious

There was an error while trying to autobuild your package:

> Automatic build of openh323-titan_1.19.1~dfsg-4 on lebrun by sbuild/sparc 98
> Build started at 20080411-2311

[...]

> ** Using build dependencies supplied by package:
> Build-Depends: autotools-dev, binutils (>= 2.17), debhelper (>= 5), doxygen, 
> dpatch (>= 1.11), dpkg-dev (>= 1.13.19), libgsm1-dev (>= 1.0.10-11), 
> libpt-1.11.2-dev (>= 1.11.2~), libsasl2-dev, libspeex-dev (>= 1.1.11), 
> libssl-dev

[...]

> /usr/share/pwlib//include/ptlib/notifier.h:42: warning: the address of 'obj' 
> will always evaluate as 'true'
> g++ -o obj_linux_sparc_d/simph323 -g    -L/usr/lib 
> -L/build/buildd/openh323-titan-1.19.1~dfsg/lib/debug   
> ./obj_linux_sparc_d/main.o -lopenh323  -lpt  -lldap -llber -lldap_r  
> -lpthread -lsasl2 -lssl -lcrypto -lexpat -lSDL -lresolv -ldl 
> make[2]: Leaving directory 
> `/build/buildd/openh323-titan-1.19.1~dfsg/samples/simple'
> make[1]: Leaving directory 
> `/build/buildd/openh323-titan-1.19.1~dfsg/samples/simple'
> if (samples/simple/obj_*_d/simph323 --help >/dev/null);then \
>               echo shared debug simph323 incorrectly compiled static; false;\
>       else \
>               echo shared debug simph323 correctly compiled non-static; \
>       fi
> samples/simple/obj_linux_sparc_d/simph323: error while loading shared 
> libraries: libopenh323.so.1.19.1: cannot open shared object file: No such 
> file or directory
> shared debug simph323 correctly compiled non-static
> LD_LIBRARY_PATH=/build/buildd/openh323-titan-1.19.1~dfsg/lib/debug 
> samples/simple/obj_*_d/simph323 --help >/dev/null
> /bin/sh: line 1: 28001 Segmentation fault      
> LD_LIBRARY_PATH=/build/buildd/openh323-titan-1.19.1~dfsg/lib/debug 
> samples/simple/obj_*_d/simph323 --help >/dev/null
> make: *** [build-arch-stamp] Error 139
> dpkg-buildpackage: failure: debian/rules build gave error exit status 2

A full build log can be found at:
http://buildd.debian.org/build.php?arch=sparc&pkg=openh323-titan&ver=1.19.1~dfsg-4




--- End Message ---
--- Begin Message ---
On Sat, Aug 23, 2008 at 08:14:10PM +0100, Jurij Smakov wrote:

> It appears that pwlib-titan version currently in unstable got 
> miscompiled on sparc somehow, that's currently causing RC build 
> failures of gnugk (#478502, note that this fails on a number of 
> architectures, so other people should test whether rebuilding 
> pwlib-titan on failing arches fixes it) and openh323-titan (#475601). 
> I have rebuilt pwlib-titan with the current sid toolchain, installed 
> the resulting packages in the sid chroot and was able to successfully 
> build both gnugk and openh323-titan. Please binNMU pwlib-titan on 
> sparc (or let me know if I should do it myself), that should fix two 
> outstanding RC bugs.

BinNMU scheduled; gnugk and openh323-titan given back with dep-waits set.

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.
Ubuntu Developer                                    http://www.debian.org/
[EMAIL PROTECTED]                                     [EMAIL PROTECTED]


--- End Message ---

Reply via email to