On April 14, 2005 12:51, Alberto wrote: > Package: kdelibs > Version: 3.3.2-4.0.2 > > Tracing why kdebase does not compile for me on a k6-2: > > ] configure:28296: /usr/share/qt3/bin/uic -L > /usr/lib/kde3/plugins/designer -nounload -impl actest.h actest.ui > > ] actest.cpp > ] configure:28299: $? = 0 > ] configure:28313: result: no > ] configure:28316: error: you need to install kdelibs first. > > I got out this subtle error: > > Conflict in /usr/lib/kde3/plugins/designer/kdewidgets.so: > Plugin uses incompatible Qt library! > expected build key "i586 Linux g++-3.* full-config", got "i686 Linux > g++-3.* full-config" > I inspected kdelibs source, found many i686 references. I changed them > to i586, recompiled kdelibs and all errors dissapeared now. What are you referring to here? I see no references to i686 in the kdelibs source that could cause what you're referring to. When KDE is built, it is built as if the system were a 386. config.guess and config.sub are standard files that help the build system determine what your system is, and they shouldn't be tampered with. I have a suspicion about what's happening, though. Did you rebuild Qt on your own machine prior to rebuilding kdebase? Did you make any changes to Qt, or was it a simple download-and-build? Also, did you rebuild kdelibs _before_ this error popped up? If you did rebuild Qt, then it might have become "i586 Linux g++-3.* full-config", whereas the stock kdelibs package was built against a Qt that had "i686 Linux g++-3.* full-config". The mismatch was exposed when you tried to build kdebase (against the stock kdelibs and your own Qt). At that point, rebuilding kdelibs would of course solve the problem, since it would then have been rebuilt against the i586 Qt - no more mismatch. Changing kdelibs' 686 references would not have made a difference. Bug #253975 gives some idea of what the string in question is - it seems to represent the Qt ABI. In kdewidgets, therefore, seems to be recorded the Qt ABI against which kdelibs was built. Anyway, please let us know what happened. I don't think this is a bug in a KDE package, but this issue is probably worth following up nevertheless (it might reflect an issue with how Qt is built). Thanks, Christopher Martin
Attachment:
pgpxdrEpK2Blw.pgp
Description: PGP signature