X-Original-To: alpine-devel@lists.alpinelinux.org Delivered-To: alpine-devel@lists.alpinelinux.org Received: from mail-fx0-f219.google.com (mail-fx0-f219.google.com [209.85.220.219]) by lists.alpinelinux.org (Postfix) with ESMTP id 343C31EFC00 for ; Thu, 30 Jul 2009 12:47:39 +0000 (UTC) Received: by fxm19 with SMTP id 19so636831fxm.26 for ; Thu, 30 Jul 2009 05:47:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:from:to:cc :in-reply-to:references:content-type:date:message-id:mime-version :x-mailer:content-transfer-encoding; bh=gpIq50OGA0cPalBMdFCGAGZt2QB4L8Lrt6sO4bofvgc=; b=AnbtbdsZlEQdy5GV0DqUQvwyQeC8UfmfzFKeuMWd4TOpS0S0BWoETJ4u6eqoRAhZby J/0iLuhrY9L9k1qLaJHoBgCPS8zvYaLwF3kFNmNFmj0EZuRJUxilvpHRw+NStivAJgl5 J4zQgZGh11+hMPX2fDgs4OMMkiotm4tnvzQ/c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:date :message-id:mime-version:x-mailer:content-transfer-encoding; b=Qhr0hUaDzjJCHCShbeAy47WngNv0FRQwVpuFsd9dRTZFNoaysNcGHq3N48zmJc64QF J0rCBZ4+SgrKK+jWZ5CsVBEgcAWvZzZ3tHBdrZmkaTjQU7NNbeISb9txtTdcznrUrLGz hRoJa+ZMegk3h3qPEsmt8S7zvPfbP1N1+9E8A= Received: by 10.103.95.1 with SMTP id x1mr664722mul.92.1248958058824; Thu, 30 Jul 2009 05:47:38 -0700 (PDT) Received: from ?10.65.65.1? ([90.149.199.29]) by mx.google.com with ESMTPS id t10sm13392397muh.30.2009.07.30.05.47.36 (version=SSLv3 cipher=RC4-MD5); Thu, 30 Jul 2009 05:47:37 -0700 (PDT) Subject: Re: [alpine-devel] Multi architecture support From: Natanael Copa To: Mark Constable Cc: alpine-devel@lists.alpinelinux.org In-Reply-To: <4A713B06.9050101@renta.net> References: <4A713B06.9050101@renta.net> Content-Type: text/plain Date: Thu, 30 Jul 2009 14:48:38 +0200 Message-Id: <1248958118.19561.33.camel@localhost.localdomain> X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: Mime-Version: 1.0 X-Mailer: Evolution 2.26.3 Content-Transfer-Encoding: 7bit On Thu, 2009-07-30 at 16:17 +1000, Mark Constable wrote: > I see the default /etc/abuild.conf has CHOST=i486-alpine-linux-uclibc > and there is no sign of a PKGBUILD arch=(i686 x86_64) equivalent so > is there a recommended way to provide multiple archs from a single > APKBUILD? > > I guess using a different /etc/abuild.conf in each build environment > would suffice but I thought I should check if there is some inbuilt > method that is not documented yet. > > I intend to build a subset of packages for i686, This is ok. > x86_64, This should work, but I have never tried it. I think most APKBUILDs will work too. Looking at Arch Linux it seems like most x86_64 bit specifics are related to PIC, which we need anyway due to our hardened toolchain. > arm8 and > possibly ppc (ps3) eventually. Those would probably require cross-compiling. I think its possible but it will probably require some redesign of abuild and extra things to consider in APKBUILDs. > I'd use separate chroots for i686 > and x86_64 and possibly use the ArchMobile qemu examle for arm8 as > I have a Beagelboard begging for some TLC. TLC? I'm not familiar with ArchMobile. Does it cross-compile or native compile in qemu? Native compile in qemu might work but is slow. Btw, i use vserver for my development of x86. Its like an advanced chroot. > Sorry about the rush of newbie questions and many thanks for the > responses. > > --markc > > > --- > Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org > Help: alpine-devel+help@lists.alpinelinux.org > --- > --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---