It looks like my problem is about understanding what the files provided by multistrap are all about.
On Sat, Jun 11, 2011 at 07:45:51PM +0100, Neil Williams wrote: > > |setupscript=/usr/share/multistrap/setcrossarch.sh > > That is a cross-building script, intended to help set the > cross-building architecture in a native chroot which will then be used > to cross-build packages for that arch. OK. Then a note about its purpose would be welcome, say at the beginning of the script. "meant to be called from multistrap with directory arch variables" does not really help in ths respect. > It is not multistrap's fault if you provide a setupscript which does > the wrong thing - it can be used by multistrap when the objective is > to build a cross-building chroot and there it works fine. Indeed, my goal being to build an armel device rootfs, I naively selected "armel.conf" as a starting point. Again, a note in this file to tell that it is indeed intended to build a cross-build env would be great - although it is sure that the contents could have helped me figure that out myself. Indeed, armel.conf includes crosschroot.conf, and the contents of that one should again have helped me. But maybe renaming it to something like "crossbuildchroot.conf" would be more accurate, and better guide the poor soul trying to make sense of all this late at night :) > The clue is: > > cfg="/etc/pdebuild-cross/pdebuild-cross.rc" > > It is provided to assist pdebuild-cross. So why isn't it shipped with pdebuild-cross instead ? > There are many use-cases for a root filesystem - one is to create a > native chroot, another is a native chroot containing a cross-compiler > to build packages for a foreign architecture in a contained manner and > a third is to create a root filesystem of native or foreign packages > which can then be used to build a device using packages built in a > chroot. Multistap can do all of these permutations but you've > misunderstood the purpose of one of the scripts provided to support > cross-building and used it for no good purpose and for no useful effect > in a situation where what you want is a root filesystem, not a > cross-building chroot. Right. It looks like my problem was just that I expected a conf file suitable for the third case, and having selected a wrong one I did not adapt it correctly. In fact, it looks like there is no conf file shipped for this case, or did I just miss it ? Anyway, improving the naming of those files would help users to quickly and acurately select the one they need. > The reference to pdebuild-cross really should have been enough of a > clue. ... except that I am not trying to build a cross-build chroot :) Best regards, -- Yann -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
