From owner-freebsd-ports Sat Aug 8 16:23:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA07074 for freebsd-ports-outgoing; Sat, 8 Aug 1998 16:23:35 -0700 (PDT) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA06968; Sat, 8 Aug 1998 16:21:57 -0700 (PDT) (envelope-from hoek@FreeBSD.org) From: Tim Vanderhoek Received: (from hoek@localhost) by freefall.freebsd.org (8.8.8/8.8.5) id QAA13858; Sat, 8 Aug 1998 16:21:55 -0700 (PDT) Date: Sat, 8 Aug 1998 16:21:55 -0700 (PDT) Message-Id: <199808082321.QAA13858@freefall.freebsd.org> To: sanpei@sanpei.org, hoek@FreeBSD.ORG, freebsd-ports@FreeBSD.ORG Subject: Re: ports/7509 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Synopsis: ncftp-2.4.3 on packages-2.2.7 is not runable under 2.2.7-RELEASE State-Changed-From-To: open-closed State-Changed-By: hoek State-Changed-When: Sat Aug 8 16:14:15 PDT 1998 State-Changed-Why: This is a known bug and can't be fixed for 2.2.7-RELEASE since a -RELEASE is, well, -RELEASEd.... The problem results (if memory serves correctly) from ncftp2 having grabbed a header from the ncurses port when the package was being built. There doesn't appear to be any work-around (I just tried forcing it to use the libncurses.so from the ncurses port, but that core dumps). You need to either build ncftp2 from the source, using the port, or you need to grab a newer ncftp2 package (I'm not sure if we have a newer one available yet, but as you noticed, an older one works, too :). The bug has been fixed in newer versions of the ncurses port by setting MANUAL_PACKAGE_BUILD. Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message