Debian Bug report logs - #476303
iceweasel: ftbfs on armel: temporary object destruction order

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Jon Dowland <jon+bts@alcopop.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: iceweasel: ftbfs on armel: temporary object destruction order

Date: Fri, 04 Apr 2008 19:04:08 +0100

Package: iceweasel
Version: 3.0~b5-1
Severity: normal

...
checking for unwind.h... yes
checking for _Unwind_Backtrace... yes
checking for gcc -pipe support... yes
checking whether compiler supports -Wno-long-long... yes
checking whether C compiler supports -fprofile-generate... yes
checking for correct temporary object destruction order... no
configure: error: Your compiler does not follow the C++ specification 
for temporary object destruction order.
make: *** [config.status] Error 1
dpkg-buildpackage: failure: debian/rules build gave error exit status 2



-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: armel (armv5tel)

Kernel: Linux 2.6.24-1-iop32x
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Message #10 received at 474281@bugs.debian.org (full text, mbox, reply):

From: Jon Dowland <jon+bts@alcopop.org>

To: 474281@bugs.debian.org

Subject: Re: Bug#474281: Acknowledgement (iceweasel: ftbfs on armel: temporary object destruction order)

Date: Fri, 4 Apr 2008 19:22:07 +0100

[Message part 1 (text/plain, inline)]

config.log attached.

ii  g++                             4:4.3.0-3                  The GNU
ii  g++-4.3                         4.3.0-2                    The GNU
ii  gcc                             4:4.3.0-3                  The GNU C
ii  gcc-4.2-base                    4.2.3-3                    The GNU
ii  gcc-4.3                         4.3.0-2                    The GNU C
ii  gcc-4.3-base                    4.3.0-2                    The GNU

[config.log (text/plain, attachment)]

Message #15 received at 474281@bugs.debian.org (full text, mbox, reply):

From: Jon Dowland <jon@alcopop.org>

To: control@bugs.debian.org

Cc: 474281@bugs.debian.org

Subject: severity of 474281 is normal

Date: Fri, 04 Apr 2008 19:29:16 +0100

# Automatically generated email from bts, devscripts version 2.10.20
# I forgot armel isn't a released arch yet
severity 474281 normal

Message #22 received at 474281@bugs.debian.org (full text, mbox, reply):

From: Mike Hommey <mh@glandium.org>

To: Jon Dowland <jon+bts@alcopop.org>, 474281@bugs.debian.org

Subject: Re: Bug#474281: Acknowledgement (iceweasel: ftbfs on armel: temporary object destruction order)

Date: Fri, 4 Apr 2008 21:31:27 +0200

On Fri, Apr 04, 2008 at 07:22:07PM +0100, Jon Dowland wrote:
> configure:17706: c++ -o conftest  -fno-strict-aliasing -fshort-wchar -pthread -pipe   -lpthread -Wl,--as-needed conftest.C -ldl -lm  1>&5
> /usr/bin/ld: ERROR: /tmp/ccef8aU1.o: Conflicting definitions of wchar_t

WTF?!? There's not even wchar_t in the source

> /usr/bin/ld: failed to merge target specific data of file /tmp/ccef8aU1.o
> collect2: ld returned 1 exit status
> configure: failed program was:
> #line 17686 "configure"
> #include "confdefs.h"
>  class A {
>              public:  A(int& x) : mValue(x) {}
>                       ~A() { mValue--; }
>                       operator char**() { return 0; }
>              private:  int& mValue;
>              };
>              void func(char **arg) {}
>              int m=2;
>              void test() {
>                   func(A(m));
>                   if (m==1) m = 0;
>              }
>              int main() {
>                  test();
>                  return(m);
>              }
>              

Message #27 received at 474281@bugs.debian.org (full text, mbox, reply):

From: Jon Dowland <jon+bts@alcopop.org>

To: Mike Hommey <mh@glandium.org>

Cc: 474281@bugs.debian.org

Subject: Re: Bug#474281: Acknowledgement (iceweasel: ftbfs on armel: temporary object destruction order)

Date: Fri, 4 Apr 2008 20:50:31 +0100

On Fri, Apr 04, 2008 at 09:31:27PM +0200, Mike Hommey wrote:
> On Fri, Apr 04, 2008 at 07:22:07PM +0100, Jon Dowland wrote:
> > configure:17706: c++ -o conftest  -fno-strict-aliasing -fshort-wchar -pthread -pipe   -lpthread -Wl,--as-needed conftest.C -ldl -lm  1>&5
> > /usr/bin/ld: ERROR: /tmp/ccef8aU1.o: Conflicting definitions of wchar_t
> 
> WTF?!? There's not even wchar_t in the source

I know bugger all about c++ but I'm plodding on, since there's no
experimental buildd for armel yet.

19:32 < suihkulokki> Jon: The problem is -fshort-wchar option, you would
need to hack the configure scripts to not enable it

I'm just trying to disable that chunk of stuff in configure.in and
regenerate the makefiles, then try again.


-- 
Jon Dowland

Message #32 received at 474281@bugs.debian.org (full text, mbox, reply):

From: Mike Hommey <mh@glandium.org>

To: Jon Dowland <jon+bts@alcopop.org>

Cc: 474281@bugs.debian.org

Subject: Re: Bug#474281: Acknowledgement (iceweasel: ftbfs on armel: temporary object destruction order)

Date: Fri, 4 Apr 2008 22:08:28 +0200

On Fri, Apr 04, 2008 at 08:50:31PM +0100, Jon Dowland wrote:
> On Fri, Apr 04, 2008 at 09:31:27PM +0200, Mike Hommey wrote:
> > On Fri, Apr 04, 2008 at 07:22:07PM +0100, Jon Dowland wrote:
> > > configure:17706: c++ -o conftest  -fno-strict-aliasing -fshort-wchar -pthread -pipe   -lpthread -Wl,--as-needed conftest.C -ldl -lm  1>&5
> > > /usr/bin/ld: ERROR: /tmp/ccef8aU1.o: Conflicting definitions of wchar_t
> > 
> > WTF?!? There's not even wchar_t in the source
> 
> I know bugger all about c++ but I'm plodding on, since there's no
> experimental buildd for armel yet.
> 
> 19:32 < suihkulokki> Jon: The problem is -fshort-wchar option, you would
> need to hack the configure scripts to not enable it
> 
> I'm just trying to disable that chunk of stuff in configure.in and
> regenerate the makefiles, then try again.

On the other hand, it builds this correctly:
configure:8114: checking for compiler -fshort-wchar option
configure:8128: c++ -c  -fno-strict-aliasing -fshort-wchar   conftest.C 1>&5

This being generated by the following configure.in snippet:
        [AC_TRY_COMPILE([#include <stddef.h>
                         $configure_static_assert_macros],
                        [CONFIGURE_STATIC_ASSERT(sizeof(wchar_t) == 2);
                         CONFIGURE_STATIC_ASSERT((wchar_t)-1 > (wchar_t) 0)],
                        ac_cv_have_usable_wchar_option_v2="yes",
                        ac_cv_have_usable_wchar_option_v2="no")])

This snippet is responsible for the addition of -fshort-wchar in the CXX_FLAGS in
what is failing for you.

Mike

Message #39 received at 474281@bugs.debian.org (full text, mbox, reply):

From: Mike Hommey <mh@glandium.org>

To: Jon Dowland <jon+bts@alcopop.org>

Cc: 474281@bugs.debian.org

Subject: Re: Bug#474281: Acknowledgement (iceweasel: ftbfs on armel: temporary object destruction order)

Date: Fri, 4 Apr 2008 22:23:03 +0200

On Fri, Apr 04, 2008 at 10:08:28PM +0200, Mike Hommey wrote:
> On Fri, Apr 04, 2008 at 08:50:31PM +0100, Jon Dowland wrote:
> > On Fri, Apr 04, 2008 at 09:31:27PM +0200, Mike Hommey wrote:
> > > On Fri, Apr 04, 2008 at 07:22:07PM +0100, Jon Dowland wrote:
> > > > configure:17706: c++ -o conftest  -fno-strict-aliasing -fshort-wchar -pthread -pipe   -lpthread -Wl,--as-needed conftest.C -ldl -lm  1>&5
> > > > /usr/bin/ld: ERROR: /tmp/ccef8aU1.o: Conflicting definitions of wchar_t
> > > 
> > > WTF?!? There's not even wchar_t in the source
> > 
> > I know bugger all about c++ but I'm plodding on, since there's no
> > experimental buildd for armel yet.
> > 
> > 19:32 < suihkulokki> Jon: The problem is -fshort-wchar option, you would
> > need to hack the configure scripts to not enable it
> > 
> > I'm just trying to disable that chunk of stuff in configure.in and
> > regenerate the makefiles, then try again.
> 
> On the other hand, it builds this correctly:
> configure:8114: checking for compiler -fshort-wchar option
> configure:8128: c++ -c  -fno-strict-aliasing -fshort-wchar   conftest.C 1>&5
> 
> This being generated by the following configure.in snippet:
>         [AC_TRY_COMPILE([#include <stddef.h>
>                          $configure_static_assert_macros],
>                         [CONFIGURE_STATIC_ASSERT(sizeof(wchar_t) == 2);
>                          CONFIGURE_STATIC_ASSERT((wchar_t)-1 > (wchar_t) 0)],
>                         ac_cv_have_usable_wchar_option_v2="yes",
>                         ac_cv_have_usable_wchar_option_v2="no")])
> 
> This snippet is responsible for the addition of -fshort-wchar in the CXX_FLAGS in
> what is failing for you.

And both tests have not changed for a while, and xulrunner build fine on
armel in unstable [1]

Could you try to use the same toolchain as when xulrunner was built ?
i.e. gcc-4.2_4.2.3-2 g++-4.2_4.2.3-2 binutils_2.18.1~cvs20080103-1

Mike

1.  http://buildd.debian.org/fetch.cgi?pkg=xulrunner;ver=1.8.1.12-5;arch=armel;stamp=1206621388

Message #44 received at 474281@bugs.debian.org (full text, mbox, reply):

From: Riku Voipio <riku.voipio@iki.fi>

To: Mike Hommey <mh@glandium.org>

Cc: Jon Dowland <jon+bts@alcopop.org>, 474281@bugs.debian.org

Subject: Re: Bug#474281: Acknowledgement (iceweasel: ftbfs on armel: temporary object destruction order)

Date: Sat, 5 Apr 2008 00:13:45 +0300

On Fri, Apr 04, 2008 at 07:22:07PM +0100, Jon Dowland wrote:
> configure:17706: c++ -o conftest  -fno-strict-aliasing -fshort-wchar -pthread -pipe   -lpthread -Wl,--as-needed conftest.C -ldl -lm  1>&5
> /usr/bin/ld: ERROR: /tmp/ccef8aU1.o: Conflicting definitions of wchar_t

Notice the error happens at linking time

> On the other hand, it builds this correctly:
> configure:8114: checking for compiler -fshort-wchar option
> configure:8128: c++ -c  -fno-strict-aliasing -fshort-wchar   conftest.C 1>&5

...and 'c++ -c' specifically does _not_ link.

$ cat test.c
#include <stddef.h>
#include <wchar.h>

int main() {
; return 0; }
all6500-2:~/icew
$ c++ -c -fno-strict-aliasing -fshort-wchar test.c
$ echo $?
0
$ c++  -fno-strict-aliasing -fshort-wchar test.c
/usr/bin/ld: ERROR: /tmp/ccKVwN1s.o: Conflicting definitions of wchar_t
/usr/bin/ld: failed to merge target specific data of file
/tmp/ccKVwN1s.o
collect2: ld returned 1 exit status

> And both tests have not changed for a while, and xulrunner build fine on
> armel in unstable [1]

FWIW xulrunner/iceweasel based on FF 2.0 does not work (even if it
compiles) on armel. That's why we are looking at getting FF3.0
compiled. The nokia internet tablets are based on armel and and
have browser based on FF3.0 alpha, so it would seem more feasible
to get FF3.0 working than backporting the support to 2.0..

> Could you try to use the same toolchain as when xulrunner was built ?
> i.e. gcc-4.2_4.2.3-2 g++-4.2_4.2.3-2 binutils_2.18.1~cvs20080103-1

A quick test confirms, test.c compiles fine with g++-4.2, but fails with
g++-4.3.

Message #49 received at 474281@bugs.debian.org (full text, mbox, reply):

From: Mike Hommey <mh@glandium.org>

To: Riku Voipio <riku.voipio@iki.fi>, 474281@bugs.debian.org

Cc: Jon Dowland <jon+bts@alcopop.org>

Subject: Re: Bug#474281: Acknowledgement (iceweasel: ftbfs on armel: temporary object destruction order)

Date: Sat, 5 Apr 2008 10:25:45 +0200

On Sat, Apr 05, 2008 at 12:13:45AM +0300, Riku Voipio wrote:
> On Fri, Apr 04, 2008 at 07:22:07PM +0100, Jon Dowland wrote:
> > configure:17706: c++ -o conftest  -fno-strict-aliasing -fshort-wchar -pthread -pipe   -lpthread -Wl,--as-needed conftest.C -ldl -lm  1>&5
> > /usr/bin/ld: ERROR: /tmp/ccef8aU1.o: Conflicting definitions of wchar_t
> 
> Notice the error happens at linking time
> 
> > On the other hand, it builds this correctly:
> > configure:8114: checking for compiler -fshort-wchar option
> > configure:8128: c++ -c  -fno-strict-aliasing -fshort-wchar   conftest.C 1>&5
> 
> ...and 'c++ -c' specifically does _not_ link.
> 
> $ cat test.c
> #include <stddef.h>
> #include <wchar.h>
> 
> int main() {
> ; return 0; }
> all6500-2:~/icew
> $ c++ -c -fno-strict-aliasing -fshort-wchar test.c
> $ echo $?
> 0
> $ c++  -fno-strict-aliasing -fshort-wchar test.c
> /usr/bin/ld: ERROR: /tmp/ccKVwN1s.o: Conflicting definitions of wchar_t
> /usr/bin/ld: failed to merge target specific data of file
> /tmp/ccKVwN1s.o
> collect2: ld returned 1 exit status
> 
> > And both tests have not changed for a while, and xulrunner build fine on
> > armel in unstable [1]
> 
> FWIW xulrunner/iceweasel based on FF 2.0 does not work (even if it
> compiles) on armel. That's why we are looking at getting FF3.0
> compiled. The nokia internet tablets are based on armel and and
> have browser based on FF3.0 alpha, so it would seem more feasible
> to get FF3.0 working than backporting the support to 2.0..

It would still be nice to get the bug reports, especially considering
iceape and icedove, which i assume both build fine too, will more than
probably ship in 2.0 based versions in lenny.

> > Could you try to use the same toolchain as when xulrunner was built ?
> > i.e. gcc-4.2_4.2.3-2 g++-4.2_4.2.3-2 binutils_2.18.1~cvs20080103-1
> 
> A quick test confirms, test.c compiles fine with g++-4.2, but fails with
> g++-4.3.

Seems like a candidate for a gcc regression :-/

Mike

Message #54 received at 474281@bugs.debian.org (full text, mbox, reply):

From: Riku Voipio <riku.voipio@iki.fi>

To: Mike Hommey <mh@glandium.org>

Cc: 474281@bugs.debian.org, Jon Dowland <jon+bts@alcopop.org>

Subject: Re: Bug#474281: Acknowledgement (iceweasel: ftbfs on armel: temporary object destruction order)

Date: Wed, 9 Apr 2008 01:35:06 +0300

This bug also affect xulrunner build on unstable with gcc-4.3 now
as default:

http://buildd.debian.org/fetch.cgi?pkg=xulrunner;ver=1.8.1.13-1;arch=armel;stamp=1207348728

-snip-
configure:10281: checking for iconv in -lc
configure:10303: c++ -o conftest  -fshort-wchar -pthread   -Wl,--as-needed conftest.C -lc  -ldl -lm  1>&5
/usr/bin/ld: ERROR: /tmp/ccAhgliI.o: Conflicting definitions of wchar_t
/usr/bin/ld: failed to merge target specific data of file /tmp/ccAhgliI.o
-snip-

On Sat, Apr 05, 2008 at 10:25:45AM +0200, Mike Hommey wrote:
> On Sat, Apr 05, 2008 at 12:13:45AM +0300, Riku Voipio wrote:
> > $ cat test.c
> > #include <stddef.h>
> > #include <wchar.h>
> > 
> > int main() {
> > ; return 0; }
> > all6500-2:~/icew
> > $ c++ -c -fno-strict-aliasing -fshort-wchar test.c
> > $ echo $?
> > 0
> > $ c++  -fno-strict-aliasing -fshort-wchar test.c
> > /usr/bin/ld: ERROR: /tmp/ccKVwN1s.o: Conflicting definitions of wchar_t
> > /usr/bin/ld: failed to merge target specific data of file
> > /tmp/ccKVwN1s.o
> > collect2: ld returned 1 exit status
> > 
> > A quick test confirms, test.c compiles fine with g++-4.2, but fails with
> > g++-4.3.

> Seems like a candidate for a gcc regression :-/

Not really, gcc has just become more strict.

on arm EABI, wchar_t is "unsigned int", while -fshort-wchar enforces
"short unsigned int". One is creating code that is incompatible with
platform ABI, which the linker refuses to mix.

Message #59 received at 474281@bugs.debian.org (full text, mbox, reply):

From: Mike Hommey <mh@glandium.org>

To: Riku Voipio <riku.voipio@iki.fi>

Cc: 474281@bugs.debian.org, Jon Dowland <jon+bts@alcopop.org>

Subject: Re: Bug#474281: Acknowledgement (iceweasel: ftbfs on armel: temporary object destruction order)

Date: Wed, 9 Apr 2008 08:29:17 +0200

On Wed, Apr 09, 2008 at 01:35:06AM +0300, Riku Voipio wrote:
> Not really, gcc has just become more strict.
> 
> on arm EABI, wchar_t is "unsigned int", while -fshort-wchar enforces
> "short unsigned int". One is creating code that is incompatible with
> platform ABI, which the linker refuses to mix.

Is arm EABI the only ABI with such incompatibility ?

Mike

PS: I wonder if gcc shouldn't dump -fshort-wchar in such situation. The
option doesn't make sense if it will always lead to this error.

Message #64 received at 474281@bugs.debian.org (full text, mbox, reply):

From: Riku Voipio <riku.voipio@iki.fi>

To: Mike Hommey <mh@glandium.org>

Cc: 474281@bugs.debian.org, Jon Dowland <jon+bts@alcopop.org>

Subject: Re: Bug#474281: Acknowledgement (iceweasel: ftbfs on armel: temporary object destruction order)

Date: Wed, 9 Apr 2008 12:06:51 +0300

On Wed, Apr 09, 2008 at 08:29:17AM +0200, Mike Hommey wrote:
> On Wed, Apr 09, 2008 at 01:35:06AM +0300, Riku Voipio wrote:
> > on arm EABI, wchar_t is "unsigned int", while -fshort-wchar enforces
> > "short unsigned int". One is creating code that is incompatible with
> > platform ABI, which the linker refuses to mix.

> Is arm EABI the only ABI with such incompatibility ?

Good question. All other our archs seem to define wchar_t as int,
while on arm it's unsigned int. Handling signed values
on arm is slower than unsigned and negative values for wchar_t make
little point.

The gcc manpage seems to indicate that -fshort-wchar creates
ABI incompatability, and is only usefull for wine programming
(since windowsen wchar_t is unsigned short). Why in practice it's
only causing problems on arm eabi with gcc >= 4.3 is weird.

> PS: I wonder if gcc shouldn't dump -fshort-wchar in such situation. The
> option doesn't make sense if it will always lead to this error.

Theoretically it is valid option on arm eabi too, if you are not
linking against the system libraries (building kernel, bootloader or
static binaries with your own libc-like functionality ).

-- 
"rm -rf" only sounds scary if you don't have backups

Message #69 received at 474281@bugs.debian.org (full text, mbox, reply):

From: Riku Voipio <riku.voipio@iki.fi>

To: Mike Hommey <mh@glandium.org>

Cc: 474281@bugs.debian.org, Jon Dowland <jon+bts@alcopop.org>, control@bugs.debian.org

Subject: Re: Bug#474281: Acknowledgement (iceweasel: ftbfs on armel: temporary object destruction order)

Date: Tue, 15 Apr 2008 13:00:40 +0300

tags 474281 + patch
thanks

Well, if the error happens at linking stage, changing AC_TRY_COMPILE to
AC_TRY_LINK will catch it, and configure will not bother using
-short-wchar anymore.

This needs to be applied to all packages of mozilla origin and
auto(re)confed.

-- 
"rm -rf" only sounds scary if you don't have backups

Message #74 received at 474281@bugs.debian.org (full text, mbox, reply):

From: Riku Voipio <riku.voipio@iki.fi>

To: Mike Hommey <mh@glandium.org>

Cc: 474281@bugs.debian.org, Jon Dowland <jon+bts@alcopop.org>

Subject: Re: Bug#474281: Acknowledgement (iceweasel: ftbfs on armel: temporary object destruction order)

Date: Tue, 15 Apr 2008 13:01:47 +0300

[Message part 1 (text/plain, inline)]

On Tue, Apr 15, 2008 at 01:00:40PM +0300, Riku Voipio wrote:
> This needs to be applied to all packages of mozilla origin and
> auto(re)confed.

Actually add the patch..

-- 
"rm -rf" only sounds scary if you don't have backups

[mozilla.patch (text/plain, attachment)]

Message #91 received at 476303-close@bugs.debian.org (full text, mbox, reply):

From: Mike Hommey <glandium@debian.org>

To: 476303-close@bugs.debian.org

Subject: Bug#476303: fixed in xulrunner 1.8.1.14-1

Date: Fri, 18 Apr 2008 06:02:14 +0000

Source: xulrunner
Source-Version: 1.8.1.14-1

We believe that the bug you reported is fixed in the latest version of
xulrunner, which is due to be installed in the Debian FTP archive:

libmozillainterfaces-java_1.8.1.14-1_all.deb
  to pool/main/x/xulrunner/libmozillainterfaces-java_1.8.1.14-1_all.deb
libmozjs-dev_1.8.1.14-1_all.deb
  to pool/main/x/xulrunner/libmozjs-dev_1.8.1.14-1_all.deb
libmozjs0d-dbg_1.8.1.14-1_amd64.deb
  to pool/main/x/xulrunner/libmozjs0d-dbg_1.8.1.14-1_amd64.deb
libmozjs0d_1.8.1.14-1_amd64.deb
  to pool/main/x/xulrunner/libmozjs0d_1.8.1.14-1_amd64.deb
libxul-common_1.8.1.14-1_all.deb
  to pool/main/x/xulrunner/libxul-common_1.8.1.14-1_all.deb
libxul-dev_1.8.1.14-1_all.deb
  to pool/main/x/xulrunner/libxul-dev_1.8.1.14-1_all.deb
libxul0d-dbg_1.8.1.14-1_amd64.deb
  to pool/main/x/xulrunner/libxul0d-dbg_1.8.1.14-1_amd64.deb
libxul0d_1.8.1.14-1_amd64.deb
  to pool/main/x/xulrunner/libxul0d_1.8.1.14-1_amd64.deb
python-xpcom_1.8.1.14-1_amd64.deb
  to pool/main/x/xulrunner/python-xpcom_1.8.1.14-1_amd64.deb
spidermonkey-bin_1.8.1.14-1_amd64.deb
  to pool/main/x/xulrunner/spidermonkey-bin_1.8.1.14-1_amd64.deb
xulrunner-gnome-support_1.8.1.14-1_amd64.deb
  to pool/main/x/xulrunner/xulrunner-gnome-support_1.8.1.14-1_amd64.deb
xulrunner_1.8.1.14-1.diff.gz
  to pool/main/x/xulrunner/xulrunner_1.8.1.14-1.diff.gz
xulrunner_1.8.1.14-1.dsc
  to pool/main/x/xulrunner/xulrunner_1.8.1.14-1.dsc
xulrunner_1.8.1.14-1_amd64.deb
  to pool/main/x/xulrunner/xulrunner_1.8.1.14-1_amd64.deb
xulrunner_1.8.1.14.orig.tar.gz
  to pool/main/x/xulrunner/xulrunner_1.8.1.14.orig.tar.gz



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 476303@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mike Hommey <glandium@debian.org> (supplier of updated xulrunner package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Thu, 17 Apr 2008 21:08:57 +0200
Source: xulrunner
Binary: xulrunner xulrunner-gnome-support libmozjs0d libmozjs-dev libmozjs0d-dbg spidermonkey-bin libxul0d libxul-common libxul-dev libxul0d-dbg libmozillainterfaces-java python-xpcom
Architecture: source all amd64
Version: 1.8.1.14-1
Distribution: unstable
Urgency: low
Maintainer: Mike Hommey <glandium@debian.org>
Changed-By: Mike Hommey <glandium@debian.org>
Description: 
 libmozillainterfaces-java - XPCOM bindings for Java
 libmozjs-dev - Development files for the Mozilla SpiderMonkey JavaScript library
 libmozjs0d - The Mozilla SpiderMonkey JavaScript library
 libmozjs0d-dbg - Development files for the Mozilla SpiderMonkey JavaScript library
 libxul-common - Gecko engine library - common files
 libxul-dev - Development files for the Gecko engine library
 libxul0d   - Gecko engine library
 libxul0d-dbg - Development files for the Gecko engine library
 python-xpcom - XPCOM bindings for Python
 spidermonkey-bin - standalone JavaScript/ECMAScript (ECMA-262) interpreter
 xulrunner  - XUL + XPCOM application runner
 xulrunner-gnome-support - Support for GNOME in xulrunner applications
Closes: 476303
Changes: 
 xulrunner (1.8.1.14-1) unstable; urgency=low
 .
   * New security/stability upstream release (taken from upstream CVS)
   * Fixes mfsa-2008-20, also known as CVE-2008-1380.
   * debian/patches/38_armel.dpatch: Force to not use -fshort-wchar where it
     fails. Closes: #476303.
   * debian/patches/00list: Updated accordingly.
   * debian/patches/99_configure.dpatch: Updated.
Checksums-Sha1: 
 20f3a96a1a74d14a98d5658f0de46bf40b3dbbd8 1625 xulrunner_1.8.1.14-1.dsc
 88818ba13fc434dba0fcaed19bf9ecd74099dda2 40889518 xulrunner_1.8.1.14.orig.tar.gz
 52d7922f6b5cb21867db2463983c1c277fed88ee 132470 xulrunner_1.8.1.14-1.diff.gz
 b0e3047d40f4cf0eda90bb6a4c552f0140339357 192164 libmozjs-dev_1.8.1.14-1_all.deb
 2f6e9964d294cee51d11b73c8365de8ad912b06e 1206384 libxul-common_1.8.1.14-1_all.deb
 90602f3100a5b5257826f195601d9c476d42c89f 3023148 libxul-dev_1.8.1.14-1_all.deb
 164d367344f2d78263029ec4316ec35787a137a1 1343468 libmozillainterfaces-java_1.8.1.14-1_all.deb
 e921c35ebc0b62b68cb0071023d31cbd2dd9a58d 292036 xulrunner_1.8.1.14-1_amd64.deb
 4a5de329872bfe68a49f884b5b71651c90efd2f3 70394 xulrunner-gnome-support_1.8.1.14-1_amd64.deb
 de06045f2844112865ea9c7fdd5b28821cb453ae 389116 libmozjs0d_1.8.1.14-1_amd64.deb
 b39033458fe22360228704b2d6a3c025890e11a2 867546 libmozjs0d-dbg_1.8.1.14-1_amd64.deb
 d0f22ada83af43102e20a12f816b37e62ebc3188 56086 spidermonkey-bin_1.8.1.14-1_amd64.deb
 b2131f40ad27a0549c4a61546e09fa41747259db 6695322 libxul0d_1.8.1.14-1_amd64.deb
 b9bab375ac2e343c2f6d9aef5bf6363397ad8d19 47079700 libxul0d-dbg_1.8.1.14-1_amd64.deb
 6a1834fe7f9fb80deafbd3d00412825cd3144e6f 126096 python-xpcom_1.8.1.14-1_amd64.deb
Checksums-Sha256: 
 cbae40d7bf70b36a8c4431ea396c04b97a43a0fda8f9b9910c3e4937b9dc4cef 1625 xulrunner_1.8.1.14-1.dsc
 5acc145d501d3c89086f410c8daf5eaf313725ca63c6fb69f6c542fe558b0510 40889518 xulrunner_1.8.1.14.orig.tar.gz
 b16484806cdb186d0d2fcfbad981b86ab397dd517b61f51a8a737e8d102ef647 132470 xulrunner_1.8.1.14-1.diff.gz
 e7c618c94a3753c57d02b88f2d83938af7cb47c07bd9a24d170a1c0f95ba5a71 192164 libmozjs-dev_1.8.1.14-1_all.deb
 f699fa5f9de012c40c4922b974da32fc22b02f2cec01402ac5eb072434db7310 1206384 libxul-common_1.8.1.14-1_all.deb
 88d297b93371b8e3c99f4b0affbae6fefcdaa32bbdbbbb97aedb5df47cc860c0 3023148 libxul-dev_1.8.1.14-1_all.deb
 06cbc55544bb88ba04a9e644105bfb4e0f4becbd3596f321165788cd2f1cf35a 1343468 libmozillainterfaces-java_1.8.1.14-1_all.deb
 3fb4064fbb445d5bb9fd5ce1eaa656eb18b5ece7b3ca01559ec92ec3aa6d7327 292036 xulrunner_1.8.1.14-1_amd64.deb
 f0486ad68b83f1f541eb424b1f5e840be57ef0912c7b8e7f5fd38d025a96bafd 70394 xulrunner-gnome-support_1.8.1.14-1_amd64.deb
 6581e4f49484ad83ec5f68113974be9880b0e399a4ca7b64293084160bc4702d 389116 libmozjs0d_1.8.1.14-1_amd64.deb
 ac2704d5d4b3a003f19563dd1edc81ee99ef3fe72d1aae82ff3ff4b600616b86 867546 libmozjs0d-dbg_1.8.1.14-1_amd64.deb
 9bf780630edcf3db27aa990c5a604ac2e20d55f2f2c968ad3e0491faf593ef87 56086 spidermonkey-bin_1.8.1.14-1_amd64.deb
 69f472a82cf03a970bc23bf349a47d675bbb64f3df550f4240b06ea5c2a5429d 6695322 libxul0d_1.8.1.14-1_amd64.deb
 c135a4702ad947847be45c3dd293752a8ffab6c0af5cb445b87d87ed4d2ec933 47079700 libxul0d-dbg_1.8.1.14-1_amd64.deb
 f0ded78ce65f46113dceb88c29728420f32f955e1deee383f4c9ca2cf111285a 126096 python-xpcom_1.8.1.14-1_amd64.deb
Files: 
 a5a036b0a31d33800bf94385679b3a2e 1625 devel optional xulrunner_1.8.1.14-1.dsc
 585ecf22664601ce09e59952d8eb5781 40889518 devel optional xulrunner_1.8.1.14.orig.tar.gz
 5615fc1edfc20b210766e12a8f22e089 132470 devel optional xulrunner_1.8.1.14-1.diff.gz
 e4b62dad607b991fbb8eba7a4bb784ed 192164 libdevel optional libmozjs-dev_1.8.1.14-1_all.deb
 a830fb0a095890d774eced2ca054610f 1206384 libs optional libxul-common_1.8.1.14-1_all.deb
 0f7ed4696db8bb6c593d6dd87826a758 3023148 libdevel optional libxul-dev_1.8.1.14-1_all.deb
 36e84937591a3a6578ad1fecadf520c5 1343468 libdevel extra libmozillainterfaces-java_1.8.1.14-1_all.deb
 fbbac9a24efa7fdee192fea0a5637fed 292036 devel optional xulrunner_1.8.1.14-1_amd64.deb
 6d1fccccb1766411d0001a705e7c4f2f 70394 devel optional xulrunner-gnome-support_1.8.1.14-1_amd64.deb
 567ec44b786cf95fbacfe503d70f73f1 389116 libs optional libmozjs0d_1.8.1.14-1_amd64.deb
 60fa2136324d9083717f376d9502194b 867546 libdevel extra libmozjs0d-dbg_1.8.1.14-1_amd64.deb
 d52a999b5ae33d1978703f75d166a8a6 56086 interpreters optional spidermonkey-bin_1.8.1.14-1_amd64.deb
 e953390e02ffc0ea57a74165bea6ff53 6695322 libs optional libxul0d_1.8.1.14-1_amd64.deb
 4566c654cdd34f22692a0ad23afe371a 47079700 libdevel extra libxul0d-dbg_1.8.1.14-1_amd64.deb
 ef64a9167c92bf02af23f7d075bdb6b6 126096 python extra python-xpcom_1.8.1.14-1_amd64.deb

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

iD8DBQFICDHF3kvaLFT9KlgRAqDdAJ4lgQxZa3kc4tAoqhcyySA6YvptUQCgioQf
Wu8OTf+MW96g9FNPI3hGfLk=
=Vu/d
-----END PGP SIGNATURE-----

Message #101 received at 476303-close@bugs.debian.org (full text, mbox, reply):

From: Mike Hommey <glandium@debian.org>

To: 476303-close@bugs.debian.org

Subject: Bug#476303: fixed in xulrunner 1.9~b5-3

Date: Thu, 24 Apr 2008 21:02:43 +0000

Source: xulrunner
Source-Version: 1.9~b5-3

We believe that the bug you reported is fixed in the latest version of
xulrunner, which is due to be installed in the Debian FTP archive:

libmozillainterfaces-java_1.9~b5-3_all.deb
  to pool/main/x/xulrunner/libmozillainterfaces-java_1.9~b5-3_all.deb
libmozjs-dev_1.9~b5-3_all.deb
  to pool/main/x/xulrunner/libmozjs-dev_1.9~b5-3_all.deb
libmozjs1d-dbg_1.9~b5-3_amd64.deb
  to pool/main/x/xulrunner/libmozjs1d-dbg_1.9~b5-3_amd64.deb
libmozjs1d_1.9~b5-3_amd64.deb
  to pool/main/x/xulrunner/libmozjs1d_1.9~b5-3_amd64.deb
python-xpcom_1.9~b5-3_amd64.deb
  to pool/main/x/xulrunner/python-xpcom_1.9~b5-3_amd64.deb
spidermonkey-bin_1.9~b5-3_amd64.deb
  to pool/main/x/xulrunner/spidermonkey-bin_1.9~b5-3_amd64.deb
xulrunner-1.9-common_1.9~b5-3_all.deb
  to pool/main/x/xulrunner/xulrunner-1.9-common_1.9~b5-3_all.deb
xulrunner-1.9-dbg_1.9~b5-3_amd64.deb
  to pool/main/x/xulrunner/xulrunner-1.9-dbg_1.9~b5-3_amd64.deb
xulrunner-1.9-gnome-support_1.9~b5-3_amd64.deb
  to pool/main/x/xulrunner/xulrunner-1.9-gnome-support_1.9~b5-3_amd64.deb
xulrunner-1.9_1.9~b5-3_amd64.deb
  to pool/main/x/xulrunner/xulrunner-1.9_1.9~b5-3_amd64.deb
xulrunner-dev-static_1.9~b5-3_amd64.deb
  to pool/main/x/xulrunner/xulrunner-dev-static_1.9~b5-3_amd64.deb
xulrunner-dev_1.9~b5-3_all.deb
  to pool/main/x/xulrunner/xulrunner-dev_1.9~b5-3_all.deb
xulrunner_1.9~b5-3.diff.gz
  to pool/main/x/xulrunner/xulrunner_1.9~b5-3.diff.gz
xulrunner_1.9~b5-3.dsc
  to pool/main/x/xulrunner/xulrunner_1.9~b5-3.dsc



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 476303@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mike Hommey <glandium@debian.org> (supplier of updated xulrunner package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Thu, 24 Apr 2008 21:12:31 +0200
Source: xulrunner
Binary: xulrunner-1.9 xulrunner-1.9-gnome-support libmozjs1d libmozjs-dev libmozjs1d-dbg spidermonkey-bin xulrunner-1.9-common xulrunner-dev xulrunner-dev-static xulrunner-1.9-dbg libmozillainterfaces-java python-xpcom
Architecture: source all amd64
Version: 1.9~b5-3
Distribution: experimental
Urgency: low
Maintainer: Mike Hommey <glandium@debian.org>
Changed-By: Mike Hommey <glandium@debian.org>
Description: 
 libmozillainterfaces-java - XPCOM bindings for Java
 libmozjs-dev - Development files for the Mozilla SpiderMonkey JavaScript library
 libmozjs1d - The Mozilla SpiderMonkey JavaScript library
 libmozjs1d-dbg - Development files for the Mozilla SpiderMonkey JavaScript library
 python-xpcom - XPCOM bindings for Python
 spidermonkey-bin - standalone JavaScript/ECMAScript (ECMA-262) interpreter
 xulrunner-1.9 - XUL + XPCOM application runner
 xulrunner-1.9-common - Gecko engine library - common files
 xulrunner-1.9-dbg - Development files for the Gecko engine library
 xulrunner-1.9-gnome-support - Support for GNOME in xulrunner applications
 xulrunner-dev - Development files for the Gecko engine library
 xulrunner-dev-static - Static libraries for the Gecko engine
Closes: 476303 476920 476921 477068
Changes: 
 xulrunner (1.9~b5-3) experimental; urgency=low
 .
   * xpcom/reflect/xptcall/src/md/unix/xptcinvoke_linux_m68k.cpp,
     xpcom/reflect/xptcall/src/md/unix/xptcinvoke_asm_mips.s,
     xpcom/reflect/xptcall/src/md/unix/xptcinvoke_mips.cpp: Implement new XPCOM
     API on m68k and mips. This fixes FTBFSes on these architectures.
     Closes: #477068.
   * configure, configure.in, xpcom/base/nscore.h, xpcom/glue/nsMemory.h,
     xpcom/glue/nsProxyRelease.h, xpcom/glue/nsStringAPI.h,
     xpcom/glue/standalone/Makefile.in, xpcom/glue/standalone/nsGlueLinking.h,
     xpcom/glue/standalone/nsXPCOMGlue.h: Don't build the standalone glue as a
     dynamic library. This is actually not maintenable without being a PITA.
     Closes: #476920, #476921.
   * debian/control:
     + Invert xulrunner-dev and xulrunner-static-dev dependencies on each
       other.
     + xulrunner-dev doesn't need to conflict with libxul-dev now it doesn't
       contain libxpcomglue.so.
     + Modify xulrunner-dev-static description.
   * (was: debian/patches/38_armel.dpatch)
     configure.in, configure: Force to not use -fshort-wchar where it fails.
     Closes: #476303.
   * debian/xulrunner-dev-static.install, debian/xulrunner-dev.install: Move
     all pkg-config files into xulrunner-dev.
Checksums-Sha1: 
 bc0f1501038a6c178628ab2d89ffc2cabfda2588 1733 xulrunner_1.9~b5-3.dsc
 90318445ce746128a4634b7c9f138ad5bb56bea7 85598 xulrunner_1.9~b5-3.diff.gz
 c8b4a35838b6f2e6a0724aded8e25807da9987a7 215932 libmozjs-dev_1.9~b5-3_all.deb
 20b3750fab543d12ced26303c4309b19b708f7f0 1264836 xulrunner-1.9-common_1.9~b5-3_all.deb
 6a9b912b33a203c2d01910a42226f0aa2eabff7e 4735844 xulrunner-dev_1.9~b5-3_all.deb
 500e99f13003392a9ca9cec5459b43232a85cbff 1430664 libmozillainterfaces-java_1.9~b5-3_all.deb
 770a3c7bedb02f1533c488170d984172fe7acd64 6439328 xulrunner-1.9_1.9~b5-3_amd64.deb
 a038184d01410f16ebbc9fe83293dcdddae47043 93780 xulrunner-1.9-gnome-support_1.9~b5-3_amd64.deb
 22e63b6cff03f666b3ea6012be8e219529e1e73a 364866 libmozjs1d_1.9~b5-3_amd64.deb
 dada722ede8d657024db0dc151d2655f1e93b631 911648 libmozjs1d-dbg_1.9~b5-3_amd64.deb
 ebb38f7d833355720f3b3e227bb9f8ce160bbd98 62330 spidermonkey-bin_1.9~b5-3_amd64.deb
 cad2d3d4db9fc4c2aabe5451c4af9b0e885d028c 189012 xulrunner-dev-static_1.9~b5-3_amd64.deb
 8eb2e15e33bf4a4dd4a0293fa3548bf6ba5ea1ee 49666530 xulrunner-1.9-dbg_1.9~b5-3_amd64.deb
 0dcfbe249093e5d952b75eaf869e8e986d73e2cf 144082 python-xpcom_1.9~b5-3_amd64.deb
Checksums-Sha256: 
 be52da72237ffa0cfecb5a2d65d969b6243e3d3637a17c7667280ae42e29c9ba 1733 xulrunner_1.9~b5-3.dsc
 4543b26ffa4eaf3c1655f776cf32d8b72b091d953a139a10f92b31c3be769819 85598 xulrunner_1.9~b5-3.diff.gz
 980ee23d22c84312646cf9d3baae46625766a2c2b5053dbab86bd8c8292eedc2 215932 libmozjs-dev_1.9~b5-3_all.deb
 1fb24e71a971910769c41e3509caa994fc8db3e9eba7209902539279b63bfe26 1264836 xulrunner-1.9-common_1.9~b5-3_all.deb
 231065fb46ae4c5b16b585054ea71ddab979959e5093bbfa89dc267b7bfc7469 4735844 xulrunner-dev_1.9~b5-3_all.deb
 e7b647535b2397ef81b329d867a78bc50f82d4f573899117a61060e8d0f32634 1430664 libmozillainterfaces-java_1.9~b5-3_all.deb
 bde89f4ee79df5d02a64a1bcc98aac8db3268beb68cd448269496621e1f41624 6439328 xulrunner-1.9_1.9~b5-3_amd64.deb
 95d2a4dbe5eedce8603a5e38080dafa5f96f5bb73257bb1cb48cc2efddcee626 93780 xulrunner-1.9-gnome-support_1.9~b5-3_amd64.deb
 02f825f436a092bbd6ec774a19576a18b34a65310f78c17895d4859e4e6de444 364866 libmozjs1d_1.9~b5-3_amd64.deb
 c0f8be02b4c006879a7a48eac49e2cb57e625e260603f9638d4961aec5e68416 911648 libmozjs1d-dbg_1.9~b5-3_amd64.deb
 51b7dcd8d6749d6bcb672c5ba6c262878af6127dc44038a14d99074667475fe9 62330 spidermonkey-bin_1.9~b5-3_amd64.deb
 a751dc405f63981e0066e0eca3ce1d4d584f5c47593b4606cc642f908f5533ef 189012 xulrunner-dev-static_1.9~b5-3_amd64.deb
 e3d4682d7749f587c57a73470af05231200a6a2a20da7076b262165810e7f61f 49666530 xulrunner-1.9-dbg_1.9~b5-3_amd64.deb
 41e80d02d073ac41209772645839821574b8ecee44860a9ab09d3ab565c3acef 144082 python-xpcom_1.9~b5-3_amd64.deb
Files: 
 9126aee7b7baa0fc1c0db3e2839ac759 1733 devel optional xulrunner_1.9~b5-3.dsc
 31d33cf037f63f9ace5f39eb41536631 85598 devel optional xulrunner_1.9~b5-3.diff.gz
 751d4014fb51b8d4d6abcd2b7d13ddb6 215932 libdevel optional libmozjs-dev_1.9~b5-3_all.deb
 522b527e4550efcb359c92c72f351bc8 1264836 libs optional xulrunner-1.9-common_1.9~b5-3_all.deb
 4899aac8c77139b07489cdea9dab7192 4735844 libdevel optional xulrunner-dev_1.9~b5-3_all.deb
 cf5bf2cd273e249772cb389ce9b33c42 1430664 libdevel extra libmozillainterfaces-java_1.9~b5-3_all.deb
 38febdc930e5dfd32cd2df6d18201bf8 6439328 devel optional xulrunner-1.9_1.9~b5-3_amd64.deb
 c2ca1d17c187b5af3de0ee4e8245b831 93780 devel optional xulrunner-1.9-gnome-support_1.9~b5-3_amd64.deb
 558fbe9b0e7f730821f64b908ba50251 364866 libs optional libmozjs1d_1.9~b5-3_amd64.deb
 f39ed0e841acb9c4c754a5e4b0ac8a9a 911648 libdevel extra libmozjs1d-dbg_1.9~b5-3_amd64.deb
 0be9f272541738e4c33ee72717a3d2ca 62330 interpreters optional spidermonkey-bin_1.9~b5-3_amd64.deb
 06e515ae7b741754bb95ba27acd41051 189012 libdevel optional xulrunner-dev-static_1.9~b5-3_amd64.deb
 8f7f995fedf87d8c07eb8eee585163a2 49666530 libdevel extra xulrunner-1.9-dbg_1.9~b5-3_amd64.deb
 11c2fd5be170f4dbe43fa06f955a4260 144082 python extra python-xpcom_1.9~b5-3_amd64.deb

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

iD8DBQFIEO3g3kvaLFT9KlgRArp7AJ9CLWas0dRMbYxihOUg8OOWi4gvRgCbBzaY
K/xP174Gr2a/dPu6YosZrvU=
=1CCz
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.