From: Alexander Dahl <post@lespocky.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Building a older version toolchain using a a newer version ptxdist
Date: Mon, 21 May 2012 12:59:55 +0200 [thread overview]
Message-ID: <a5852d1df07fef35e0e232b7ba827c4f@idefix.lespocky.dyndns.org> (raw)
In-Reply-To: <CAPTGAH4KzpDOFiA0Q_-VJyJJqOiaZER6HmkJHr_BY6dsvTxUhQ@mail.gmail.com>
Am 2012-05-16 19:50, schrieb MC Potgieter:
> Then what about the BSP? Will I have to use the 2011.11.0 BSP too?
> I want to take advantage of the latest packages available in the
> latest BSP (2012.02.0).
You could take the offered BSP as base for your own stuff and for
example do an `ptxdist migrate` inside.
> What should I do? What combination of tools should I use to compile
> the latest BSP?
Build the toolchain as suggested: OSELAS Toolchain 2011.11.x with the
ptxdist version it wants. You can use this toolchain for all upcoming
BSP, at least for the foreseeable future.
Use the BSP you download with the ptxdist version it wants. ptxdist
complains if the BSP is for another version of ptxdist. If you want to
have the new features of newer ptxdist versions upgrade your BSP by
using `ptxdist migrate` as stated above.
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
prev parent reply other threads:[~2012-05-21 11:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 16:56 MC Potgieter
2012-05-16 17:13 ` MC Potgieter
2012-05-16 17:39 ` Juergen Beisert
2012-05-16 17:50 ` MC Potgieter
2012-05-16 18:31 ` MC Potgieter
2012-05-21 10:59 ` Alexander Dahl [this message]
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=a5852d1df07fef35e0e232b7ba827c4f@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