Re: [Angstrom-devel] [meta-angstrom][PATCH 1/2] angstrom-core-tweaks.inc: actually use fs-perms-angstrom.txt

[Stefan Agner]

On 2016-07-18 12:45, Max Krummenacher wrote:
> FILESYSTEM_PERMS_TABLES must be set with the relative path from one of the
> BBPATH paths.
> 
> Without this patch the setting of FILESYSTEM_PERMS_TABLES disables the use
> of openembedded-core/meta/files/fs-perms.txt but, as the file in
> meta-angstrom/files/fs-perms-angstrom.txt is not found, that file is not
> used for the fixup-perms task.
> 
> With fs-perms-angstrom.txt active files deployed from copydebugsources no
> longer trigger these warnings:
> | WARNING: helloworld-1.0-r0 do_package_qa: QA Issue: helloworld: 
> .../src/main.c
> | is owned by uid 1000, which is the same as the user running bitbake. This 
> may
> | be due to host contamination [host-user-contaminated]
> 
> Signed-off-by: Max Krummenacher 
> ---
>  conf/distro/include/angstrom-core-tweaks.inc | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/conf/distro/include/angstrom-core-tweaks.inc
> b/conf/distro/include/angstrom-core-tweaks.inc
> index 33aaaef..1a3af9d 100644
> --- a/conf/distro/include/angstrom-core-tweaks.inc
> +++ b/conf/distro/include/angstrom-core-tweaks.inc
> @@ -62,7 +62,7 @@ PACKAGE_CLASSES = "package_ipk"
>  # Image.bbclass stuff:
>  
>  # Override default fs-perms.txt that messes with our /var setup:
> -FILESYSTEM_PERMS_TABLES = "fs-perms-angstrom.txt"
> +FILESYSTEM_PERMS_TABLES = "files/fs-perms-angstrom.txt"
>   
>  #
>  # udev, devfsd, busybox-mdev (from busybox) or none

What is the state of this patch? It seems to me that the missing files/
sub directory is really a bug which should be fixed.

--
Stefan

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

Re: [Angstrom-devel] [meta-angstrom 1/2] images: consolidate development packages in development-image

[Stefan Agner]

On 2016-06-28 23:17, Stefan Agner wrote:
> The images development-gnome-image and development-xfce-image share
> a large amount of pakages (mainly console utilities). Create a common
> base image "development-image" (which can be used standalone too).

Any comment on this patches? Haven't been merged so far...

--
Stefan

> 
> Signed-off-by: Stefan Agner <ste...@agner.ch>
> ---
>  recipes-images/angstrom/development-gnome-image.bb | 53 ++--
>  recipes-images/angstrom/development-image.bb   | 58 
> ++
>  recipes-images/angstrom/development-xfce-image.bb  | 55 ++--
>  3 files changed, 64 insertions(+), 102 deletions(-)
>  create mode 100644 recipes-images/angstrom/development-image.bb
> 
> diff --git a/recipes-images/angstrom/development-gnome-image.bb
> b/recipes-images/angstrom/development-gnome-image.bb
> index d198bf4..9518926 100644
> --- a/recipes-images/angstrom/development-gnome-image.bb
> +++ b/recipes-images/angstrom/development-gnome-image.bb
> @@ -1,16 +1,10 @@
> -# Image with a GNOME2 desktop and various tools installed
> +# Image with a XFCE desktop and various development tools installed
>  
> -CONMANPKGS = "connman connman-client connman-angstrom-settings
> connman-plugin-loopback connman-plugin-ethernet connman-plugin-wifi
> connman-gnome"
> -
> -require systemd-image.bb
> +require development-image.bb
>  
>  EXTRA_IMAGE_FEATURES += "splash"
> -ARCHTOOLS = ""
> -ARCHTOOLS_x86 = "dmidecode"
>  
>  IMAGE_INSTALL += " \
> - xinput-calibrator \
> - systemd-analyze \
>   packagegroup-gnome \
>   packagegroup-gnome-apps \
>   packagegroup-gnome-themes \
> @@ -18,48 +12,7 @@ IMAGE_INSTALL += " \
>   packagegroup-core-x11-xserver \
>   packagegroup-gnome-fonts \
>   \
> - packagegroup-sdk-target \
> - \
> - pciutils \
> - usbutils \
> - i2c-tools \
> - parse-edid \
> - memtester \
> - alsa-utils \
> - devmem2 \
> - iw \
> - bonnie++ \
> - hdparm \
> - iozone3 \
> - iperf \
> - lmbench \
> - rt-tests \
> - evtest \
> - bc \
> - fb-test \
> - tcpdump \
> - procps \
> - util-linux \
> - coreutils \
> - ethtool \
> - bridge-utils \
> - wget \
> - screen \
> - minicom \
> - rsync \
> - vim vim-vimrc \
> - ${ARCHTOOLS} \
> - \
> - git \
> - \
> - e2fsprogs-mke2fs \
> - dosfstools \
> - parted \
> - xfsprogs \
> - btrfs-tools \
> - \
> - python-core python-modules \
> + connman-gnome \
>  "
>  
>  export IMAGE_BASENAME = "development-GNOME-image"
> -
> diff --git a/recipes-images/angstrom/development-image.bb
> b/recipes-images/angstrom/development-image.bb
> new file mode 100644
> index 000..b5c971a
> --- /dev/null
> +++ b/recipes-images/angstrom/development-image.bb
> @@ -0,0 +1,58 @@
> +# Image with target SDK and various development tools installed
> +
> +CONMANPKGS = "connman connman-client connman-angstrom-settings
> connman-plugin-loopback connman-plugin-ethernet connman-plugin-wifi"
> +
> +require systemd-image.bb
> +
> +ARCHTOOLS = ""
> +ARCHTOOLS_x86 = "dmidecode"
> +
> +IMAGE_INSTALL += " \
> + packagegroup-sdk-target \
> + \
> + xinput-calibrator \
> + systemd-analyze \
> + \
> + bash \
> +pciutils \
> + usbutils \
> + i2c-tools \
> + parse-edid \
> + memtester \
> + alsa-utils \
> + devmem2 \
> + iw \
> + bonnie++ \
> + hdparm \
> + iozone3 \
> + iperf \
> + lmbench \
> + rt-tests \
> + evtest \
> + bc \
> + fb-test \
> + tcpdump \
> + procps \
> + util-linux \
> + coreutils \
> + ethtool \
> + bridge-utils \
> + wget \
> + screen \
> + minicom \
> + rsync \
> + vim vim-vimrc \
> + ${ARCHTOOLS} \
> + \
> + git \
> + \
> + e2fsprogs-mke2fs \
> + dosfstools \
> + parted \
> + xfsprogs \
> + btrfs-tools \
> + \
> + python-core python-modules \
> +"
> +
> +export IMAGE_BASENAME = "development-image"
> diff --git a/recipes-images/angstrom/development-xfce-image.bb
> b/recipes-images/angstrom/development-xfce-image.bb
> index 3b1e50a..42df038 100644
> --- a/recipes-images/angstrom/development-xfce-image.bb
> +++ b/recipes-images/angstrom/develo

[Angstrom-devel] [meta-angstrom 1/2] images: consolidate development packages in development-image

[Stefan Agner]

The images development-gnome-image and development-xfce-image share
a large amount of pakages (mainly console utilities). Create a common
base image "development-image" (which can be used standalone too).

Signed-off-by: Stefan Agner <ste...@agner.ch>
---
 recipes-images/angstrom/development-gnome-image.bb | 53 ++--
 recipes-images/angstrom/development-image.bb   | 58 ++
 recipes-images/angstrom/development-xfce-image.bb  | 55 ++--
 3 files changed, 64 insertions(+), 102 deletions(-)
 create mode 100644 recipes-images/angstrom/development-image.bb

diff --git a/recipes-images/angstrom/development-gnome-image.bb 
b/recipes-images/angstrom/development-gnome-image.bb
index d198bf4..9518926 100644
--- a/recipes-images/angstrom/development-gnome-image.bb
+++ b/recipes-images/angstrom/development-gnome-image.bb
@@ -1,16 +1,10 @@
-# Image with a GNOME2 desktop and various tools installed
+# Image with a XFCE desktop and various development tools installed
 
-CONMANPKGS = "connman connman-client connman-angstrom-settings 
connman-plugin-loopback connman-plugin-ethernet connman-plugin-wifi 
connman-gnome"
-
-require systemd-image.bb
+require development-image.bb
 
 EXTRA_IMAGE_FEATURES += "splash"
-ARCHTOOLS = ""
-ARCHTOOLS_x86 = "dmidecode"
 
 IMAGE_INSTALL += " \
-   xinput-calibrator \
-   systemd-analyze \
packagegroup-gnome \
packagegroup-gnome-apps \
packagegroup-gnome-themes \
@@ -18,48 +12,7 @@ IMAGE_INSTALL += " \
packagegroup-core-x11-xserver \
packagegroup-gnome-fonts \
\
-   packagegroup-sdk-target \
-   \
-   pciutils \
-   usbutils \
-   i2c-tools \
-   parse-edid \
-   memtester \
-   alsa-utils \
-   devmem2 \
-   iw \
-   bonnie++ \
-   hdparm \
-   iozone3 \
-   iperf \
-   lmbench \
-   rt-tests \
-   evtest \
-   bc \
-   fb-test \
-   tcpdump \
-   procps \
-   util-linux \
-   coreutils \
-   ethtool \
-   bridge-utils \
-   wget \
-   screen \
-   minicom \
-   rsync \
-   vim vim-vimrc \
-   ${ARCHTOOLS} \
-   \
-   git \
-   \
-   e2fsprogs-mke2fs \
-   dosfstools \
-   parted \
-   xfsprogs \
-   btrfs-tools \
-   \
-   python-core python-modules \
+   connman-gnome \
 "
 
 export IMAGE_BASENAME = "development-GNOME-image"
-
diff --git a/recipes-images/angstrom/development-image.bb 
b/recipes-images/angstrom/development-image.bb
new file mode 100644
index 000..b5c971a
--- /dev/null
+++ b/recipes-images/angstrom/development-image.bb
@@ -0,0 +1,58 @@
+# Image with target SDK and various development tools installed
+
+CONMANPKGS = "connman connman-client connman-angstrom-settings 
connman-plugin-loopback connman-plugin-ethernet connman-plugin-wifi"
+
+require systemd-image.bb
+
+ARCHTOOLS = ""
+ARCHTOOLS_x86 = "dmidecode"
+
+IMAGE_INSTALL += " \
+   packagegroup-sdk-target \
+   \
+   xinput-calibrator \
+   systemd-analyze \
+   \
+   bash \
+pciutils \
+   usbutils \
+   i2c-tools \
+   parse-edid \
+   memtester \
+   alsa-utils \
+   devmem2 \
+   iw \
+   bonnie++ \
+   hdparm \
+   iozone3 \
+   iperf \
+   lmbench \
+   rt-tests \
+   evtest \
+   bc \
+   fb-test \
+   tcpdump \
+   procps \
+   util-linux \
+   coreutils \
+   ethtool \
+   bridge-utils \
+   wget \
+   screen \
+   minicom \
+   rsync \
+   vim vim-vimrc \
+   ${ARCHTOOLS} \
+   \
+   git \
+   \
+   e2fsprogs-mke2fs \
+   dosfstools \
+   parted \
+   xfsprogs \
+   btrfs-tools \
+   \
+   python-core python-modules \
+"
+
+export IMAGE_BASENAME = "development-image"
diff --git a/recipes-images/angstrom/development-xfce-image.bb 
b/recipes-images/angstrom/development-xfce-image.bb
index 3b1e50a..42df038 100644
--- a/recipes-images/angstrom/development-xfce-image.bb
+++ b/recipes-images/angstrom/development-xfce-image.bb
@@ -1,16 +1,9 @@
-# Image with a GNOME2 desktop and various tools installed
+# Image with a GNOME2 desktop and various development tools installed
 
-CONMANPKGS = "connman connman-client connman-angstrom-settings 
connman-plugin-loopback connman-plugin-ethernet connman-plugin-wifi 
connman-gnome"
+require development-image.bb
 
-require systemd-image.bb
-
-ARCHTOOLS = ""
-ARCHTOOLS_x86 = "dmidecode"
 
 IMAGE_INSTALL += " \
-   xinput-calibrator \
-   systemd-analyze \
-   \
packagegroup-xfce-base \
packagegroup-gnome-xserver-base \
packagegroup-core-x11-xserver \
@@ -19,48 +12,7 @@ IMAGE_INSTALL += " \
\
angstrom-gd

[Angstrom-devel] [meta-angstrom 2/2] images: extend development images with useful utilties

[Stefan Agner]

Add additional development utilities to the development image.

Signed-off-by: Stefan Agner <ste...@agner.ch>
---
 recipes-images/angstrom/development-image.bb | 9 +
 1 file changed, 9 insertions(+)

diff --git a/recipes-images/angstrom/development-image.bb 
b/recipes-images/angstrom/development-image.bb
index b5c971a..ae59469 100644
--- a/recipes-images/angstrom/development-image.bb
+++ b/recipes-images/angstrom/development-image.bb
@@ -6,6 +6,7 @@ require systemd-image.bb
 
 ARCHTOOLS = ""
 ARCHTOOLS_x86 = "dmidecode"
+ARCHTOOLS_arm = "dtc"
 
 IMAGE_INSTALL += " \
packagegroup-sdk-target \
@@ -22,17 +23,25 @@ IMAGE_INSTALL += " \
alsa-utils \
devmem2 \
iw \
+   blktool \
bonnie++ \
hdparm \
iozone3 \
+   mmc-utils \
iperf \
+   iperf3 \
lmbench \
rt-tests \
evtest \
bc \
fb-test \
+   libdrm-tests \
tcpdump \
procps \
+   strace \
+   kexec \
+   perf \
+   qemu \
util-linux \
coreutils \
ethtool \
-- 
1.9.1


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

Re: [Angstrom-devel] Non existing -dev recommends

[Stefan Agner]

On 2016-04-20 12:53, Khem Raj wrote:
> On Wed, Apr 20, 2016 at 12:49 PM Stefan Agner <ste...@agner.ch> wrote:
> 
>> Hi,
>>
>> Using the  v2015.12 packages feeds -dev packages showed that there are
>> quite some nonexisting packages which are in the recommends list of
>> packages, leading to lot of messages, e.g.:
>> libxcb-dev: unsatisfied recommendation for libxcb-shape-dev
>> libxcb-dev: unsatisfied recommendation for libxcb-dpms-dev
>> libxcb-dev: unsatisfied recommendation for libxcb-render-dev
>> libxcb-dev: unsatisfied recommendation for libxcb-shm-dev
>> libxcb-dev: unsatisfied recommendation for libxcb-dri3-dev
>> libxcb-dev: unsatisfied recommendation for libxcb-damage-dev
>> libxcb-dev: unsatisfied recommendation for libxcb-glx-dev
>> libxcb-dev: unsatisfied recommendation for libxcb-composite-dev
>> libxcb-dev: unsatisfied recommendation for libxcb-res-dev
>> libxcb-dev: unsatisfied recommendation for libxcb-xvmc-dev
>> libxcb-dev: unsatisfied recommendation for libxcb-xkb-dev
>> libxcb-dev: unsatisfied recommendation for libxcb-sync-dev
>> libxcb-dev: unsatisfied recommendation for libxcb-xevie-dev
>> libxcb-dev: unsatisfied recommendation for libxcb-dri2-dev
>> libxcb-dev: unsatisfied recommendation for libxcb-randr-dev
>> libxcb-dev: unsatisfied recommendation for libxcb-record-dev
>> libxcb-dev: unsatisfied recommendation for libxcb-xprint-dev
>> libxcb-dev: unsatisfied recommendation for libxcb-xv-dev
>> libxcb-dev: unsatisfied recommendation for libxcb-xtest-dev
>> libxcb-dev: unsatisfied recommendation for libxcb-screensaver-dev
>> libxcb-dev: unsatisfied recommendation for libxcb-present-dev
>> libxcb-dev: unsatisfied recommendation for libxcb-xf86dri-dev
>> libxcb-dev: unsatisfied recommendation for libxcb-xinerama-dev
>> libxcb-dev: unsatisfied recommendation for libxcb-xfixes-dev
>> libx11-dev: unsatisfied recommendation for libx11-xcb-dev
>>
>> So libxcb-dev, has libxcb-shape-dev in its recommendation list, but
>> libxcb-shape-dev does not exist at all. I guess the reason for that is
>> libxcb-shape is built from the recipe libxcb with some package split
>> magic. Any idea how to get rid of those non-existing recommendations?
>>
>> Also, it seems to be a new behavior I don't remember seen this in
>> 2015.06 releases.
>>
> 
> I wonder if its due to the fact that all dev files are now bundled into
> single ipk.
> may be we are missng the RPROVIDES then ?

Hm, you mean the -dev package of the main package should contain a
provides for all -dev packges of the splitted packages?

The recipe at hand does not seem to provide such RPROVIDES:
http://cgit.openembedded.org/openembedded-core/tree/meta/recipes-graphics/xorg-lib/libxcb.inc?h=jethro

Note that it is not only libxcb, also perl-modules and other stuff have
such unresolved recommends...

--
Stefan

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

Re: [Angstrom-devel] [oe] license_create_manifest fails on jethro

[Stefan Agner]

Hi Alimon,

On 2016-03-11 09:00, Aníbal Limón wrote:
> Hi Stefan,
> 
> I tried to build angstrom v2015.12-yocto2.0 using qemux86-64 and
> systemd-image following [1] then the next errors appears:
> 
> ERROR: Nothing PROVIDES 'virtual/nativesdk-nativesdk-libx11' (but
> virtual:nativesdk:/home/alimon/repos/angstrom/sources/openembedded-core/meta/recipes-graphics/libsdl/libsdl_1.2.15.bb
> DEPENDS on or otherwise requires it). Close matches:
>   virtual/nativesdk-libx11
>   virtual/nativesdk-libc
>   virtual/nativesdk-db
> 
> ERROR: Required build target 'systemd-image' has no buildable providers.
> Missing or unbuildable dependency chain was: ['systemd-image',
> 'nativesdk-packagegroup-sdk-host', 'nativesdk-qemu', 'nativesdk-libsdl',
> 'virtual/nativesdk-nativesdk-libx11']

Not sure what is going on, also had this error here with Poky. This
helped for core-image-minimal:
DISTRO_FEATURES_remove = "x11"

To quickly reproduce this, I now setup just the Freescale BSP with Poky:
http://freescale.github.io/#download

Along with this config in conf/local.conf (which basically emulates the
Ångström config):
LICENSE_DIRECTORY = "${DEPLOY_DIR}/licenses/${MACHINE_ARCH}"

And enable copying licenses to the target directory:
COPY_LIC_MANIFEST = "1"
COPY_LIC_DIRS = "1"

Then I built this two images:

MACHINE=colibri-vf bitbake core-image-minimal
MACHINE=colibri-imx6 bitbake core-image-minimal

Note that for instance
tmp/deploy/licenses/colibri_vf/base-files/
exits after the first bitbake build, but the second bitbake build tries
to copy the license from
tmp/deploy/licenses/colibri_imx6/base-files/

--
Stefan

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

[Angstrom-devel] license_create_manifest fails on jethro

[Stefan Agner]

Hi Anibal,

I think the patch a7976cbae3 ("license_class: Reimplemented manifest
creation in python") broke Ångstroms way of deploying license files.
With jethro I get the following error when building the _second_
machine:

ERROR: Error executing a python function in
/build/ags/oe-core_V2.6/build/../stuff/meta-toradex/recipes/images/console-trdx-image.bb:

The stack trace of python calls that resulted in this exception/failure
was:
File: 'license_create_manifest', lineno: 110, function: 
 0106:
 0107:os.link(pkg_license,
pkg_rootfs_license)
 0108:
 0109:
 *** 0110:license_create_manifest(d)
 0111:
File: 'license_create_manifest', lineno: 86, function:
license_create_manifest
 0082:pkg_rootfs_license_dir =
os.path.join(rootfs_license_dir, pkg)
 0083:os.makedirs(pkg_rootfs_license_dir)
 0084:pkg_license_dir =
os.path.join(d.getVar('LICENSE_DIRECTORY', True),
 0085:   
pkg_dic[pkg]["PN"])
 *** 0086:licenses = os.listdir(pkg_license_dir)
 0087:for lic in licenses:
 0088:rootfs_license =
os.path.join(rootfs_license_dir, lic)
 0089:pkg_license =
os.path.join(pkg_license_dir, lic)
 0090:pkg_rootfs_license =
os.path.join(pkg_rootfs_license_dir, lic)
Exception: OSError: [Errno 2] No such file or directory:
'/build/ags/oe-core_V2.6/build/out-glibc/deploy/licenses/colibri_imx7/alsa-utils'

ERROR: Function failed: license_create_manifest
ERROR: Logfile of failure stored in:
/build/ags/oe-core_V2.6/build/out-glibc/work/colibri_imx7-angstrom-linux-gnueabi/console-trdx-image/V2.6-r0/temp/log.do_rootfs.29351
ERROR: Task 7
(/build/ags/oe-core_V2.6/build/../stuff/meta-toradex/recipes/images/console-trdx-image.bb,
do_rootfs) failed with exit code '1'

It might relate to how Ångström configures the LICENSE_DIRECTORY
variable (by including MACHINE_ARCH, see
https://github.com/Angstrom-distribution/meta-angstrom/blob/angstrom-v2015.12-yocto2.0/conf/distro/include/angstrom-core-tweaks.inc):
LICENSE_DIRECTORY = "${DEPLOY_DIR}/licenses/${MACHINE_ARCH}"

I am not sure what exactly causes the issue, but after reverting your
patch two consecutive builds of different machines succeeded...

However, I still get a lot of warnings such as:
WARNING: The license listed LGPLv2.1 was not in the licenses collected
for systemd

Any ideas?

--
Stefan

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

[Angstrom-devel] meta-angstrom minimal dependencies

[Stefan Agner]

Hi,

According to README, meta-angstrom should only depend on
openembedded-core. However, when building the jethero branch without
meta-qt5, I get this error:

ERROR: ParseError at
/build/ags/oe-core_V2.6/build/../stuff/meta-angstrom/recipes-images/angstrom/systemd-qt5-image.bb:5:
Could not inherit file classes/populate_sdk_qt5.bbclass

Is this issue known? Maybe Ångström should introduce a
meta-angstrom-images layer?

--
Stefan

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

Re: [Angstrom-devel] [RFC] angstrom-feed-configs: add non-thumb package arch

[Stefan Agner]

On 2016-01-28 00:51, Koen Kooi wrote:
>> Op 28 jan. 2016, om 09:43 heeft Stefan Agner <ste...@agner.ch> het volgende 
>> geschreven:
>>
>> On 2016-01-28 00:35, Koen Kooi wrote:
>>>> Op 27 jan. 2016, om 23:36 heeft Stefan Agner <ste...@agner.ch> het 
>>>> volgende geschreven:
>>>>
>>>> From: Stefan Agner <stefan.ag...@toradex.com>
>>>>
>>>> Several packages are only available in the non-thumb (ARM) feeds.
>>>> E.g. tremor (libvorbisdec1) uses ARM_INSTRUCTION_SET = "arm" in its
>>>> recipe, and therefor is built only for non-thumb architectures such
>>>> as armv7ahf-vfp-neon.
>>>
>>> That’s what I suspected, thanks for tracking this down.
>>>
>>>> This introduces TUNE_ARMPKGARCH which is TUNE_PKGARCH without the
>>>> thumb part (ARMPKGSFX_THUMB). FEED_ARCHS can contain multiple
>>>> architectures, and the feed configuration files are generated
>>>> accordingly.
>>>
>>> This is what distro-feed-configs.bb does as well and it leads to problems:
>>
>> Not exactly. The patch only adds one additional arch, the same arch as
>> TUNE_PKGARCH, just without the thumb…
> 
> Doh, I skipped over the angstrom.inc bits.
> 
>>
>>>
>>> 1) it adds all archs, including arch(N-1), arch(N-2), so it will also
>>> pick up armv6 in your case and other x86 archs in the x86_64 case. If
>>> for some reason you want a newer version of $package for arch(N-1),
>>> but not arch(N) this breaks.
>>> 2) not all archs have a feed dir, since a lot of them are
>>> autogenerated and to be honest, bogus. So users will get 404s.
>>
>> As soon as there is one package with ARM_INSTRUCTION_SET = "arm", the
>> non thumb arch will be there anyway. And libc is one of the packages
>> making use of that, so it is practically guaranteed...
>>
>>> 3) extra feed lists on the device which makes opkg slow.
>>
>> It seems that you are not building explicitly armv7ahf-vfp-neon platform
>> currently. Hence armv7ahf-vfp-neon and armv7at2hf-vfp-neon are
>> practically disjoint sets... Hence it's 2 smaller ones vs 1 large
>> package file...
>>
>>>
>>> Having said all that, how about this:
>>>
>>> diff --git a/contrib/sort.sh b/contrib/sort.sh
>>> index 8953e4c..12f1718 100755
>>> --- a/contrib/sort.sh
>>> +++ b/contrib/sort.sh
>>> @@ -118,6 +118,10 @@ case "$arch" in
>>>"armv7at2hf-vfp-neon-mx6")
>>>archdir="armv7ahf-vfp-neon"
>>>machines="" ;;
>>> +   "armv7ahf-vfp-neon")
>>> +   archdir="armv7at2hf-vfp-neon" ;;
>>> +   "armv7ahf-vfp")
>>> +   archdir="armv7at2hf-vfp" ;;
>>>"armv7ahfb-vfp-neon")
>>>machine="genericarmv7ab" ;;
>>>"armv7a-vfp")
>>> @@ -128,15 +132,16 @@ case "$arch" in
>>>archdir="blackfin"
>>>machines="adsp-bf537-stamp" ;;
>>>"cortexa5t2hf-vfp-neon")
>>> -   archdir="armv7ahf-vfp-neon"
>>> +   archdir="armv7at2hf-vfp-neon"
>>>machines="" ;;
>>>"cortexa5hf-vfp-neon")
>>> -   archdir="armv7ahf-vfp-neon"
>>> +   archdir="armv7at2hf-vfp-neon"
>>>machines="" ;;
>>>"cortexa9hf-vfp-neon")
>>> +   archdir="armv7at2hf-vfp-neon"
>>>machines="" ;;
>>>"cortexa9hf-vfp-neon-mx6")
>>> -   archdir="cortexa9hf-vfp-neon"
>>> +   archdir="armv7at2hf-vfp-neon"
>>>machine="" ;;
>>>"geode")
>>>machines="alix geodegx geodelx iei-nanogx-466 xo" ;;
>>>
>>> That will sort related bits into a single feed. And on the feedserver
>>> we symlink armv7at2hf-vfp-neon -> armv7ahf-vfp-neon and so on. In
>>> theory the sort.sh change should be enough, but it is possible to
>>> co

Re: [Angstrom-devel] [RFC] angstrom-feed-configs: add non-thumb package arch

[Stefan Agner]

On 2016-01-28 00:35, Koen Kooi wrote:
>> Op 27 jan. 2016, om 23:36 heeft Stefan Agner <ste...@agner.ch> het volgende 
>> geschreven:
>>
>> From: Stefan Agner <stefan.ag...@toradex.com>
>>
>> Several packages are only available in the non-thumb (ARM) feeds.
>> E.g. tremor (libvorbisdec1) uses ARM_INSTRUCTION_SET = "arm" in its
>> recipe, and therefor is built only for non-thumb architectures such
>> as armv7ahf-vfp-neon.
> 
> That’s what I suspected, thanks for tracking this down.
> 
>> This introduces TUNE_ARMPKGARCH which is TUNE_PKGARCH without the
>> thumb part (ARMPKGSFX_THUMB). FEED_ARCHS can contain multiple
>> architectures, and the feed configuration files are generated
>> accordingly.
> 
> This is what distro-feed-configs.bb does as well and it leads to problems:

Not exactly. The patch only adds one additional arch, the same arch as
TUNE_PKGARCH, just without the thumb...

> 
> 1) it adds all archs, including arch(N-1), arch(N-2), so it will also
> pick up armv6 in your case and other x86 archs in the x86_64 case. If
> for some reason you want a newer version of $package for arch(N-1),
> but not arch(N) this breaks.
> 2) not all archs have a feed dir, since a lot of them are
> autogenerated and to be honest, bogus. So users will get 404s.

As soon as there is one package with ARM_INSTRUCTION_SET = "arm", the
non thumb arch will be there anyway. And libc is one of the packages
making use of that, so it is practically guaranteed...

> 3) extra feed lists on the device which makes opkg slow.

It seems that you are not building explicitly armv7ahf-vfp-neon platform
currently. Hence armv7ahf-vfp-neon and armv7at2hf-vfp-neon are
practically disjoint sets... Hence it's 2 smaller ones vs 1 large
package file...

> 
> Having said all that, how about this:
> 
> diff --git a/contrib/sort.sh b/contrib/sort.sh
> index 8953e4c..12f1718 100755
> --- a/contrib/sort.sh
> +++ b/contrib/sort.sh
> @@ -118,6 +118,10 @@ case "$arch" in
> "armv7at2hf-vfp-neon-mx6")
> archdir="armv7ahf-vfp-neon"
> machines="" ;;
> +   "armv7ahf-vfp-neon")
> +   archdir="armv7at2hf-vfp-neon" ;;
> +   "armv7ahf-vfp")
> +   archdir="armv7at2hf-vfp" ;;
> "armv7ahfb-vfp-neon")
> machine="genericarmv7ab" ;;
> "armv7a-vfp")
> @@ -128,15 +132,16 @@ case "$arch" in
> archdir="blackfin"
> machines="adsp-bf537-stamp" ;;
> "cortexa5t2hf-vfp-neon")
> -   archdir="armv7ahf-vfp-neon"
> +   archdir="armv7at2hf-vfp-neon"
> machines="" ;;
> "cortexa5hf-vfp-neon")
> -   archdir="armv7ahf-vfp-neon"
> +   archdir="armv7at2hf-vfp-neon"
> machines="" ;;
> "cortexa9hf-vfp-neon")
> +   archdir="armv7at2hf-vfp-neon"
> machines="" ;;
> "cortexa9hf-vfp-neon-mx6")
> -   archdir="cortexa9hf-vfp-neon"
> +   archdir="armv7at2hf-vfp-neon"
> machine="" ;;
> "geode")
> machines="alix geodegx geodelx iei-nanogx-466 xo" ;;
> 
> That will sort related bits into a single feed. And on the feedserver
> we symlink armv7at2hf-vfp-neon -> armv7ahf-vfp-neon and so on. In
> theory the sort.sh change should be enough, but it is possible to
> construct a broken MACHINE.conf, so let’s be safe.

Hm, I see. The server side solution would also have the advantage that
it solves the issue for all the devices out there immediately.

It just feels a bit wrong to sort armv7ahf-vfp-neon into
armv7at2hf-vfp-neon.

--
Stefan


>> ---
>>
>> conf/distro/include/angstrom.inc   | 2 ++
>> recipes-angstrom/angstrom/angstrom-feed-configs.bb | 5 -
>> 2 files changed, 6 insertions(+), 1 deletion(-)
>>
>> diff --git a/conf/distro/include/angstrom.inc 
>> b/conf/distro/include/angstrom.inc
>> index c5f9fab..0b5ea25 100644
>> --- a/conf/distro/include/angstrom.inc
>> +++ b/conf/distro/include/angstrom.inc
>> @@ -21,6 +21,8 @@ ONLINE_PACKAGE_MANAGEMENT = "full"
>> #Alphabetically sorted
>>
>> FEED_ARCH ?= "${TU

[Angstrom-devel] [RFC] angstrom-feed-configs: add non-thumb package arch

[Stefan Agner]

From: Stefan Agner <stefan.ag...@toradex.com>

Several packages are only available in the non-thumb (ARM) feeds.
E.g. tremor (libvorbisdec1) uses ARM_INSTRUCTION_SET = "arm" in its
recipe, and therefor is built only for non-thumb architectures such
as armv7ahf-vfp-neon.

This introduces TUNE_ARMPKGARCH which is TUNE_PKGARCH without the
thumb part (ARMPKGSFX_THUMB). FEED_ARCHS can contain multiple
architectures, and the feed configuration files are generated
accordingly.
---

 conf/distro/include/angstrom.inc   | 2 ++
 recipes-angstrom/angstrom/angstrom-feed-configs.bb | 5 -
 2 files changed, 6 insertions(+), 1 deletion(-)

diff --git a/conf/distro/include/angstrom.inc b/conf/distro/include/angstrom.inc
index c5f9fab..0b5ea25 100644
--- a/conf/distro/include/angstrom.inc
+++ b/conf/distro/include/angstrom.inc
@@ -21,6 +21,8 @@ ONLINE_PACKAGE_MANAGEMENT = "full"
 #Alphabetically sorted
 
 FEED_ARCH ?= "${TUNE_PKGARCH}"
+TUNE_ARMPKGARCH = 
"${ARMPKGARCH}${ARMPKGSFX_DSP}${ARMPKGSFX_EABI}${ARMPKGSFX_ENDIAN}${ARMPKGSFX_FPU}"
+FEED_ARCHS ?= "${TUNE_PKGARCH} ${TUNE_ARMPKGARCH}"
 
 #blackfin machines
 FEED_ARCH_bfin  = "blackfin"
diff --git a/recipes-angstrom/angstrom/angstrom-feed-configs.bb 
b/recipes-angstrom/angstrom/angstrom-feed-configs.bb
index 4b14b2a..e40057a 100644
--- a/recipes-angstrom/angstrom/angstrom-feed-configs.bb
+++ b/recipes-angstrom/angstrom/angstrom-feed-configs.bb
@@ -13,7 +13,10 @@ do_compile() {
mkdir -p ${S}/${sysconfdir}/opkg
 
for feed in base debug perl python gstreamer ; do
- echo "src/gz ${feed} 
${ANGSTROM_URI}/${FEED_BASEPATH}${FEED_ARCH}/${feed}" > 
${S}/${sysconfdir}/opkg/${feed}-feed.conf
+   rm ${S}/${sysconfdir}/opkg/${feed}-feed.conf
+   for feed_arch in ${FEED_ARCHS} ; do
+   echo "src/gz ${feed}-${feed_arch} 
${ANGSTROM_URI}/${FEED_BASEPATH}${feed_arch}/${feed}" >> 
${S}/${sysconfdir}/opkg/${feed}-feed.conf
+   done
done
 
echo "src/gz ${MACHINE_ARCH} 
${ANGSTROM_URI}/${FEED_BASEPATH}${FEED_ARCH}/machine/${MACHINE_ARCH}" >  
${S}/${sysconfdir}/opkg/${MACHINE_ARCH}-feed.conf
-- 
1.9.3


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

[Angstrom-devel] [meta-angstrom][PATCH v2] README: add link to angstrom-manifest

[Stefan Agner]

Signed-off-by: Stefan Agner <ste...@agner.ch>
---
 README | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README b/README
index 5c369b0..c1f67f8 100644
--- a/README
+++ b/README
@@ -14,7 +14,7 @@ revision: HEAD
Setup
 ==
 
-It is recommended to follow the instruction at 
http://www.angstrom-distribution.org/building-angstrom
+It is recommended to follow the instruction at 
https://github.com/Angstrom-distribution/angstrom-manifest
 
 This will set it up for the OpenEmbedded-core layout needed for this layer 
instead of the old OpenEmbedded-dev layout.
 
-- 
2.6.4


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

[Angstrom-devel] [meta-angstrom] README: add link to angstrom-manifest

[Stefan Agner]

---
 README | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README b/README
index 5c369b0..c1f67f8 100644
--- a/README
+++ b/README
@@ -14,7 +14,7 @@ revision: HEAD
Setup
 ==
 
-It is recommended to follow the instruction at 
http://www.angstrom-distribution.org/building-angstrom
+It is recommended to follow the instruction at 
https://github.com/Angstrom-distribution/angstrom-manifest
 
 This will set it up for the OpenEmbedded-core layout needed for this layer 
instead of the old OpenEmbedded-dev layout.
 
-- 
2.6.4


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

Re: [Angstrom-devel] State of package feed for 2015.06

[Stefan Agner]

On 2015-10-26 10:29, Koen Kooi wrote:
>> Op 26 okt. 2015, om 18:21 heeft Stefan Agner <ste...@agner.ch> het volgende 
>> geschreven:
>>
>> On 2015-10-22 04:55, Koen Kooi wrote:
>>>> Op 20 okt. 2015, om 22:34 heeft Stefan Agner <ste...@agner.ch> het 
>>>> volgende geschreven:
>>>>
>>>> Hi,
>>>>
>>>> It seems that the feeds of version 2015.06 currently contains a lot less
>>>> packages than the 2014.12 feeds did.
>>>>
>>>> At least this is true for armv7at2hf-vfp/ and armv7at2hf-vfp-neon/. E.g.
>>>> the first package at the very top which is missing is a52dec, but there
>>>> is a lot of stuff like binutils or mono which are missing.
>>>>
>>>> Is this intentional? build-feeds.sh in meta-angstrom/contrib/ seems not
>>>> to be altered recently, so it should produce the same packages…?
>>>
>>> Great timing! The feeds are now being populated using Jenkins CI and
>>> there is a big rebuild for 2015.06 underway due to the big DISTRO
>>> changes that went in last week (i.e. blacklisting bluez5).
>>> Eyeballing the jenkins page there are 5 architectures left in the
>>> queue, good for 16h builds each spread over 2 machines, so I’d say
>>> “will finish this weekend”.
>>
>> It seems the packages are online now, thanks Koen!
>>
>> Was there any specific reason why those packages were not part of the
>> previous build for 2015.06?
> 
> Mostly lack of time to sit down and check a few architectures on real
> devices. I was also concerned about ABI changes and heisenbugs like
> the bluez5 blacklisting last week. The prserv support needs to get
> updated as well to keep feed updates consistent and working. The good
> news is that all the work going into v2015.06 wrt feed updates works
> for v2015.12 and next as well :)
> 
>> Just to understand your setup a bit better: Is your Jenkins using the
>> scripts under meta-angstrom/contrib/ or is that no longer the way the
>> packages get built?
> 
> For v2015.06 and newer it wraps around
> https://github.com/Angstrom-distribution/angstrom-manifest/ and does
> some magic for reusing sstate. I’ll paste the build step of the
> console-feed run at the bottom of this email. It’s not pretty, but it
> gets the job done.

Ok, and you call these script for each machine? So you basically build
all packages for all machines, and then upload just the packages which
are not up there yet..

I guess you do this to make sure that all the packages built by the
recipe list in the build step are available for _all_ the machines you
build... But with that, you probably rebuild armv7at2hf-vfp-neon several
times right? And the images are another build step?

Would you mind add colibri-vf to the list of machines? Since fido the
machine is in meta-fsl-arm-extra which is already part of your
bblayers.conf...

--
Stefan

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

Re: [Angstrom-devel] State of package feed for 2015.06

[Stefan Agner]

On 2015-10-22 04:55, Koen Kooi wrote:
>> Op 20 okt. 2015, om 22:34 heeft Stefan Agner <ste...@agner.ch> het volgende 
>> geschreven:
>>
>> Hi,
>>
>> It seems that the feeds of version 2015.06 currently contains a lot less
>> packages than the 2014.12 feeds did.
>>
>> At least this is true for armv7at2hf-vfp/ and armv7at2hf-vfp-neon/. E.g.
>> the first package at the very top which is missing is a52dec, but there
>> is a lot of stuff like binutils or mono which are missing.
>>
>> Is this intentional? build-feeds.sh in meta-angstrom/contrib/ seems not
>> to be altered recently, so it should produce the same packages…?
> 
> Great timing! The feeds are now being populated using Jenkins CI and
> there is a big rebuild for 2015.06 underway due to the big DISTRO
> changes that went in last week (i.e. blacklisting bluez5).
> Eyeballing the jenkins page there are 5 architectures left in the
> queue, good for 16h builds each spread over 2 machines, so I’d say
> “will finish this weekend”.

It seems the packages are online now, thanks Koen!

Was there any specific reason why those packages were not part of the
previous build for 2015.06?

Just to understand your setup a bit better: Is your Jenkins using the
scripts under meta-angstrom/contrib/ or is that no longer the way the
packages get built?

--
Stefan

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

[Angstrom-devel] State of package feed for 2015.06

[Stefan Agner]

Hi,

It seems that the feeds of version 2015.06 currently contains a lot less
packages than the 2014.12 feeds did.

At least this is true for armv7at2hf-vfp/ and armv7at2hf-vfp-neon/. E.g.
the first package at the very top which is missing is a52dec, but there
is a lot of stuff like binutils or mono which are missing.

Is this intentional? build-feeds.sh in meta-angstrom/contrib/ seems not
to be altered recently, so it should produce the same packages...?

--
Stefan

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