[meta-ti] [Angstrom-devel] Can't build cloud9 image
Koen Kooi
koen at dominion.thruhere.net
Sun Mar 4 05:09:30 PST 2012
Op 4 mrt. 2012, om 14:02 heeft Gary Thomas het volgende geschreven:
> On 2012-03-04 05:46, Koen Kooi wrote:
>>
>> Op 3 mrt. 2012, om 13:51 heeft Gary Thomas het volgende geschreven:
>>
>>> OE Build Configuration:
>>> BB_VERSION = "1.15.1"
>>> TARGET_ARCH = "arm"
>>> TARGET_OS = "linux-gnueabi"
>>> MACHINE = "beaglebone"
>>> DISTRO = "angstrom"
>>> DISTRO_VERSION = "v2012.03-core"
>>> TUNE_FEATURES = "armv7a vfp neon cortexa8"
>>> TARGET_FPU = "vfp-neon"
>>> meta-angstrom = "master:2129eed920364abcc4f3f72d395333a041634e26"
>>> meta-oe
>>> meta-efl
>>> meta-gpe
>>> meta-gnome
>>> meta-xfce
>>> meta-initramfs = "master:fdff8697ea2db6254d26510adb7d11e6352d950f"
>>> meta-opie = "master:efa3892b20a4ef80274e56e5633ebd62c16f9731"
>>> meta-java = "master:d430de31c167cd264be74a1d82af4b732bb915dd"
>>> meta-mozilla = "master:5737d9fa26a632a27b2aa760c0d01190f0a17d0e"
>>> meta-ti = "master:020b6f893d13e36bccd7a2d8e6a0e6ab5e602450"
>>> meta-efikamx = "master:2c09a3a780b23448e8a6ca964256ff7f5ccba65d"
>>> meta-nslu2 = "master:3d9fc951b05b4df476374b6fc3085ebac7f293ee"
>>> meta-htc
>>> meta-nokia
>>> meta-openmoko
>>> meta-palm = "master:cda19686a2a3573ce50c86733c3469d926124995"
>>> meta-handheld = "master:fa1e6dcb524eb7ed29a6cd971a150d35c31e96e7"
>>> meta-intel
>>> meta-sugarbay
>>> meta-crownbay
>>> meta-emenlow
>>> meta-fishriver
>>> meta-jasperforest
>>> meta-n450 = "master:df18b721f86f0737c0f302e49b27ea232c70e683"
>>> meta = "master:b24d4bcde21b013e48eaffea5f3a70d8b1df1047"
>>>
>>> Building of cloud9-image ends up with this error:
>>> /etc/fstab entries need to be created with the user flag for the loop devices like:
>>> /dev/loop2 /local/new-angstrom/build/tmp-angstrom_2010_x-eglibc/work/beaglebone-angstrom-linux-gnueabi/cloud9-image-1.0-r0/tmp-mnt-boot vfat user 0 0
>>>
>>> My host is Fedora-16 (i386)
>>>
>>> How do I solve this so I can build the full cloud9-image?
>>
>> At the risk of responding to a practical joke: /etc/fstab entries need to be created with the user flag for the loop devices, the error message even includes the exact entry you need to add.
>
> I see that, but what if I'm "Joe user" who can't (or doesn't want to)
> edit /etc/fstab?
Then you can't build this image.
> Everything else builds with no special "root" style
> privileges, why does this one image need it?
Simply put: because the tools suck. A this point in time there is no tool (or tools plural) that allows creating 2 partitions (vfat and extX) and concatenating them into a valid image with an MBR. The biggest lack is something like 'genfatfs', mcopy is a step in the right direction but is too limited to work in this scenario.
And genext2fs will likely OOM on a lot of buildmachines.
> Also, what if I build
> in another tree/path? Now, I have to edit /etc/fstab again?
Correct, it's the gift that keeps on giving :(
Anyway, why are you posting this to the angstrom list? The cloud9 recipe and offending bbclass live in meta-ti.
More information about the meta-ti
mailing list