From owner-freebsd-arm@freebsd.org  Tue Jan  3 17:02:08 2017
Return-Path: <owner-freebsd-arm@freebsd.org>
Delivered-To: freebsd-arm@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 7D1F5C9D69E
 for <freebsd-arm@mailman.ysv.freebsd.org>;
 Tue,  3 Jan 2017 17:02:08 +0000 (UTC)
 (envelope-from tech-lists@zyxst.net)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com
 [66.111.4.26])
 (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 522DB1CAD
 for <freebsd-arm@freebsd.org>; Tue,  3 Jan 2017 17:02:08 +0000 (UTC)
 (envelope-from tech-lists@zyxst.net)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44])
 by mailout.nyi.internal (Postfix) with ESMTP id 0049A2060F
 for <freebsd-arm@freebsd.org>; Tue,  3 Jan 2017 12:02:06 -0500 (EST)
Received: from frontend1 ([10.202.2.160])
 by compute4.internal (MEProxy); Tue, 03 Jan 2017 12:02:06 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=zyxst.net; h=
 content-transfer-encoding:content-type:date:from:in-reply-to
 :message-id:mime-version:references:subject:to:x-me-sender
 :x-me-sender:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=Nq9UvYgPojFqyjH
 +MV3V6OVToxQ=; b=VfqDfIE0G/dfPxrIzAmSIhktLejPQTAR7FS5KH+J/BD30OS
 iltNj4+rmxjRJyEHMhEilflb6CmdpCAxE482EVOFhSOeDZRjd4H64dXnKJN1W3iI
 zmk6obGpAwchks1salDF+5v0atieYhB49y91u8kitO9pUWvJQkG8hec3toyE=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=
 messagingengine.com; h=content-transfer-encoding:content-type
 :date:from:in-reply-to:message-id:mime-version:references
 :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s=
 smtpout; bh=Nq9UvYgPojFqyjH+MV3V6OVToxQ=; b=o10BqRWIhGyubb3e1Idq
 jCEsGgWok6yT8V0bXUhycNdOB54z+tHICCCn9V2A85rPM409Sq+1vfp1POX2NNy1
 DwWxtIRQAkVZfV1dXdNQV6wIQXwLKmoHy3IbOFDMn2Fjypka/oaNe3YvN8SzLpVb
 MrS44zvf66agXERNQ7rxgFY=
X-ME-Sender: <xms:DtlrWDH_r2mKqUCp1eUghEko2ZhggM3scKeB6euyElPfrHVb6J1hYA>
X-Sasl-enc: Ja9I0uaoghXIkoQkxif2RjFo8UVntCt/O5pXBPGELHkZ 1483462926
Received: from pumpkin.growveg.org (pumpkin.growveg.org [82.70.91.101])
 by mail.messagingengine.com (Postfix) with ESMTPA id 962227F075
 for <freebsd-arm@freebsd.org>; Tue,  3 Jan 2017 12:02:06 -0500 (EST)
Subject: Re: aarch64 on pi3 advice
References: <05fee124-ad8f-43e8-79d9-ccb99bc83214@zyxst.net>
 <F3906407-13F0-4D3E-B4DE-440CD5D2C7D7@kientzle.com>
 <20170103081759.40624fbd@X220.alogt.com>
To: freebsd-arm@freebsd.org
From: tech-lists <tech-lists@zyxst.net>
Message-ID: <7f42af09-4698-9866-9ffa-7800c0bb95ba@zyxst.net>
Date: Tue, 3 Jan 2017 17:02:03 +0000
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101
 Thunderbird/45.5.1
MIME-Version: 1.0
In-Reply-To: <20170103081759.40624fbd@X220.alogt.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-arm@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: "Porting FreeBSD to ARM processors." <freebsd-arm.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arm/>
List-Post: <mailto:freebsd-arm@freebsd.org>
List-Help: <mailto:freebsd-arm-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Jan 2017 17:02:08 -0000

On 03/01/2017 00:17, Erich Dollansky wrote:
> I am not able to compile and link any programs on my Raspberry.
> Compiling works but linking fails. This is a known problem. Linking on
> a x86 machine results in an working binary if you have the patched
> bin-utils.

How does one compile ports into the image? aarch64-binutils is installed
on the x86 machine. Should I take this question to the crochet list?

many thanks,
-- 
J.