Hello,
System-Info:
Scratchbox-Version: Scratchbox Apophis r3
Host-System: SuSE 10.0
Compiler: "selfmade" toolchain with "gcc-2.95.3-glibc-2.1.3" for a SA110
I'm using sb for a few weeks now and all works fine. Thanks to the guys
who wrote that funny tool. No more patching of configure scripts or
hourless writing of proprietary makefiles.
How it is done:
to generate an updated version of a distribution I am using a predecessor of
the distribution root file system from a Jffs2-Image.
This is done by mounting the image to the target's device node "mtdblock0",
at the directory, let's call it "FLASH/". Then a TGZ-File (Flash.tgz) is
made from "FLASH/". All the above steps are done with sudo-commands (I've
written a devkit for it).
Now, as the scratchbox user, the "Flash.tgz"-File is untarred to a directory
"TMP/". This is done to give the scratchbox-user access rights to the
files of the image.
The files which have to be updated are installed to a directory "ROOTFS/"
during the build process.
The files of "ROOTFS/" are merged to the directory "TMP/" via rsync.
Now the updated version of the distribution resides under "TMP/".
To get an image of the new distribution I simply do a "mkfs.jffs2" (also
part of my devkit).
My problem (of understanding?):
first, according to the documentation of fakeroot, fakeroot should not be
used for the whole build process, because it is confused by
"configure"-calls. So far, so good. Nevertheless I've tried it, sometimes it
seems to work, sometimes not.
Therefore I decided to use fakeroot only for the copying and install steps
during the build process with the "-i" and "-s" options.
For example, I use it at the "scratchbox user untar-step" ("fakeroot -u -i
fr.dta -s fr.dta tar xvzf Flash.tgz"), etc.
The results are interesting, but unpredictable. I've tried a lot, but file
owners and groups never match the intended results. As a test example I'm
using the file "/etc/shadow" from the base image that should be
"root.shadow" in the resulting image.
What is interesting, the file "fr.dta" has always a size of 0 bytes.
I'm using fakeroot always according the prerequisite "what's going out of a
directory has always to go into the directory with fakeroot". This includes
delete operations etc.
I've played around with fakeroot on the host outside scratchbox. It works as
intended.
I've not managed it to get a log of what fakeroot is doing. I think the
problem is the 0 bytes file.
Has anyone an idea, how to get closer to the problem?
Thanks in advance,
Siegfried
_______________________________________________
Scratchbox-users mailing list
Scratchbox-users@lists.scratchbox.org
http://lists.scratchbox.org/cgi-bin/mailman/listinfo/scratchbox-users
