UNSUBSCRIBE

UNSUBSCRIBE UNSUBSCRIBE UNSUBSCRIBE

JANE ! ! !

JANE ! ! !

STOP THIS CRAZY THING ! ! !

JAAAAAANNNNNNEEEEE!!!!!!!!!

-----Original Message-----
From: angstrom-distro-devel-boun...@linuxtogo.org
[mailto:angstrom-distro-devel-boun...@linuxtogo.org] On Behalf Of
angstrom-distro-devel-requ...@linuxtogo.org
Sent: Sunday, March 04, 2012 9:35 AM
To: angstrom-distro-devel@linuxtogo.org
Subject: Angstrom-distro-devel Digest, Vol 66, Issue 7

Send Angstrom-distro-devel mailing list submissions to
        angstrom-distro-devel@linuxtogo.org

To subscribe or unsubscribe via the World Wide Web, visit
        
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

or, via email, send a message with subject or body 'help' to
        angstrom-distro-devel-requ...@linuxtogo.org

You can reach the person managing the list at
        angstrom-distro-devel-ow...@linuxtogo.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Angstrom-distro-devel digest..."


Today's Topics:

   1. Re: Can't build cloud9 image (Gary Thomas)
   2. Re: Can't build cloud9 image (Koen Kooi)
   3. Images are all broken (Gary Thomas)
   4. Re: Can't build cloud9 image (Gary Thomas)
   5. Re: Can't build cloud9 image (Koen Kooi)
   6. Extraneous package config file (.pc) breaking     build sanity
      test (Alex J Lennon)
   7. Re: Extraneous package config file (.pc) breaking build
      sanity test (Koen Kooi)


----------------------------------------------------------------------

Message: 1
Date: Sun, 04 Mar 2012 05:42:54 -0700
From: Gary Thomas <g...@mlbassoc.com>
Subject: Re: [Angstrom-devel] Can't build cloud9 image
To: Discussion of the angstrom distribution development
        <angstrom-distro-devel@linuxtogo.org>
Message-ID: <4f53634e.3030...@mlbassoc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

On 2012-03-03 05:51, Gary Thomas wrote:
> 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-angstro
m-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?
>
> Thanks
>

Interesting note: the image actually gets created, this error must
be happening in some post-processing, perhaps the build history?

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------



------------------------------

Message: 2
Date: Sun, 4 Mar 2012 13:46:27 +0100
From: Koen Kooi <k...@dominion.thruhere.net>
Subject: Re: [Angstrom-devel] Can't build cloud9 image
To: Discussion of the angstrom distribution development
        <angstrom-distro-devel@linuxtogo.org>
Message-ID:
        <89b59491-7bdb-4a5d-bdc0-d4e3863e4...@dominion.thruhere.net>
Content-Type: text/plain; charset=us-ascii


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-angstro
m-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.





------------------------------

Message: 3
Date: Sun, 04 Mar 2012 05:48:52 -0700
From: Gary Thomas <g...@mlbassoc.com>
Subject: [Angstrom-devel] Images are all broken
To: Discussion of the angstrom distribution development
        <angstrom-distro-devel@linuxtogo.org>
Message-ID: <4f5364b4.3030...@mlbassoc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

All of the recent images I've built (for beaglebone at least)
fail on boot with these messages:

  Starting Journal Service...
   Failed to start Journal Service
[FAILED]
   See 'systemctl status systemd-journald.service' for details.
   Dependency failed. Aborted start of Getty on tty1                      [
ABORT]
   Dependency failed. Aborted start of Serial Getty on ttyO0              [
ABORT]

Since this is a very early-on failure, nothing runs and I can't get in
to run the status command to figure out what's wrong.  Perhaps there is
some way to get more verbose output to the console?  I could edit some
config file, etc, offline an try another boot.

This build was for systemd-image, from a 100% scratch setup,
as of 2012-03-02 1500 GMT

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"

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------



------------------------------

Message: 4
Date: Sun, 04 Mar 2012 06:02:37 -0700
From: Gary Thomas <g...@mlbassoc.com>
Subject: Re: [Angstrom-devel] Can't build cloud9 image
To: angstrom-distro-devel@linuxtogo.org
Message-ID: <4f5367ed.1060...@mlbassoc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

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-angstro
m-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?  Everything else builds with no special "root" style
privileges, why does this one image need it?  Also, what if I build
in another tree/path?  Now, I have to edit /etc/fstab again?

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------



------------------------------

Message: 5
Date: Sun, 4 Mar 2012 14:09:30 +0100
From: Koen Kooi <k...@dominion.thruhere.net>
Subject: Re: [Angstrom-devel] Can't build cloud9 image
To: Discussion of the angstrom distribution development
        <angstrom-distro-devel@linuxtogo.org>
Cc: meta...@yoctoproject.org
Message-ID:
        <7ab88097-7498-4bee-879a-d24894a4c...@dominion.thruhere.net>
Content-Type: text/plain; charset=us-ascii


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-angstro
m-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.


------------------------------

Message: 6
Date: Sun, 04 Mar 2012 13:42:14 +0000
From: Alex J Lennon <ajlen...@dynamicdevices.co.uk>
Subject: [Angstrom-devel] Extraneous package config file (.pc)
        breaking        build sanity test
To: Discussion of the angstrom distribution development
        <angstrom-distro-devel@linuxtogo.org>
Message-ID: <4f537136.8080...@dynamicdevices.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Hi,

I've been trying to add in a recipe for libgdiplus.so as I need it for 
some Mono/SDLDotNet rendering I'm looking at.

The recipe builds the package (inheriting autotools) but seems to leave 
a package configuration hanging around which then breaks a sanity check -

ERROR: QA Issue with staging: libgdiplus.pc failed sanity test (tmpdir) 
in path 
/data_drive/openembedded/build/tmp-angstrom_2008_1/sysroots/armv5te-angstrom
-linux-gnueabi/usr/lib/pkgconfig

Can anybody point me to an example recipe showing what I need to do to 
clean this up correctly?

Thanks,

Alex




------------------------------

Message: 7
Date: Sun, 4 Mar 2012 15:26:31 +0100
From: Koen Kooi <k...@dominion.thruhere.net>
Subject: Re: [Angstrom-devel] Extraneous package config file (.pc)
        breaking        build sanity test
To: Discussion of the angstrom distribution development
        <angstrom-distro-devel@linuxtogo.org>
Message-ID:
        <9bed6b0b-c0d6-4f0e-90a4-b3f667ebd...@dominion.thruhere.net>
Content-Type: text/plain; charset=us-ascii


Op 4 mrt. 2012, om 14:42 heeft Alex J Lennon het volgende geschreven:

> Hi,
> 
> I've been trying to add in a recipe for libgdiplus.so as I need it for
some Mono/SDLDotNet rendering I'm looking at.
> 
> The recipe builds the package (inheriting autotools) but seems to leave a
package configuration hanging around which then breaks a sanity check -
> 
> ERROR: QA Issue with staging: libgdiplus.pc failed sanity test (tmpdir) in
path
/data_drive/openembedded/build/tmp-angstrom_2008_1/sysroots/armv5te-angstrom
-linux-gnueabi/usr/lib/pkgconfig
> 
> Can anybody point me to an example recipe showing what I need to do to
clean this up correctly?

Have a look at the meta-mono layer:
https://github.com/KokoFitClub/meta-mono/tree/master/recipes-mono/libgdiplus

regards,

Koen


------------------------------

_______________________________________________
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel


End of Angstrom-distro-devel Digest, Vol 66, Issue 7
****************************************************



_______________________________________________
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Reply via email to