From owner-freebsd-stable Sun Feb 11 17:58: 0 2001 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 7D38937B401 for ; Sun, 11 Feb 2001 17:57:58 -0800 (PST) Received: from billy-club.village.org (billy-club.village.org [10.0.0.3]) by rover.village.org (8.11.2/8.11.0) with ESMTP id f1C1vvh15073; Sun, 11 Feb 2001 18:57:57 -0700 (MST) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (localhost [127.0.0.1]) by billy-club.village.org (8.11.1/8.8.3) with ESMTP id f1C1tYE05473; Sun, 11 Feb 2001 18:55:35 -0700 (MST) Message-Id: <200102120155.f1C1tYE05473@billy-club.village.org> To: Pekka Savola Subject: Re: 3.5-S->4.2-S: still fail w/ setresuid on miniperl Cc: freebsd-stable@FreeBSD.ORG In-reply-to: Your message of "Sun, 11 Feb 2001 17:37:42 +0200." References: Date: Sun, 11 Feb 2001 18:55:34 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Pekka Savola writes: : As a lot of others including some @FreeBSD.org people, I got: I'd suggest building -DNOPERL when upgrading. If that works (I have no 3.x boxes fast enough to test this on), then let me know so I can update UPDATING. : make buildworld -DNOPERL works around this, of course. Oh, that's different, I'll update UPDATING. : But shouldn't this be fixed? Or are 3.x users such a diminishing : community it's not worth risking breaking the tree? I think it should just work, but I'm afraid to touch perl to fix it :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message