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. 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 <[EMAIL PROTECTED]> http://openmoko.org/ ============================================================================ Software for the world's first truly open Free Software mobile phone _______________________________________________ devel mailing list [email protected] https://lists.openmoko.org/mailman/listinfo/devel
