Fabien Renaud wrote:
But kaffe shouldn´t complain about libawt when the problem comes from
qt, no ?
True. It may be a libtool issue, I'll look into it.
cheers,
dalibor topic
___
kaffe mailing list
[EMAIL PROTECTED]
http://kaffe.org/cgi-bin/mailman/listin
Dalibor Topic wrote:
Fabien Renaud wrote:
But kaffe shouldn´t complain about libawt when the problem comes from
qt, no ?
Could you add a printf to
325 const char *err =
LIBRARYERROR(); in file kaffe/kaffevm/external.c
to see if the error from libtool mention
Fabien Renaud wrote:
But kaffe shouldn´t complain about libawt when the problem comes from
qt, no ?
Could you add a printf to
325 const char *err =
LIBRARYERROR(); in file kaffe/kaffevm/external.c
to see if the error from libtool mentions qt ?
cheers,
dalibor
Dalibor Topic wrote:
Fabien Renaud wrote:
Hello,
I said it in IRC but I repeat here because some people asked the
question.
Why kaffe says me "libawt not found" whereas the lib is here with all
my other libs ?
Because kaffe doesn´t find libqt. It seems kaffe doesnt search in QTDIR.
Quoting from
Fabien Renaud wrote:
Hello,
I said it in IRC but I repeat here because some people asked the question.
Why kaffe says me "libawt not found" whereas the lib is here with all my
other libs ?
Because kaffe doesn´t find libqt. It seems kaffe doesnt search in QTDIR.
Quoting from FAQ.awt:
* Dynamical
Hello,
I said it in IRC but I repeat here because some people asked the question.
Why kaffe says me "libawt not found" whereas the lib is here with all my
other libs ?
Because kaffe doesn´t find libqt. It seems kaffe doesnt search in QTDIR.
Cheers,
Fabien
_
