mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Alexander Dahl <post@lespocky.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2013.12.2 released
Date: Wed, 07 May 2014 13:16:10 +0200	[thread overview]
Message-ID: <5b341d629e4cdada6ccbc3619c262734@idefix.lespocky.dyndns.org> (raw)
In-Reply-To: <20140507102326.GC17823@pengutronix.de>

Hei hei, 

Am 2014-05-07 12:23, schrieb Michael Olbrich:
> 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/.

I like the idea, however it does not work out of the box because of line
36 in build_all_v2.mk … ;-)

But handy anyway, thanks for the hint.

Greets
Alex

-- 
»With the first link, the chain is forged. The first speech censured,
the first thought forbidden, the first freedom denied, chains us all
irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie)
*** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601  D1D5 8FBA 7744 CC87 10D0 ***

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2014-05-07 11:16 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
2014-05-07 11:16     ` Alexander Dahl [this message]
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=5b341d629e4cdada6ccbc3619c262734@idefix.lespocky.dyndns.org \
    --to=post@lespocky.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