| 1 |
On 5 October 2012 22:28, "Paweł Hajdan, Jr." <phajdan.jr@g.o> wrote: |
| 2 |
> This is the case with dev-lang/v8: it doesn't build on x32 |
| 3 |
> (<https://bugs.gentoo.org/423815>), and upstream said they *won't* |
| 4 |
> support x32 |
| 5 |
> (<https://groups.google.com/d/msg/v8-users/c-_URSZqTq8/7wHl095t2CMJ>). |
| 6 |
> |
| 7 |
> Note that with v8 it's not just about getting v8 itself to compile, but |
| 8 |
> also making it generate correct JIT code on x32, which would require |
| 9 |
> substantial changes to v8 code (in fact, a whole new 40K arch port, see |
| 10 |
> the discussion linked to above). |
| 11 |
> |
| 12 |
> Should dev-lang/v8 get p.masked on x32 profile, or is there some better |
| 13 |
> way to handle it? What are your suggestions? |
| 14 |
|
| 15 |
From what Diego wrote about it, I would say we shouldn't spend much |
| 16 |
time and effort on x32. I know it's the new and shiny thing, but it |
| 17 |
doesn't seem very useful. I think arm64/aarch64/armv8 is more |
| 18 |
promising, if you want to play around with a new arch. |
| 19 |
|
| 20 |
> I had a crazy idea to just build v8 and v8-dependent packages using |
| 21 |
> non-x32 ABI, but I'm not sure if it's possible and if it would be the |
| 22 |
> right thing to do. |
| 23 |
|
| 24 |
If it's easy to do a kind of multilib setup, then it might be worth doing. |
| 25 |
|
| 26 |
-- |
| 27 |
Cheers, |
| 28 |
|
| 29 |
Ben | yngwin |
| 30 |
Gentoo developer |
| 31 |
Gentoo Qt project lead, Gentoo Wiki admin |
Archives