Most of the mumble-devel packages contain a library configuration file called something mumble-config, which is installed as /usr/bin/mumble- config. This makes it impossible to install mumble-devel for both the 64-bit library and the 32-bit library on AMD x86_64 systems. Which, in turn, makes it impossible to develop many 32-bit applications on these systems. This bit me while trying to build a 32-bit version of mplayer, which is needed to access most of the publicly available codecs, which would have been easy otherwise -- just 'export CC="cc -m32"' before running configure. How hard would it be to separate these configuration files by placing them in (say) /usr/bin32 and /usr/bin64, to be used only for packages with the same name that produce different results depending on the desired architecture, or in /usr/lib and /usr/lib64, or /usr/lib/bin and /usr/lib64/bin, or whatever? At any rate, I wish something like this could be in FC4 for the AMD x86_64 processors. -- Jonathan Ryshpan <jonrysh@xxxxxxxxxxx> Berkeley Linux Team
