On 2007-09-23, Sune Vuorela <[EMAIL PROTECTED]> wrote: > The "buildkey" string is encoded in qconfig.h: > $ grep -i QT_BUI /usr/include/qt3/qconfig.h > #define QT_BUILD_KEY "i686 Linux g++-4.* full-config" where it is > generated by "uname -m" "uname -s" "compilerversion" "config options"
And it is not only limited to a few archs to look weird: alpha/usr/include/qt3/qconfig.h:#define QT_BUILD_KEY "alpha Linux g++-4.* full-config" amd64/usr/include/qt3/qconfig.h:#define QT_BUILD_KEY "x86_64 Linux g++-4.* full-config" arm/usr/include/qt3/qconfig.h:#define QT_BUILD_KEY "armv4l Linux g++-4.* full-config" hppa/usr/include/qt3/qconfig.h:#define QT_BUILD_KEY "parisc64 Linux g++-4.* full-config" i386/usr/include/qt3/qconfig.h:#define QT_BUILD_KEY "i686 Linux g++-4.* full-config" ia64/usr/include/qt3/qconfig.h:#define QT_BUILD_KEY "ia64 Linux g++-4.* full-config" mips/usr/include/qt3/qconfig.h:#define QT_BUILD_KEY "mips Linux g++-4.* full-config" mipsel/usr/include/qt3/qconfig.h:#define QT_BUILD_KEY "mips Linux g++-4.* full-config" powerpc/usr/include/qt3/qconfig.h:#define QT_BUILD_KEY "ppc Linux g++-4.* full-config" s390/usr/include/qt3/qconfig.h:#define QT_BUILD_KEY "s390x Linux g++-4.* full-config" sparc/usr/include/qt3/qconfig.h:#define QT_BUILD_KEY "sparc Linux g++-4.* full-config" I wonder now wether the best solution is to try in qt to relax/remove the check - or wether to kick in a transition (and how) - or doing a lot of dpkg-architecture - followed by mappings between current values (as shown above) and dpkg-arch values. or just to make Bastian Blank build s390 as s390 instead of s390x and forget the rest. /Sune -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
