From owner-freebsd-ports@FreeBSD.ORG Fri Jul 6 01:05:04 2007 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 815E716A400 for ; Fri, 6 Jul 2007 01:05:04 +0000 (UTC) (envelope-from me@janh.de) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.179]) by mx1.freebsd.org (Postfix) with ESMTP id 068EE13C459 for ; Fri, 6 Jul 2007 01:05:03 +0000 (UTC) (envelope-from me@janh.de) Received: from [80.171.114.220] (helo=janh.freebsd) by mrelayeu.kundenserver.de (node=mrelayeu3) with ESMTP (Nemesis), id 0MKxQS-1I6c3e0cpW-0008HO; Fri, 06 Jul 2007 02:52:26 +0200 Message-ID: <468D9246.9060600@janh.de> Date: Fri, 06 Jul 2007 02:52:22 +0200 From: Jan Henrik Sylvester User-Agent: Thunderbird 2.0.0.4 (X11/20070615) MIME-Version: 1.0 To: freebsd-ports@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX182Q1iVqDx2CjxwAqMeqvik8aJCpDmq1VQFUXi xp8ZARjkpY9scNsuzi+CRM312+VELqy38DR9XV/CVuXqycw6gb ub5D4JjuAwXYdAD2lt5nA== Cc: David Southwell Subject: Portupgrade lynx2.-8-6 compile failure X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jul 2007 01:05:04 -0000 David Southwell wrote: >Compile failure >./LYCharSets.c: In function `HTMLGetEntityUCValue': >./LYCharSets.c:878: error: `unicode_entities' undeclared (first use in >this function) >Stop in /usr/ports/www/lynx/work/lynx2-8-6/src. I had this problem, too. Though, I have the latest ports tree (via portsnap), I am missing patch-LYCharSets (from 12 hours ago). With that, the port builds and installs fine. My Makefile is not the latest, either. Maybe it is because the last update of the port did not change the PORTREVISION (or PORTVERSION)? That should not interfere with portsnap updating the port, or should it? Or does portsnap have a "hiccup"? Rather clueless Jan Henrik