| 1 |
Jorge Almeida wrote: |
| 2 |
> java hates me. |
| 3 |
> |
| 4 |
> I already reemerged dev-java/blackdown-jdk, which is the only java |
| 5 |
> installed, and didn't forget to env-update and source /etc/profile. |
| 6 |
> Running revdep-rebuild is useless, as a second revdep-rebuild -p will |
| 7 |
> still give the same error message. |
| 8 |
|
| 9 |
It will always give you the same error message. We should fix this by |
| 10 |
using the features available in the latest revdep-rebuild. See man |
| 11 |
revdep-rebuild. |
| 12 |
|
| 13 |
> |
| 14 |
> And why should something named |
| 15 |
> /opt/blackdown-jdk-1.4.2.02/jre/lib/i386/libjsoundalsa.so exist? I don't |
| 16 |
> have the "alsa" USE flag set, for the excelent reason that this is an |
| 17 |
> office workstation with no sound equipment whatsoever. |
| 18 |
> Could it be that somehow the ebuild is ignoring this point? |
| 19 |
> I unset "browserplugin" before emerging, just in case this was pulling |
| 20 |
> sound support. Still, "mozilla" was set; the emerge says that the former |
| 21 |
> USE variable is the latter renamed... |
| 22 |
> |
| 23 |
> What to do? Can I safely ignore the revdep-rebuild messages? |
| 24 |
|
| 25 |
It exists because blackdown is a binary package that installs every |
| 26 |
binary in it. The java class libraries provide sound libraries so it |
| 27 |
naturally needs access to our sound card using alsa. We have not taken |
| 28 |
the road of removing the native libraries because you never know what |
| 29 |
breaks when doing that. You can safely ignore the messages as long as |
| 30 |
you do not try to use the features provided by libjsoundalsa.so. |
| 31 |
|
| 32 |
Regards, |
| 33 |
Petteri Räty (Betelgeuse) |
Archives