From owner-freebsd-current Thu Oct 10 21:59:08 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA16804 for current-outgoing; Thu, 10 Oct 1996 21:59:08 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA16799 for ; Thu, 10 Oct 1996 21:58:59 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.7.6/8.7.3) with ESMTP id VAA01796; Thu, 10 Oct 1996 21:58:22 -0700 (PDT) Message-Id: <199610110458.VAA01796@austin.polstra.com> To: Masafumi NAKANE/=?ISO-2022-JP?B?GyRCQ2Y6LDJtSjgbKEI=?= cc: nate@mt.sri.com, current@freefall.freebsd.org Subject: Re: kaffe problems In-reply-to: Your message of "Fri, 11 Oct 1996 08:44:54 +0900." <199610102344.IAA28098@mail.tky007.tth.expo96.ad.jp> Date: Thu, 10 Oct 1996 21:58:22 -0700 From: John Polstra Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Thanks folks for taking time on this problem. ... > Anyway, the problem was caused mainly by my mistake and misunderstand. > I'm awfully sorry for making you put much effort on this and spare time > on this. Max, I don't think you need to feel bad about this. Based on the symptoms you observed, it would be natural to think that something was wrong with ldconfig or the dynamic linker. All the more so since some extensive changes were made to both of them very recently. And, kaffe uses dlopen() and dlsym(), which exercise parts of the dynamic linker that are very rarely used. I drew the same (wrong) conclusion as you. You did a good job of stating the problem and of answering the questions that we asked. The reason it took so much time to solve this was that it was a very baffling problem! Nobody blames you for that. > I had strong belief that LD_LIBRARY_PATH is unnecessary as long as > you execute ldconfig properly. Yes, you are right about that, as far as the dynamic linker is concerned. Unfortunately, kaffe itself examines LD_LIBRARY_PATH directly, and does something with it. That is unusual. > The Makefile of kaffe port does ldconfig after the > installation and that made my belief even stronger. ;_) Yup! > jdp> Maybe he's got a hardware problem. Maybe he's got a > jdp> corrupted libc.so.3.0. > > Oh, right, actually I rebuilt libc.so.3.0, too before reinstalling > kaffe and jdk ports, so this may be true. Yes, maybe that was the problem. Something was seriously hosed in your system, anyway. I'm glad it's working OK again. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth