On 28/08/2011 15:35, Giuseppe Iuculano wrote:
On 08/28/2011 03:31 PM, Jérémy Lal wrote:
Shouldn't the solution be to move v8::internal::I18NExtension::get() to v8
(not internal) namespace ?
Yes, but I suspect there are a lot of v8::internal() needed by chromium.
Cheers,
Giuseppe.
v8
On 28/08/2011 15:35, Giuseppe Iuculano wrote:
On 08/28/2011 03:31 PM, Jérémy Lal wrote:
Shouldn't the solution be to move v8::internal::I18NExtension::get() to v8
(not internal) namespace ?
Yes, but I suspect there are a lot of v8::internal() needed by chromium.
A quick investigation
Package: libv8
Version: 3.4.14.13-2
Severity: important
Tags: experimental patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I'm preparing chromium 14 for experimental, and it FTFBS with this:
LINK(target) out/Release/chrome
On 28/08/2011 15:17, Giuseppe Iuculano wrote:
Package: libv8
Version: 3.4.14.13-2
Severity: important
Tags: experimental patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I'm preparing chromium 14 for experimental, and it FTFBS with this:
LINK(target) out/Release/chrome
On 08/28/2011 03:31 PM, Jérémy Lal wrote:
Shouldn't the solution be to move v8::internal::I18NExtension::get() to v8
(not internal) namespace ?
Yes, but I suspect there are a lot of v8::internal() needed by chromium.
Cheers,
Giuseppe.
signature.asc
Description: OpenPGP digital signature
5 matches
Mail list logo