On 8/15/07, Rodrigo Vivi <[EMAIL PROTECTED]> wrote: > Hi there, > first of all forget that sb2_libtool compile error... It was related > to codesourcery toolchain. Using another toolchain I could compile > that.
I'll have to give that codesourcery toolchain a try one of these days myself and try to see what's going on. > But when I tried to run using sb2 I got this strange behavior: > # > bash-3.2$ sb2 apt-get -f install > Reading package lists... Done > Building dependency tree... Done > Correcting dependencies... Done > The following packages will be REMOVED: > update-alternatives-dpkg > 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. > Need to get 0B of archives. > After unpacking 0B of additional disk space will be used. > Do you want to continue [Y/n]? > > I took a look at sb2_mapping.log file (that is attached) but I > couldn't verify anything strange. > > Does anybody have an idea about it? It's possible that sb2 is mixing your target and host dpkg or apt config files from /etc, resulting in what you see. Or then the host apt/dpkg is not really fond of the target config files/architecture/something. The idea is to use the emulation mode for this kind of operation, sb2 -e apt-get -f install, could you try that? The default mapping mode is not really suited for installing packages, emulation is much better. Installation requires that essentially all paths are mapped to the buildroot, which is completely opposite of what sb2 tries to do, emulation mode differs in that it tries to give you as pure virtual chroot into buildroot as practical, only /dev, /proc, /sys, /tmp and qemu itself are taken from the host. /lauri _______________________________________________ Scratchbox-devel mailing list [email protected] http://lists.scratchbox.org/cgi-bin/mailman/listinfo/scratchbox-devel
