From owner-freebsd-ports@freebsd.org Sun Sep 13 09:00:51 2015 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 A11F79C8119 for ; Sun, 13 Sep 2015 09:00:51 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (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 5A95918D8; Sun, 13 Sep 2015 09:00:51 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1Zb39X-000CAd-1h; Sun, 13 Sep 2015 11:00:51 +0200 Date: Sun, 13 Sep 2015 11:00:51 +0200 From: Kurt Jaeger To: Alfred Perlstein , freebsd-ports@freebsd.org Subject: Re: Anyone got RethinkDB working in FreeBSD? Message-ID: <20150913090050.GP36682@home.opsec.eu> References: <20150911091155.GU13922@pol-server.leissner.se> <20150911152118.GK36682@home.opsec.eu> <20150911162225.GU13922@pol-server.leissner.se> <20150911171305.GL36682@home.opsec.eu> <20150911192801.GM36682@home.opsec.eu> <20150912090128.GN36682@home.opsec.eu> <55F4E408.6010204@freebsd.org> <20150913085345.GO36682@home.opsec.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150913085345.GO36682@home.opsec.eu> X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Sep 2015 09:00:51 -0000 Hi! > The makefile of rethinkdb creates the ...a file with > > ar crsT > > which is different from > > ar -r > > I'll change the creation of the .a files and report back. The cause seems to be the 'T' which, according to the manual: T Make the specified archive a thin archive. If it already exists and is a regular archive, the existing members must be present in the same directory as archive. and this seems to cause the error file format not recognized; treating as linker script -- pi@opsec.eu +49 171 3101372 5 years to go !