From owner-freebsd-ports@FreeBSD.ORG  Wed Jan 29 00:07:53 2014
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id AC3F7FDE
 for <freebsd-ports@freebsd.org>; Wed, 29 Jan 2014 00:07:53 +0000 (UTC)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com
 [66.111.4.28])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 7D102186F
 for <freebsd-ports@freebsd.org>; Wed, 29 Jan 2014 00:07:53 +0000 (UTC)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43])
 by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 13F2F20A56
 for <freebsd-ports@freebsd.org>; Tue, 28 Jan 2014 19:07:52 -0500 (EST)
Received: from frontend2 ([10.202.2.161])
 by compute3.internal (MEProxy); Tue, 28 Jan 2014 19:07:52 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=
 messagingengine.com; h=from:to:subject:date:message-id
 :mime-version:content-type; s=smtpout; bh=vJ5XH9DQmq7f0/9ikdXquC
 3pzZ0=; b=XTLVP3dCLm4QPsueGJ/EIMT2J3mqqjovFQp63TtR89ui78yxA/3XpL
 HTqONs2QKzxZaRLhaXlDCLTbdhN9VkUaAoCykg9ujBtGY23UzboyP2etiqfdBbIF
 kL3NMhRrvKaNxmT+qH5+ptJ1mf1QGSFsRUE1S5ANSoCFcdfsCrKpM=
X-Sasl-enc: JkeEHDmD0N0ibuztHRGF1lrSMn0QuP6SguEzZCmNQRL3 1390954071
Received: from [10.0.17.24] (unknown [216.13.232.2])
 by mail.messagingengine.com (Postfix) with ESMTPA id B4718680112
 for <freebsd-ports@freebsd.org>; Tue, 28 Jan 2014 19:07:51 -0500 (EST)
From: "Stephen Forsyth" <mr.f@me.com>
To: freebsd-ports@freebsd.org
Subject: Error compiling ports on FreeBSD 10 for ARM (Raspberry Pi)
Date: Tue, 28 Jan 2014 16:07:50 -0800
Message-ID: <4942E753-C744-43E4-8FA1-30959298A3BB@me.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate (1.7.2r3905)
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jan 2014 00:07:53 -0000

Hi Ports subscribers,

I've been trying out a recent build of what may become the FreeBSD 10.0 
release for ARM ("FreeBSD 10.0-RELEASE (RPI-B) #0 r261135"). There 
aren't any non-x86 pkg builds available yet, so I used portsnap to 
install ports.

All the ports I have tried to install (tmux, curl, pkg, sudo) fail with 
the same error:

   /usr/lib/libcrypto.a(pmeth_lib.o):(.data+0x0): undefined reference to 
`rsa_pkey_meth'
   cc: error: linker command failed with exit code 1 (use -v to see 
invocation)
   *** [pkg-static] Error code 1

For example, if I go to /usr/ports/sysutils/tmux and run "make install" 
as root, and fifteen minutes later the build fails with this error.

Does anyone know how what the cause of an issue like this might be? I'm 
relatively new to FreeBSD, so I'm out of my depth when it comes to 
compile issues on a new architecture. Searches for rsa_pkey_meth linker 
errors using a popular web search engine didn't yield anything that 
looked useful. Are packages being signed after they are built?

Thank-you in advance for any thoughts or insights that you may have,


Steve.