From owner-freebsd-stable Wed May 9 16:19:42 2001 Delivered-To: freebsd-stable@freebsd.org Received: from scribe.pobox.com (scribe.pobox.com [208.210.124.35]) by hub.freebsd.org (Postfix) with ESMTP id 39A6337B423 for ; Wed, 9 May 2001 16:19:40 -0700 (PDT) (envelope-from jamil_taylor@pobox.com) Received: from pobox.com (jamil.netaxs.com [207.8.144.30]) by scribe.pobox.com (Postfix) with ESMTP id 38AC632585; Wed, 9 May 2001 19:19:39 -0400 (EDT) Message-ID: <3AF9D08A.FB2BD58@pobox.com> Date: Wed, 09 May 2001 19:19:38 -0400 From: Jamil Taylor X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.3-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Mike Meyer Cc: pir@pir.net, freebsd-stable@FreeBSD.ORG Subject: Re: applix 5.0 failing References: <20010509125705.B14261@pir.net> <15097.46418.265527.654361@guru.mired.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hmm. I built 4.3 STABLE right after a cvsup about four days ago. Applix works fine for me without me having to make any changes. I presume if I was to cvsup now, Applix would break? Mike Meyer wrote: > The problem is that getresuid is now available in a library that > Applixware doesn't link dynamically. The gtk port finds it at config > time, and tries to use it. When invoked from Applixware, it can't find > it because the library is missing, and you get the result you see > here. > > The gtk port maintainer claims that Applixware is at fault for not > having statically linked gtk. I'm not sufficiently conversant with > FreeBSD's shared library mechanisms, but I figure that the gtk library > should dynamically link in all the libraries it needs. Since that > isn't happening, you have to work around the problem. > > If you clean the gtk port, then do "make config", you can go back and > turn off HAVE_GETRESUID by hand in the appropriate include file. I > forget the details, but I've been through it a couple of times. The > resulting gtk library will then use a workaround so that you don't > lose any functionality. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message