Your message dated Sun, 31 Aug 2008 12:30:28 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#494930: gnash_0.8.3-5(sparc/unstable): FTBFS on sparc
has caused the Debian Bug report #494930,
regarding gnash_0.8.3-5(sparc/unstable): FTBFS 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.)
--
494930: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=494930
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: gnash
Version: 0.8.3-5
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of gnash_0.8.3-5 on lebrun by sbuild/sparc 98
> Build started at 20080813-0048
[...]
> ** Using build dependencies supplied by package:
> Build-Depends: dpkg-dev (>= 1.13.19), debhelper (>= 4.0.0), quilt, autoconf,
> dh-buildinfo, automake1.9 | automake, libtool, libltdl3-dev, help2man,
> libxmu-dev, dejagnu, autotools-dev, libboost-dev, libboost-thread-dev,
> libxml2-dev, libjpeg-dev, libboost-date-time-dev, libboost-filesystem-dev,
> libpng12-dev | libpng-dev, libagg-dev, libgstreamer0.10-dev, libkonq4-dev,
> libpango1.0-dev | pango-devel, libgtkglext1-dev, libmad0-dev,
> libcurl4-gnutls-dev | libcurl3-gnutls-dev | libcurl4-openssl-dev |
> libcurl3-openssl-dev, libcaca-dev, libavcodec-dev, libavformat-dev,
> libming-dev, libming-util, libgstreamer-plugins-base0.10-dev, libqt3-mt-dev
> (>= 3:3.3.8), libboost-serialization-dev, python
[...]
> /usr/include/boost/detail/sp_counted_impl.hpp: In member function 'void
> boost::detail::sp_counted_impl_pd<P, D>::dispose() [with P =
> boost::io::basic_altstringbuf<char, std::char_traits<char>,
> std::allocator<char> >*, D = boost::io::basic_oaltstringstream<char,
> std::char_traits<char>, std::allocator<char> >::No_Op]':
> /usr/include/boost/detail/sp_counted_impl.hpp:146: internal compiler error:
> Segmentation fault
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <file:///usr/share/doc/gcc-4.3/README.Bugs> for instructions.
> make[4]: *** [string.lo] Error 1
> make[4]: Leaving directory `/build/buildd/gnash-0.8.3/tmp.agg/server/asobj'
> make[3]: *** [all-recursive] Error 1
> make[3]: Leaving directory `/build/buildd/gnash-0.8.3/tmp.agg/server'
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory `/build/buildd/gnash-0.8.3/tmp.agg'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory `/build/buildd/gnash-0.8.3/tmp.agg'
> make: *** [build-stamp] Error 2
> 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=gnash&ver=0.8.3-5
--- End Message ---
--- Begin Message ---
Hi,
On Sat Aug 30, 2008 at 21:15:12 +0200, Martin Zobel-Helas wrote:
> Hi,
>
> On Sat Aug 30, 2008 at 20:54:51 +0200, Petter Reinholdtsen wrote:
> > This gnash build issue on sparc keep the latest gnash package out of
> > Lenny. Is there work going on to fix it? One idea to work around the
> > GCC bug is to use -O0 on sparc to disable optimization, hopefully
> > avoiding the compiler bug.
>
> i am looking into it ATM as sparc buildd maintainer and porter.
the latest hand-build of gnash on sparc worked out okay. thus closing
the bug.
Greetings
Martin
--
Martin Zobel-Helas <[EMAIL PROTECTED]> | Debian Release Team Member
Debian & GNU/Linux Developer | Debian Listmaster
Public key http://zobel.ftbfs.de/5d64f870.asc - KeyID: 5D64 F870
GPG Fingerprint: 5DB3 1301 375A A50F 07E7 302F 493E FB8E 5D64 F870
--- End Message ---
