Hi Steve,

Steve Juma wrote:
> I was previously using the toolchain that came with the FriendlyArm
> DVD so I thought I might compile some of the OSELAS.Toolchain() ones.
> My steps and results are as follows.
>
> $ ptxdist version
> 2012.07.0
>
> $ ptxdist select configs/ptxconfig
> info: selected ptxconfig:
>       'configs/ptxconfig'
>
> ptxdist platform configs/platform-friendlyarm-mini6410/platformconfig
> info: selected platformconfig:
>       'configs/platform-friendlyarm-mini6410/platformconfig'
>
> found and using toolchain:
> '/opt/OSELAS.Toolchain-2011.03.0/arm-1136jfs-linux-gnueabi/gcc-4.5.2-glibc-
>2.13-binutils-2.21-kernel-2.6.36-sanitized/bin'
>
> ptxdist go
> error:  The ptxconfig file version and ptxdist version do not match:
>
>         configfile version: 2011.10.1
>         ptxdist version:    2012.07.0
>
>         You can either migrate from an older ptxdist release with:
>         'ptxdist migrate'
>
>         or, to ignore this error, add '--force'
>         to ptxdist's parameters, e.g.:
>         'ptxdist --force go'
>
> ptxdist --force -n5 go
>
> [After a while doing some work]
>
>
> ---------------------
> target: kmod-9.tar.xz
> ---------------------
>
>
> error: empty parameter to 'ptxd_make_get'

Whenever you use a different PTXdist version than the BSP project was prepared 
for, you can use the "--force". This might work - but sometimes not.

The better way to adapt the BSP project to a more recent version of PTXdist is 
to use the "migrate" command.

But keep in mind: Do not blindly accept all questions with a 'yes'. Better is 
to answer "no". With the "menuconfig" command you can enable everything later 
on if you miss something in your root filesystem.

Another way is to run:

$ ptxdist --force platformconfig
<and leave the menu without any change, but then save the new config>
$ ptxdist --force menuconfig
<and leave the menu without any change, but then save the new config>

This will also adapt the configuration to the new PTXdist version. It will 
also re-organize the dependencies so the next "ptxdist go" should work as 
expected.

Regards,
Juergen

-- 
Pengutronix e.K.                              | Juergen Beisert             |
Linux Solutions for Science and Industry      | http://www.pengutronix.de/  |

Reply via email to