From: Alexander Dahl <post@lespocky.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Which versionS should i use?
Date: Wed, 02 Jul 2014 09:45:50 +0200 [thread overview]
Message-ID: <3b5b459260fe87dca747e7976e58d04c@idefix.lespocky.dyndns.org> (raw)
In-Reply-To: <53B2DD88.5080300@webware-experts.de>
Hei hei,
Am 2014-07-01 18:10, schrieb Norbert Roos:
> I downloaded the project "phyCORE-OMAP4-2013.01.0", which uses ptxdist
> 2013.01.0. Ok so far.
Is this a board support package? Does it contain a toolchain? Where did
you get it?
> Now i want to build a toolchain, but there is no OSELAS 2013.01.1
> toolchain. If i take a different toolchain, ptxdist gives me an error
> about a mismatching ptxdist version (i tried it with the toolchain
> versions 2012.12.1 and 2013.12.2).
I guess you mean when compiling the toolchain?
> I could of course ignore the error, but i'd like to do it the right
> way. So what is the correct way then?
For compiling the toolchain, install the exact ptxdist version wanted.
As said before, it's no problem to have several ptxdist versions
installed in parallel.
> And do i see it right that the downloaded project package
> (phyCORE-OMAP4-2013.01.0) is the BSP, or are these two different
> packages?
It's not clear what you actually downloaded and where, so we can not
easily have a look inside. ;-)
In general: toolchain and BSP are two different things.
Besides: it's possible to set a toolchain version in the BSP package, so
maybe in this phyCORE BSP there's set one. Which is it?
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:[~2014-07-02 7:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-01 16:10 Norbert Roos
2014-07-01 18:54 ` Bernhard Walle
2014-07-02 7:45 ` 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=3b5b459260fe87dca747e7976e58d04c@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