On Friday 12 March 2010 08:25:35 Wookey wrote:
> +++ Charles Manning [2010-03-11 15:07 +1300]:
> > I got r 839 built fine.
> >
> > I updated to 1014 and the build failed the same as when SUBDIRS was set
> > to both emdebian and debian.
> >
> > 1014 only tries SUBDIR = emdebian and the build fails as below.
> >
> > Any hints?
> >
> > Multistrap system installed successfully
> > in ../../../build/rootfs/emdebian/emdebian-grip-rootfs/.
> >
> > # the real sources are in /etc/apt/sources.list.d/
> > rm -f
> > ../../../build/rootfs/emdebian/emdebian-grip-rootfs/etc/apt/sources.list
> > touch multistrap-stamp
> > #fix up rootfs enough to boot it and do dpkg --configure -a
> > ROOTFS_CONFIG='rootfs-config'
> > FILES='files'
> > + '[' '' = ../../../build/rootfs/emdebian/emdebian-grip-rootfs ']'
> > + '[' -e ../../../build/rootfs/emdebian/emdebian-grip-rootfs ']'
> > + ROOTFS=../../../build/rootfs/emdebian/emdebian-grip-rootfs
> > + '[' / = ROOTFS ']'
> > + '[' '' = files ']'
> > + '[' -d files ']'
> > + CONFIG=files
> > + '[' -e config ']'
> > + . config
> > ./rootfs-config: line 37: .: config: file not found
> > make[2]: *** [../../../build/rootfs/emdebianrootstrap.tgz] Error 1
> > make[2]: Leaving directory `/opt/balloon/trunk/rootfs/emdebian'
> > make[1]: *** [all] Error 1
> > make[1]: Leaving directory `/opt/balloon/trunk/rootfs'
> > make: *** [all] Error 1
>
> Hmm. I'm not getting this problem on my builds because the bit before
> fails:
> + /dev/MAKEDEV -v std
> create mem c 1 1 root:kmem 0640
> mknod: mem-': Operation not permitted
>
> which isn't fatal, but does mean it never does the above so my build
> completes, but not with any device files in the rootfs.
>
> The above failure is odd. presumably you do have a file called
> "config" in your trunk/rootfs/emdebian/ dir?
charles@qcore:/opt/balloon/trunk$ ls -ial rootfs/emdebian/
total 68
24626 drwxr-xr-x 8 charles charles 4096 2010-03-11 12:51 .
24625 drwxr-xr-x 6 charles charles 4096 2010-03-11 13:44 ..
16822 -rw-r--r-- 1 charles charles 34 2010-02-05 14:50 config
24644 drwxr-xr-x 3 charles charles 4096 2010-03-11 12:24 files
213263 drwxr-xr-x 3 charles charles 4096 2010-03-11 12:24 files-CUED
24653 drwxr-xr-x 3 charles charles 4096 2010-03-11 12:24 files-podpoint
24627 drwxr-xr-x 3 charles charles 4096 2010-03-11 12:24 files-tcl-sl40
32781 drwxr-xr-x 4 charles charles 4096 2010-02-05 14:46 machine
16800 -rw-r--r-- 1 charles charles 2919 2010-03-11 12:24 Makefile
16825 -rw-r--r-- 1 charles charles 1334 2010-03-11 12:24
multistrap-balloon.conf
16823 -rw-r--r-- 1 charles charles 1339 2010-03-11 12:24
multistrap-balloon-CUED.conf
16824 -rw-r--r-- 1 charles charles 1434 2010-03-11 12:24
multistrap-balloon-podpoint.conf
16829 -rw-r--r-- 1 charles charles 1568 2010-03-11 12:24
multistrap-balloon-tcl-sl40.conf
12439 -rw-r--r-- 1 charles charles 0 2010-03-11 14:30 multistrap-stamp
16835 -rwxr-xr-x 1 charles charles 3325 2010-03-11 12:24 rootfs-config
16828 -rwxr-xr-x 1 charles charles 3448 2010-03-11 12:24
rootfs-config-podpoint
16799 -rwxr-xr-x 1 charles charles 3355 2010-03-11 12:24
rootfs-config-tcl-sl40
24636 drwxr-xr-x 6 charles charles 4096 2010-03-11 14:56 .svn.
charles@qcore:/opt/balloon/trunk$ cat rootfs/emdebian/config
CONSOLE=ttyS2
CONSOLESPEED=115200
charles@qcore:/opt/balloon/trunk$
> try adding echo `pwd` to rootfs-config just before #read in settings
>
> alternatively nobble that file to set
> CONSOLE=ttyS2
> CONSOLESPEED=115200
> internally and skip reading "config" by way of a workaround.
>
> As mentioned previously, for nand experiments you don't want a debian
> or emdebian root anyway so setting
> ROOTFSTOBUILD=""
> in your top-level makefile.local (or Makefile.inc) will get you past
> this problem (and save quite a lot of time) until you actually need it
> and we work out what the problem is.
OK. I'll skip that for now though I expect I'll need to play with the rootfs
at some stage if I mod the nand partitioning etc.
>
> I've been having fun and games with different version of multistrap
> and fakeroot which cause all this stuff that used to work nicely to go
> wrong, especially when wrapped in fakeroot. We fixed an obscure bug to
> day to do with relative paths. Actually I think I simply want to use
> realpath and get rid of all the relative paths as they tend to cause
> breakage. But lets get you going first, as that could be an invasive
> change.
>
> Which version of fakeroot do you have installed? fakeroot or
> fakeroot-ng?
fakeroot version 1.12.4
>
>
> Wookey