From owner-freebsd-ports@freebsd.org Tue Feb 28 03:14:53 2017 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0D30BCF05F0 for ; Tue, 28 Feb 2017 03:14:53 +0000 (UTC) (envelope-from shaojwen@aim.com) Received: from omr-a011e.mx.aol.com (omr-a011e.mx.aol.com [204.29.186.59]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C37BA27B for ; Tue, 28 Feb 2017 03:14:52 +0000 (UTC) (envelope-from shaojwen@aim.com) Received: from mtaomg-maa01.mx.aol.com (mtaomg-maa01.mx.aol.com [172.26.222.143]) by omr-a011e.mx.aol.com (Outbound Mail Relay) with ESMTP id 48A6F3800098; Mon, 27 Feb 2017 22:09:19 -0500 (EST) Received: from core-mbx01h.mail.aol.com (core-mbx01.mail.aol.com [10.73.16.211]) by mtaomg-maa01.mx.aol.com (OMAG/Core Interface) with ESMTP id 21E1B38000083; Mon, 27 Feb 2017 22:09:19 -0500 (EST) Received: from 71.114.3.186 by webprd-a81.mail.aol.com (10.72.112.246) with HTTP (WebMailUI); Mon, 27 Feb 2017 22:09:18 -0500 Date: Mon, 27 Feb 2017 22:09:18 -0500 From: Erdos New To: dim@FreeBSD.org Cc: freebsd-ports@freebsd.org Message-Id: <15a82b18bde-3cce-13ce9@webprd-a81.mail.aol.com> In-Reply-To: <6A10A9AA-EF03-4878-8F4F-5C88FE8BB4C3@FreeBSD.org> Subject: Re: seamonkey port compiling error MIME-Version: 1.0 X-MB-Message-Source: WebUI X-MB-Message-Type: User X-Mailer: JAS STD X-Originating-IP: [71.114.3.186] x-aol-global-disposition: G DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aim.com; s=20150623; t=1488251359; bh=xZJD5c+EmErunlsXg9hgj+kC//4xy35TcwHPYe2ha1c=; h=From:To:Subject:Message-Id:Date:MIME-Version:Content-Type; b=mAfYADV2Lxf6qj4WpvPFP5k6fTMAsGDY0ImFBj/xa+7lQpFAaPxFtTtiPIZFIQJuD wbUk0rTfoeWa1tE/h/AjNd1x8K0gql9cJmMk25dnMnBYxw/52pcb/95i8dZQOFlwIg 7YzoznI7gmCnL5gRh2NkGb7YkQXfUyKwwjREZsyw= x-aol-sid: 3039ac1ade8f58b4e9df77c6 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Feb 2017 03:14:53 -0000 thanks! I end up just installing the package through 'pkg' instead of building through port. afterwards it works fine. -----Original Message----- From: Dimitry Andric To: Erdos New Cc: freebsd-ports Sent: Sun, Feb 26, 2017 2:06 pm Subject: Re: seamonkey port compiling error On 26 Feb 2017, at 19:55, Erdos New via freebsd-ports wrote: > > i tried to install 'seamonkey' to my freebsd10.1 32-bit system. however, encountered errors: > root@oblivion:/usr/ports/www/seamonkey # make install > > > install seamonky: > llvm[6]: Compiling IndexBody.cpp for Release build (PIC) > llvm[6]: Compiling IndexDecl.cpp for Release build (PIC) > llvm[6]: Compiling IndexTypeSourceInfo.cpp for Release build (PIC) > llvm[6]: Compiling Indexing.cpp for Release build (PIC) > llvm[6]: Compiling IndexingContext.cpp for Release build (PIC) > llvm[6]: Linking Release Shared Library libclang.so > llvm[6]: Building Release Archive Library libclang.a > gmake[6]: Leaving directory '/usr/ports/lang/clang36/work/llvm-3.6.2.src/tools/clang/tools/libclang' > gmake[6]: Entering directory '/usr/ports/lang/clang36/work/llvm-3.6.2.src/tools/clang/tools/c-index-test' > llvm[6]: Compiling c-index-test.c for Release build > llvm[6]: Linking Release executable c-index-test (without symbols) > /usr/ports/lang/clang36/work/llvm-3.6.2.src/Release/lib/libLLVM-3.6.so: undefined reference to `futimens@FBSD_1.4' Most likely, you installed a binary package for devel/llvm36. Binary packages are now built on FreeBSD 10.3, the most recent supported version for ports, and this version has introduced a new syscall which your system does not have. The simplest solution is probably to delete the llvm36 port, and rebuild it on your 10.1 system. Then try to rebuild the Seamonkey port and its dependent ports again. Though it would be easiest if you upgraded the system to 10.3. :) -Dimitry