ARMv4 vs ARMv6

Koen Kooi k.kooi at student.utwente.nl
Thu Oct 16 19:06:34 CEST 2008


Op 16 okt 2008, om 18:41 heeft Harald Welte het volgende geschreven:

> Hi Andy, Koen,
>
> On Thu, Oct 16, 2008 at 03:01:54PM +0100, Andy Green wrote:
>> |  You might have
>> | something else installed on the same box that required the v4  
>> ones too,
>> | so the /usr/lib and /usr/lib64 type thing is needed for same  
>> library /
>> | different arch coexistence on one system.  It is like the i386 /  
>> x86_64
>> | multiarch situation.
>> |
>> |> As Harald, Graeme and I said before: no, it's not like that
>>
>> Can you spell it out for this idiot WHY it isn't like that?  It's not
>> like that because we can't handle parallel install of same lib of
>> different arch?  Or we can handle it fine already?  How?  Just  
>> telling
>> me I am wrong and OE is perfect is not really advancing my or anyone
>> else's understanding of the situation.
>
> From what I know:
> Your application will depend on some library.  The dependency is  
> expressed as a
> library package name.  Two packages (one armv4, one armv6) provide  
> this
> library.  Either of the two will fulfill that dependency.  On an  
> armv6 device,
> opkg will prefer the armv6 over the armv4 from the feed.  An armv4  
> device will
> not even look at the armv6 feed and thus only see the armv4 package  
> and install
> it.  so by default you should get whatever is best for your device.

And even if it did look at the armv6 feed it wouldn't use it :)

regards,

Koen

>
>
> The difference to i386/x86_64 is exactly this:
> * x86_64 application cannot link i386 lib
> * i386 application cannot link x86_64 libt
> * armv6 application can link armv4 lib
> * armv4 application can link armv6 lib
>
> Cheers,
> -- 
> - Harald Welte <laforge at openmoko.org>          	        http://openmoko.org/
> = 
> = 
> = 
> = 
> = 
> = 
> ======================================================================
> Software for the world's first truly open Free Software mobile phone
>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://lists.openmoko.org/pipermail/devel/attachments/20081016/00db173b/attachment.pgp 


More information about the devel mailing list