On Wed, 23 Mar 2011 15:37:34 +0100 Marcin Juszkiewicz marcin.juszkiewicz@linaro.org wrote:
Ubuntu 'natty' switched to multiarch recently and my cross toolchain packages started to fail to build. Most of problems were fixed but then dpkg-cross hit us.
Today I looked at dpkg-cross and made attached patch to handle problem. What patch does is converting multiarch packages into old style ones.
Are you sure you want to convert Multi-Arch paths to the old paths? The idea is to get the packages concerned to use Multi-Arch paths which the toolchain should just find without needing dpkg-cross at all. The toolchain should be looking in the Multi-Arch paths first, then the old cross paths.
The expected role for dpkg-cross once Multi-Arch started to be deployed was only in putting non-Multi-Arch packages into old paths, letting the toolchain find the other packages in their normal Multi-Arch paths.
There is no extra switch like "--force-even-when-multiarch" and "--convert-anyway -A" is used instead. This is change against latest CVS code (dpkg-cross r1.83).
From my tests it looks like it does proper job.
It sounds like the wrong job to me. Why are the libraries IN the correct Multi-Arch paths not being found by a Multi-Arch aware toolchain? You need a Multi-Arch-Cross toolchain to work with Multi-Arch and not changes to dpkg-cross. Old toolchains need to be upgraded.
If correctly Multi-Arch'd packages are not being found by a Multi-Arch aware toolchain, that's not something dpkg-cross should be expected to solve.