From: MC Potgieter <mc.rdc@mweb.co.za>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Building a older version toolchain using a a newer version ptxdist
Date: Wed, 16 May 2012 11:31:53 -0700 [thread overview]
Message-ID: <CAPTGAH5PoeCceinXPzO9ANt8Wq8G7ivxqmLOvJuyUgf_DjG55w@mail.gmail.com> (raw)
In-Reply-To: <CAPTGAH4KzpDOFiA0Q_-VJyJJqOiaZER6HmkJHr_BY6dsvTxUhQ@mail.gmail.com>
On Wed, May 16, 2012 at 10:50 AM, MC Potgieter <mc.rdc@mweb.co.za> wrote:
> On Wed, May 16, 2012 at 10:39 AM, Juergen Beisert <jbe@pengutronix.de> wrote:
>> MC Potgieter wrote:
>>> I'm trying to build the latest available combination of tools
>>> (ptxdist, BSP and toolchain)
>>>
>>> My versions are (this is the latest available tools):
>>>
>>> ptxdist: 2012.05.0
>>> oselas toolchain: 2011.11.0
>>> oselas BSP: 2012.02.0
>>>
>>> After installing ptxdist I configure the toolchain:
>>>
>>> ptxdist select ptxconfigs/arm-v4t-linux-gnueabi_gcc-4.6.2_glibc-2.14.1_binutils-2.21.1a_kernel-2.6.39-sanitized.ptxconfig
>>>
>>> and then try and build it, but I get:
>>>
>>> error: The ptxconfig file version and ptxdist version do not match:
>>>
>>> configfile version: 2011.11.0
>>> ptxdist version: 2012.05.0
>>>
>>> Which ptxconfig should I select to get matching versions (where is it
>>> located)? Or should I force the build?
>>
>> Building every OSELAS.Toolchain-2011.11.0/1 is tested with PTXdist-2011.11.0. If
>> you want to be safe, install PTXdist-2011.11.0 and build the toolchain with
>> this version.
>> If you are brave, you can force the build also with the PTXdist-2012.05.0.
>> Most of the time it will work, but this version combination is not tested here.
>> So, in case of trouble we will blame you ;)
>>
>> Regards,
>> Juergen
>>
>> --
>> Pengutronix e.K. | Juergen Beisert |
>> Linux Solutions for Science and Industry | http://www.pengutronix.de/ |
>>
>> --
>> ptxdist mailing list
>> ptxdist@pengutronix.de
>
> Hi Juergen,
>
> 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).
> If I'm going to compile BSP 2012.02.0 when using ptx 2011 and
> toolchain 2011 it is going to give me the same error.
>
> What should I do? What combination of tools should I use to compile
> the latest BSP?
>
> MC
Or is the BSP compiled independent of the ptx and toolchain versions?
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2012-05-16 18:32 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 [this message]
2012-05-21 10:59 ` Alexander Dahl
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=CAPTGAH5PoeCceinXPzO9ANt8Wq8G7ivxqmLOvJuyUgf_DjG55w@mail.gmail.com \
--to=mc.rdc@mweb.co.za \
--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