| 1 |
On 10/14/07, Randy Barlow <randy@×××××××××××××××××.com> wrote: |
| 2 |
> |
| 3 |
> Florian Philipp wrote: |
| 4 |
> > I've noticed that the gcj use flag is not enabled by default and |
| 5 |
> > therefore all java code is compiled to byte code instead of native |
| 6 |
> > binaries, am I correct? |
| 7 |
> |
| 8 |
> gcj can compile java code directly to machine code, and I'm pretty sure |
| 9 |
> that the Sun compiler just compiles to byte code. I have no experience |
| 10 |
> with gcj though, so I can't answer your second question... |
| 11 |
> |
| 12 |
> > I wonder how I can change that. Just re-emerge gcc with USE="gcj" and |
| 13 |
> > all packages containing java code? Is it even a good idea? |
| 14 |
|
| 15 |
|
| 16 |
Probably not, but you could always try it and report back to the list... :o) |
| 17 |
|
| 18 |
Nothing that needs to work with a class loader, like applets do, will work. |
| 19 |
I would expect some problems with introspection. Moreover, last I tried it, |
| 20 |
there were buckets of incompatibility with the Java libraries. Maybe it's |
| 21 |
more mature now. |
| 22 |
|
| 23 |
Kevin O'Gorman, PhD |
Archives