From owner-freebsd-arm@FreeBSD.ORG Wed Jan 22 23:58:01 2014 Return-Path: Delivered-To: freebsd-arm@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 9BD5091E for ; Wed, 22 Jan 2014 23:58:01 +0000 (UTC) Received: from mail2.asahi-net.or.jp (mail2.asahi-net.or.jp [202.224.39.198]) by mx1.freebsd.org (Postfix) with ESMTP id 6C6DA11F9 for ; Wed, 22 Jan 2014 23:58:00 +0000 (UTC) Received: from localhost (w142149.ppp.asahi-net.or.jp [121.1.142.149]) by mail2.asahi-net.or.jp (Postfix) with ESMTP id 44FB176D6A; Thu, 23 Jan 2014 08:57:54 +0900 (JST) Date: Thu, 23 Jan 2014 08:56:09 +0900 (JST) Message-Id: <20140123.085609.53072279.shigeru@os-hackers.jp> To: hiren.panchasara@gmail.com Subject: Re: my private build RaspberryPi Image is available From: shigeru@os-hackers.jp In-Reply-To: References: <20140122.190031.29969140.shigeru@os-hackers.jp> <20140122.224425.103076338.shigeru@os-hackers.jp> X-Mailer: Mew version 3.3 on Emacs 21.4 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-arm@freebsd.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jan 2014 23:58:01 -0000 >>>>> "hiren" == hiren panchasara writes: hiren> Nice work. Would you mind sharing how you created the packages? On hiren> RPi itself or you have some sort of cross-build setup? I create pkg binaries on RaspberyPi, not on cross build environment. You, maybe, have a question: "why not use cross compile enviromnet?". It is for checking -current FreeBSD/RaspberryPi is stable or not. #unfortunately, -current is not stable ;-( And I think, stable system should be build itself on itself! How to build pkg binaries are, 1) svn checkout http://svn.freebsd.org/ports/head /usr/ports 2) change to target directory 3) do 'make package' (or 'make package-recursive') 4) do 'pkg repo /usr/ports/packages' to create a pkg catalog 5) copy/rsync pkg binaries to my web site Unfortunately, there are some ports which I can't compile on -current FreeBSD/RaspberryPi. These ports requires GCC, but gcc ports in -current does not support arm/armv6. I fix some ports to compile on -current clang/llvm/FreeBSD/RaspberryPi. #It is quick hack. Currently, I do not open patches, and I think how to open information/patches. Thanks, --- YAMAMOTO Shigeru