1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
|
THE TYA FAQ
--------------------------------------------------------------------------
Q:
> I've just installed tya0.7 and it seemed to install ok, but when I tried
> the Iview test in demos (and any other of my Java apps) I get this
> error:
>
> libtya.so: cannot open shared object file: No such file or directory
> (libtya.so)
> Warning: JIT compiler "tya" not found. Will use interpreter.
>
> But of course it is there:
> -rwxr-xr-x 1 root root 54642 Jun 18 17:30
> /usr/local/lib/libtya.so
A:
set your LD_LIBRARY_PATH
i.e.
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib ;export LD_LIBRARY_PATH
Joe Carter <joseph.carter@man.brite.co.uk>
--------------------------------------------------------------------------
Q:
> My compiler cannot find the include files "native.h" and/or "typedefs_md.h"
> and subsequently reports many (typing) errors.
> These files are in my JDK, at XXX/native.h and at YYY/typedefs_md.h
> In my case, YYY=XXX/genunix
A:
You probably have a distribution with its own homedir, containing the `java'
executable somewhere inside; and in addition, `which java' probably returns a
more standard place for an executable such as `/usr/bin/java' which is linked
to the binary inside Java's homedir.
The configure script guesses the includes are relative to `which java` by
"../include" and "../include/genunix" which is not true for these linked
binaries.
You should (manually) edit the Makefile _after_ doing configure, and locate
the line that starts "JAVAINCDIR=" and change its value into "-IXXX -IYYY".
If your system work with RPM, you may want to try a newer config script, that
asks RPM for the header files by invoking `rpm -ql jdk`.
Rick van Rein <vanrein@cyberdude.com>
--------------------------------------------------------------------------
Q:
> My compiler returns an internal error, namely:
> gcc: Internal compiler error: program cc1 got fatal signal 11
> cpp: output pipe has been closed
> And then it dumps a core file. What should I do?
A:
I don't know what the cause is... but lowering the level of optimisation solved
the problem for my gcc 2.7.2p by requesting less optimisation.
In either Makefile.in (before running configure) or in Makefile (after running
configure), locate the uncommented line that reads "COPTFLAGS=-O6" and change
it into "COPTFLAGS=-O3" and everything should be fine.
Rick van Rein <vanrein@cyberdude.com>
--------------------------------------------------------------------------
Q:
> I've gotten TYA via a Linux distribution CD. But where
> can I fetch newer TYA releases ?
A:
look to URL
ftp://gonzalez.cyberus.ca/pub/Linux/java/
N.N.
--------------------------------------------------------------------------
|
