From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2013.12.2 released
Date: Wed, 7 May 2014 12:23:26 +0200 [thread overview]
Message-ID: <20140507102326.GC17823@pengutronix.de> (raw)
In-Reply-To: <e7117db2d4794aa4029231adbe1f1a0a@idefix.lespocky.dyndns.org>
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
next prev parent reply other threads:[~2014-05-07 10:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-07 8:07 Michael Olbrich
2014-05-07 8:41 ` Alexander Dahl
2014-05-07 10:23 ` Michael Olbrich [this message]
2014-05-07 11:16 ` Alexander Dahl
2014-05-07 12:15 ` Michael Olbrich
2014-05-07 12:30 ` Bernhard Walle
2014-05-07 14:39 ` Uwe Kleine-König
2014-05-07 13:01 ` Alexander Dahl
2014-05-07 13:08 ` Michael Olbrich
2014-09-24 13:43 ` Tim Sander
2014-09-24 18:01 ` Uwe Kleine-König
2014-09-26 6:09 ` Tim Sander
2014-09-26 6:46 ` Michael Olbrich
2014-09-29 13:47 ` Tim Sander
2014-09-29 13:56 ` Tim Sander
2014-10-01 13:02 ` Michael Olbrich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140507102326.GC17823@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox