| 1 |
Whoops... accidentally replied off list much earlier today. |
| 2 |
|
| 3 |
Sebastiaan wrote: |
| 4 |
> I have tried to increase the amount of memory java can use by adding |
| 5 |
> -J-Xms48m to the command (right after configuration, since a second |
| 6 |
> compilation attempt always works), but without succes. |
| 7 |
> |
| 8 |
-Xms sets the initial memory allocated. You probably want -Xmx, which |
| 9 |
sets the maximum amount of memory that will be allocated, and you |
| 10 |
probably want this to be fairly high, or at least more than 48m. |
| 11 |
If you're going to patch the makefiles, a clean way to do it may be to |
| 12 |
add like a variable JAVACFLAGS, which we can then set in the ebuild like: |
| 13 |
use amd64 && JAVACFLAGS="-J-Xmx256m ${JAVACFLAGS}" |
| 14 |
> Does anyone have an idea what the problem can be? I am unsure if the |
| 15 |
> problem lies within VTK or Blackdown. Sun-jdk does not have a 64 bit |
| 16 |
> version available, so I cannot compare with that. |
| 17 |
> |
| 18 |
I'm pretty sure it's a blackdown on amd64 thing. We do encounter it for |
| 19 |
a few packages, like net-p2p/azureus. For the record, there is a amd64 |
| 20 |
version of sun-jdk-1.5 (and 1.6...), but I'm sure at this point I |
| 21 |
shouldn't have to go into the concerns about using them ;) |
| 22 |
|
| 23 |
> References: |
| 24 |
> I have previously posted this to |
| 25 |
> http://bugs.gentoo.org/show_bug.cgi?id=123178 as well. |
| 26 |
> |
| 27 |
|
| 28 |
Hope this helps, |
| 29 |
- Josh |
| 30 |
-- |
| 31 |
gentoo-java@g.o mailing list |
Archives