Hi, On Sunday 13 May 2007 05:37:44 samwyse wrote:
> Anyone seen this before? This was pretty early in the build process. Yes. > I'm trying to build a custom system and I suppose I could have > elimated a dependency, but I thought I had just eliminated X11, etc. > > == 22:52:39 =[1]=> Building base/mkpkg [2003-09-09 6.0.3]. > -> Reading package configuration from package directory. > -> Preparing build in src.mkpkg.system.20070509.225238.16323.localhost > -> Building. Writing output to $root/var/adm/logs/1-mkpkg.out > -> $root/var/adm/logs/1-mkpkg.out -> 1-mkpkg.log > == 05/09/07 22:52:48 =[1]=> Finished building package mkpkg. > > Creating binary package file for mkpkg. > -> Building build/.../pkgs/mkpkg-2003-09-09.tar.bz2 > chroot: cannot run command `bin/bash': No such file or directory > -> Unmounting loop mounts ... This usually happens when you build binaries for a CPU that your current system can not run. That is if you build ARM on a x86 CPU or for x86-64 even when you currently run a 32bit kernel on a AMD64 CPU. It could also indicate that the resulting binaries do not work, e.g. due bugs in the dynamic linker or c library. Or you just optimized bash away in your package selection :-) Native builds require bash as the build scripts are executed in the chroot environment. Yours, -- René Rebe - ExactCODE GmbH - Europe, Germany, Berlin http://exactcode.de | http://t2-project.org | http://rene.rebe.name
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe t2
