Date: Thu, 14 Oct 2004 15:09:47 -0600 From: Greg Lewis <glewis@eyesbeyond.com> To: Kris Kennaway <kris@obsecurity.org> Cc: java@freebsd.org Subject: Re: [ports-i386@FreeBSD.org: java_cup-10.k failed on i386 4] Message-ID: <20041014210947.GA7680@misty.eyesbeyond.com> In-Reply-To: <20041014204111.GA65200@xor.obsecurity.org> References: <20041012170114.GA70274@xor.obsecurity.org> <20041014203759.GA7268@misty.eyesbeyond.com> <20041014204111.GA65200@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Oct 14, 2004 at 01:41:11PM -0700, Kris Kennaway wrote: > On Thu, Oct 14, 2004 at 02:37:59PM -0600, Greg Lewis wrote: > > On Tue, Oct 12, 2004 at 10:01:14AM -0700, Kris Kennaway wrote: > > > Any ideas why every port that uses diablo is failing on 4.x? > > > > Works for me on 4.10. It almost seems like the .java_wrapper script is > > failing to set the LD_LIBRARY_PATH correctly or that path doesn't contain > > libjava.so (I'm not sure how this could occur) or libjava.so can't be > > loaded for some reason. Since diablo hasn't been changed recently, one > > would assume its some recent change in 4.x? Doesn't bento use some sort > > of 4.x jail on a 5.x box to do its port builds? > > Yeah (4.x chroot), but I can't think what aspect of the 5.3 kernel > might be causing the userland dynamic linker to misbehave. When I get a chance I can try updating to 4.x stable and try that to see if it makes any difference. I was wondering if the version bump for shared libraries on 5.x to do with 4.x compat could have had any impact, but it sounds like it wouldn't have. -- Greg Lewis Email : glewis@eyesbeyond.com Eyes Beyond Web : http://www.eyesbeyond.com Information Technology FreeBSD : glewis@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041014210947.GA7680>