[Meego-porting] Porting MeeGo on ARM11

Francisco Javier Cuadrado francisco.cuadrado at iunika.net
Thu Nov 4 09:00:15 PDT 2010


2010/11/4 Carsten Munk <carsten at maemo.org>:
> 2010/11/4 Alexander Kanevskiy <alexander.kanevskiy at nokia.com>:
>> ARMv7 wouldn't help as armv7 can't be used as basis for armv6.
>> compatibility is maintained only backwards.
>>
>> By default, MeeGo project in OBS needs to be self-contained. That's
>> why the idea is importing sources into separate project.
>> However to start building it, you need to have somewhere "bootstrap"
>> of linux system where at least minimal set of tools (like
>> glibc/gcc/rpm/coreutils) working. This is the place where separate
>> project with armv5 binaries are needed. They don't need to be same as
>> your targeted armv6 packages. you just need to have starting point
>> with basic tools working to enable at least something to build for
>> armv6.
>> You add it in the beginning, make a first round of building your armv6
>> packages to bootstrap armv6 repo, afterwards you can remove that armv5
>> bins project.
>
> I have a bit of a skunkworks project with building 'meego core'
> ARMv6+vfp at the moment at a lone server.
>
> I actually took a different approach - In OBS, 'armv7el' means the
> builder supports up to ARMv7 instructions.
>
> We have a bit of an advantage in MeeGo ARM because our gcc doesn't
> baseline to armv7, it uses what it's given as optimization flags.
>
> In the prjconf of my new project, I added Changetarget:
> armv6-meego-linux and it started using the right optimization and
> armv6l.rpm
>
> Then I dumped in all the source packages from Core and it started out
> with the minimal base as listed in the Trunk prjconf and compiled that
> into armv6l.rpm first.
>

I did something similar, I create a MeeGo project in my OBS instance
with armv6el build target using armv7 binaries (I copied them into
:full project directory), then OBS starts to compile some base
packages, but after some of them it stops and do nothing more.

I think, if I undestand you, that you did a similar, but different,
approach. Did you configure your MeeGo project with armv7el build
target and only changed prjconf?

> I'm currently at 499 built packages and will obviously need to scan
> for any traces of ARMv7. I'll keep you updated, I guess, but I haven't
> tried anything to allow proper multicore ARM.
>

Ok, thanks.

> BR
> Carsten Munk
>



-- 
Francisco Javier Cuadrado

SPAIN-CHINA-HONG KONG-POLAND

Spain Main: +34-910005436
Centro Empresarial Eisenhower
C/ Cañada Real de Merinas, 25
Edificio 7 - oficina 1ºC
28042 Madrid

http://www.iunika.com


More information about the MeeGo-porting mailing list