From owner-freebsd-ports@freebsd.org Thu Apr 19 18:50:20 2018 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D6E39F957F6 for ; Thu, 19 Apr 2018 18:50:20 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from mail.infocus-llc.com (mail.infocus-llc.com [199.15.120.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 812757E2C5 for ; Thu, 19 Apr 2018 18:50:20 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from draco.over-yonder.net (c-75-65-60-66.hsd1.ms.comcast.net [75.65.60.66]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.tarragon.infocus-llc.com (Postfix) with ESMTPSA id 40Rntx0NF6zDF0; Thu, 19 Apr 2018 13:43:37 -0500 (CDT) Received: by draco.over-yonder.net (Postfix, from userid 100) id 40Rntw2KgDzWhg; Thu, 19 Apr 2018 13:43:36 -0500 (CDT) Date: Thu, 19 Apr 2018 13:43:36 -0500 From: "Matthew D. Fuller" To: Wojciech Puchar Cc: freebsd-ports@freebsd.org Subject: Re: cannot compile www/node Message-ID: <20180419184336.GK11255@over-yonder.net> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.9.4 (2018-02-28) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Apr 2018 18:50:21 -0000 On Thu, Apr 19, 2018 at 07:06:32PM +0200 I heard the voice of Wojciech Puchar, and lo! it spake thus: > > /usr/bin/ld:/usr/ports/www/node/work/node-v9.11.1/out/Release/obj.target/deps/v8/src/libv8_base.a: > file format not recognized; treating as linker script I've gotten this (well, something that looks like this anyway; I don't have a recent error handy so I'm going by memory) regularly on node for 6 months or so. My workaround is to set CXX to a clang I've got around from ports, and then it gets through fine. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream.