From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from ptx.hi.pengutronix.de ([2001:6f8:1178:2:5054:ff:fec0:8e10] ident=Debian-exim) by metis.ext.pengutronix.de with esmtp (Exim 4.72) (envelope-from ) id 1Whz0T-0006iC-Tv for ptxdist@pengutronix.de; Wed, 07 May 2014 12:23:21 +0200 Received: from mol by ptx.hi.pengutronix.de with local (Exim 4.80) (envelope-from ) id 1Whz0Y-0007Bl-77 for ptxdist@pengutronix.de; Wed, 07 May 2014 12:23:26 +0200 Date: Wed, 7 May 2014 12:23:26 +0200 From: Michael Olbrich Message-ID: <20140507102326.GC17823@pengutronix.de> References: <20140507080758.GA17823@pengutronix.de> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: Subject: Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2013.12.2 released Reply-To: ptxdist@pengutronix.de List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: ptxdist@pengutronix.de Hi, On Wed, May 07, 2014 at 10:41:33AM +0200, Alexander Dahl wrote: > Am 2014-05-07 10:07, schrieb Michael Olbrich: > > - All generated toolchain archives are now XZ comressed. > > Who generates this? Can I do this when building the toolchain? Up to now > I do this manually. this is done in the build_all_v2.mk script. For one toolchain I use e.g. $ ./build_one.sh arm-v7a-linux-gnueabihf This does some matching to find the correct config and calls build_all_v2.mk with the correct target to build on toolchain. The result is in inst/ and a tarball and Debian package (if dpkg is available) are generated in dist/. Michael -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | -- ptxdist mailing list ptxdist@pengutronix.de