Re: blind spot for java
Hi Graham,
- make shure, that file is not a symlink. It should tell you if you do 'ls
-la'.
- make shure that not one of the directories has obscure permissions.
You could (as root) copy the java file into /tmp and try to execute it there.
Does it work? If not, maybe the file is corrupt. Try things like 'file java'
or 'ldd java', just to see Tools like file and/or ldd recognise it as
executable.
Tim
Am Freitag, 26. August 2005 13:32 schrieb Graham Smith:
> Hi,
>
> I know this might seem a little strange but my system seems to have
developed
> a blind spot for Java.
>
> I have a JDK installed in /usr/local/jdk1.5.0_04/ when I attempt to execute
>
> foo@bar$ /usr/local/jdk1.5.0_04/bin/java
>
> I get
>
> bash: /usr/local/jdk1.5.0_04/bin/java: No such file or directory
>
> which is quite plainly wrong as the file most certainly does exist and has
> execution rights. I have another (very slightly older and 64-bit) version of
> Java installed via java-package which works fine but I need to get this one
> working.
>
> Any ideas what might be wrong?
>
> All the other applications seems to be working fine. I have re-installed the
> JDK and tried other versions and all produce the same message. This is a
long
> shot I know but I am using the 64bit debian port and this is a 32bit VM it
is
> therefore relying on some libraries provided by the 32bit chroot. It was
> working fine yesterday but I also upgraded the chroot yesterday. I'm
wonering
> if the two could be linked. The problem is that it just doesn't seem to even
> find the java file to get.
>
> TIA, Graham.
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org
>
>
Reply to: