On Fri, 2008-06-13 at 07:17 +0200, Mike Hommey wrote:
On Fri, Jun 13, 2008 at 02:00:00AM +0100, Ben Hutchings wrote:
On Thu, 2008-06-12 at 17:22 +0300, Riku Voipio wrote:
The xulrunner 1.9 headers now use wchar_t but still require it to be
defined as a 16-bit type. The pkg-config files
The xulrunner 1.9 headers now use wchar_t but still require it to be
defined as a 16-bit type. The pkg-config files specify -fshort-wchar
to ensure that this is the case.
duplicate of #485618 ?
Now, the question is, why does it suddenly break?
It appears to be introduced by gcc-4.3,
On Thu, Jun 12, 2008 at 12:00:37AM +0100, Ben Hutchings wrote:
Package: xulrunner-dev
Version: 1.9~rc2-2
Severity: important
The xulrunner 1.9 headers now use wchar_t but still require it to be
defined as a 16-bit type. The pkg-config files specify -fshort-wchar
to ensure that this is the
On Thu, 2008-06-12 at 17:22 +0300, Riku Voipio wrote:
The xulrunner 1.9 headers now use wchar_t but still require it to be
defined as a 16-bit type. The pkg-config files specify -fshort-wchar
to ensure that this is the case.
duplicate of #485618 ?
Not exactly - you think -fshort-wchar
On Fri, Jun 13, 2008 at 02:00:00AM +0100, Ben Hutchings wrote:
On Thu, 2008-06-12 at 17:22 +0300, Riku Voipio wrote:
The xulrunner 1.9 headers now use wchar_t but still require it to be
defined as a 16-bit type. The pkg-config files specify -fshort-wchar
to ensure that this is the case.
Package: xulrunner-dev
Version: 1.9~rc2-2
Severity: important
The xulrunner 1.9 headers now use wchar_t but still require it to be
defined as a 16-bit type. The pkg-config files specify -fshort-wchar
to ensure that this is the case. Normally wchar_t is a 32-bit type,
and libstdc++ is built with
On Thu, Jun 12, 2008 at 12:00:37AM +0100, Ben Hutchings wrote:
Previously the header files defined PRunichar without referring to
wchar_t, which caused no such problems.
Actually, PRUnichar has been defined as wchar_t for a while... when
HAVE_CPP_2BYTE_WCHAR_T is set, and this has been the
7 matches
Mail list logo