Yes, I can confirm this solves the problem. Maybe we need to add a few testcases to catch this issue, similar to my testcase with 
Arch_i586.compatibleWith( Arch_i686 )

Thanks,
Anas

On Wed, Jul 6, 2011 at 9:09 AM, Michael Andres <ma@suse.de> wrote:
On Wednesday 06 July 2011 08:19:52 Zhang, Qiang Z wrote:
> In MeeGo 1.2 or suse, globals in Arch.cc are initialized before
> RepoInfo.cc, while in MeeGo 1.3 RepoInfo.cc are initialized before Arch.cc.

That's it ;(

> So the question is how to let gobals in Arch.cc being initialized first,
> how to control the initialization sequence.

We currently depend on the linker, and it might be the policy changed with
4.6, that's why it broke. I'll see how to fix his.

For now you may try this: Look into the zypp/CMakeLists.txt. You'll find the
ADD_LIBRARY line. Reverse the input list of sources:

 + list( REVERSE zypp_lib_SRCS )
   ADD_LIBRARY(zypp SHARED ${zypp_lib_SRCS})

The same change on MeeGo 1.2 or suse will trigger the bug.

--

cu,
   Michael Andres

+------------------------------------------------------------------+
Key fingerprint = 2DFA 5D73 18B1 E7EF A862  27AC 3FB8 9E3A 27C6 B0E4
+------------------------------------------------------------------+
Michael Andres   SUSE LINUX Products GmbH, Development,   ma@suse.de
GF:Jeff Hawn,Jennifer Guild,Felix Imendörffer, HRB16746(AG Nürnberg)
Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0
+------------------------------------------------------------------+

--
To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org
For additional commands, e-mail: zypp-devel+help@opensuse.org