From owner-freebsd-current Thu Oct 18 8: 6:26 2001 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id CC19737B405 for ; Thu, 18 Oct 2001 08:06:19 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f9IF6IV19242; Thu, 18 Oct 2001 09:06:18 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id f9IF6F721331; Thu, 18 Oct 2001 09:06:15 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200110181506.f9IF6F721331@harmony.village.org> To: Garance A Drosihn Subject: Re: applix 5.0 and current Cc: Brooks Davis , current@FreeBSD.ORG In-reply-to: Your message of "Tue, 16 Oct 2001 18:17:08 EDT." References: <20011016124313.A12105@Odin.AC.HMC.Edu> Date: Thu, 18 Oct 2001 09:06:15 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message Garance A Drosihn writes: : At 12:43 PM -0700 10/16/01, Brooks Davis wrote: : >I've been trying to get applix 5.0 to work and I've been running into : >some interesting problems. The first one was that current has the : >getresuid syscall and the gtk12 build detects and uses it. Unfortunately : >FreeBSD 3.x and 4.x don't have this syscall so you can't use libgtk12 : >with old libc's if it's built on current. I was able to build a new : >one with use of getresuid disabled and that got the main program to : >load. It appears that the gtk12 port needs to disable this dubious : >feature or getresuid needs to be MFC'd all the way back to 3.x. : : If I understand the above, then you compiled something on -current : and you wanted it to run on release-4 and release-3. I do not think : you can count on that. If you want a program to run on multiple : releases, then you'll need to compile it on the lowest release, not : on -current. Yup. I've done things like creating a chroot area and mounting a 3.5 or 2.2.8 cdrom and then mounting another fs in that chroot area to access the sources and then building it there. But as you go back in time in FreeBSD it gets much harder to have ports be supported... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message