Re: blind spot for java
On Friday 26 August 2005 14:34, Tim Ruehsen wrote:
> Hi Graham,
>
> - make shure, that file is not a symlink. It should tell you if you do 'ls
> -la'.
nope it's not a symlink
> - make shure that not one of the directories has obscure permissions.
drwxr-xdrwxr-xr-x 12 root root 4096 2005-08-22 16:17 usr
drwxrwsr-x 11 root staff 4096 2005-08-26 12:21 local
drwxr-sr-x 9 root staff 4096 2005-08-26 12:21 jdk1.5.0_04
drwxr-sr-x 2 root staff 4096 2005-08-26 13:51 bin
don't think there is anything odd there
>
> You could (as root) copy the java file into /tmp and try to execute it
> there. Does it work?
Nope, same error message.
> If not, maybe the file is corrupt.
Very very unlikely. Could only be corrupt if it became corrupt when I copied
it over from the server. The exact same JDK runs fine on the server (a 32bit
testing machine). Interestingly though the install won't run on this machine
either (it too runs fine on the server). The installer fails to create the
jdk1.5.0_04 directory.
> Try things like
> 'file java'
$file java
java: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux
2.2.5, dynamically linked (uses shared libs), stripped
> or 'ldd java',
this looks bad
$ldd java
/usr/bin/ldd: line 171: /lib/ld-linux.so.2: No such file or directory
ldd: /lib/ld-linux.so.2 exited with unknown exit code (127)
>I just forgot: make shure, you don't have an alias in your shell. Try 'alias'
>in your bash.
$alias
alias la='ls -A'
alias ll='ls -l'
alias ls='ls --color=auto'
Many thanks for the help so far. I suspect the fact ldd failed has something
to do with the problem but I'm just taking an educated guess there.
Graham
Reply to: