Re: [Angstrom-devel] [meta-angstrom][PATCH] angstrom.inc: set arm instruction set with existing machine overrides
> On Jul 27, 2016, at 10:55 AM, Max Krummenacherwrote: > > _armv4t, _armv5te are not (no longer?) set as MACHINEOVERRIDES if an armv4t > or armv5te tune is set. > Thus the default ARM_INSTRUCTION_SET ??= "thumb" kicks in. > > Set the override to _armv4, _armv5 to get the expected ARM_INSTRUCTION_SET. > > While at it cleanup comment to keep up with changes. > > Build tested with a build for a _armv5te machine. this is ok. > > Signed-off-by: Max Krummenacher > --- > conf/distro/include/angstrom.inc | 19 +-- > 1 file changed, 9 insertions(+), 10 deletions(-) > > diff --git a/conf/distro/include/angstrom.inc > b/conf/distro/include/angstrom.inc > index 778ab10..09f6121 100644 > --- a/conf/distro/include/angstrom.inc > +++ b/conf/distro/include/angstrom.inc > @@ -46,16 +46,6 @@ require conf/distro/include/angstrom-${TCLIBC}.inc > require conf/distro/include/angstrom-java.inc > require conf/distro/include/angstrom-jalimo.conf > > -# ARM920T and up can use thumb mode to decrease binary size at the expense > of speed > -# (the complete story is a bit more nuanced due to cache starvation) > -# Angstrom turns on thumb for armv4t machine according to this RFC: > -# > http://lists.linuxtogo.org/pipermail/angstrom-distro-devel/2008-October/002714.html > - > -ARM_INSTRUCTION_SET ??= "thumb" > -ARM_INSTRUCTION_SET_armv4t ?= "arm" > -ARM_INSTRUCTION_SET_armv5te ?= "arm" > -ARM_INSTRUCTION_SET_armv6 ?= "arm" > - > # "arm" "thumb" > #The instruction set the compiler should use when generating application > #code. The kernel is always compiled with arm code at present. arm code > @@ -63,6 +53,15 @@ ARM_INSTRUCTION_SET_armv6 ?= "arm" > #encoded RISC sub-set. Thumb code is smaller (maybe 70% of the ARM size) > #but requires more instructions (140% for 70% smaller code) so may be > #slower. > +#thumb 2 is an evolution of the original thumb instruction set which > strives > +#to keep the code size advantages without the performance penality. > +#When setting thumb the compiler will use thumb or thumb2 depending on > what > +#the selected arm architecture. > + > +ARM_INSTRUCTION_SET ??= "thumb" > +ARM_INSTRUCTION_SET_armv4 ?= "arm" > +ARM_INSTRUCTION_SET_armv5 ?= "arm" > +ARM_INSTRUCTION_SET_armv6 ?= "arm" > > #Use this variable in feeds and other parts that need a URI > ANGSTROM_URI ?= "http://feeds.angstrom-distribution.org; > -- > 2.5.5 > > > ___ > Angstrom-distro-devel mailing list > Angstrom-distro-devel@linuxtogo.org > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel signature.asc Description: Message signed with OpenPGP using GPGMail ___ 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
On Wed, Apr 20, 2016 at 12:49 PM Stefan Agnerwrote: > 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 ? > > -- > Stefan > > ___ > Angstrom-distro-devel mailing list > Angstrom-distro-devel@linuxtogo.org > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel > ___ 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][PATCH][master][angstrom-v2015.12-yocto2.0] angstrom.conf: arm: use compatible glibc and glibc-locale
> On Oct 17, 2015, at 2:27 AM, Max Krummenacherwrote: > > oe-core moved to glibc and cross-localedef-native based on version 2.22. > Angstrom currently uses linaro glibc in version 2.20 for arm. > This leads to incompatible locales. They cause exeptions or hangs. e.g.: > > root@colibri-imx6:~# sh -c "LANG=en_US" > sh: loadlocale.c:130: _nl_intern_locale_data: Assertion `cnt < (sizeof > (_nl_value_type_LC_COLLATE) / sizeof (_nl_value_type_LC_COLLATE[0]))' > failed. > Aborted applied thank you > > root@colibri-imx6:~# localectl status > ^C > > Signed-off-by: Max Krummenacher > --- > conf/distro/angstrom.conf | 2 -- > 1 file changed, 2 deletions(-) > > diff --git a/conf/distro/angstrom.conf b/conf/distro/angstrom.conf > index 330aebd..680bbd1 100644 > --- a/conf/distro/angstrom.conf > +++ b/conf/distro/angstrom.conf > @@ -58,12 +58,10 @@ ANGSTROM_GDB_VERSION ?= "7.9%" > #use Linaro tools for ARM > ANGSTROM_GCC_VERSION_arm ?= "linaro-4.9%" > ANGSTROM_BINUTILS_VERSION_arm?= "linaro-%" > -GLIBCVERSION_arm ?= "linaro-2.2%" > ANGSTROM_GDB_VERSION_arm ?= "linaro-%" > ANGSTROM_GCC_VERSION_aarch64 ?= "linaro-4.9%" > ANGSTROM_BINUTILS_VERSION_aarch64?= "linaro-%" > ANGSTROM_GDB_VERSION_aarch64 ?= "linaro-%" > -GLIBCVERSION_aarch64 ?= "linaro-2.2%" > PREFERRED_VERSION_cross-localedef-native ?= "2.2%" > > ANGSTROM_QEMU_VERSION?= "2%" > -- > 1.8.4.5 > > > ___ > Angstrom-distro-devel mailing list > Angstrom-distro-devel@linuxtogo.org > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel signature.asc Description: Message signed with OpenPGP using GPGMail ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] why linaro toolchain
On May 20, 2015, at 1:05 AM, Andreas Müller schnitzelt...@googlemail.com wrote: I wonder why angstrom pins toolchain to linaro version. Especially * there is no hint where to get linaro toolchain * if no linaro toolchain is found oe-core' default suggestion for gcc's version is overridden and gcc 5 is used causing strange trouble at least for meta-fsl kernels. Could we stop pinning in times of releases? angstrom has always used linaro toolchain for ARM platforms. Nothing new there you might be seeing some bugs which always happen due to changes in OE-Core preferred providers and introduction of new packages in toolchain etc. So post the errors. signature.asc Description: Message signed with OpenPGP using GPGMail ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] required layers
On May 20, 2015, at 12:06 PM, Trevor Woerner twoer...@gmail.com wrote: Commit8f0df794f289c0ffcc30fe77d19c5f1880f05f0c makes it necessary for the meta-qt5 layer to be available since it contains classes/populate_sdk_qt5.bbclass. Was this intentional? If so the README file should include this dependency. its required to generate qt5 SDK. We always have meta-qt5 in layer mix for angstrom. I think README needs a general update. We have images that require meta-gnome and meta-xfce and meta-efl as well. https://github.com/Angstrom-distribution/meta-angstrom/commit/8f0df794f289c0ffcc30fe77d19c5f1880f05f0c ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel signature.asc Description: Message signed with OpenPGP using GPGMail ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Feed Server Mirror Optical Experiments
On Thu, May 14, 2015 at 1:47 PM, Marcel Ziswiler mar...@ziswiler.com wrote: Thanks, Tom On Thu, 2015-05-14 at 11:32 -0700, Tom King wrote: Current is about 275GB but I suspect by the time that 2015.6 is out it will be close to 335GB. That sounds very much doable then. I believe our IT was talking about some 12TB being available. as I just started hosting this I don't have real good metrics on BW. OK, no problem. I fed that information back to our IT expecting them to start doing an rsync style mirror soon and will provide our DNS information once available. Thanks for stepping up Marcel, much appreciated. Cheers Marcel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [PATCH] angstrom: Fix access using empty root password
On Sat, May 9, 2015 at 12:00 AM, Koen Kooi k...@dominion.thruhere.net wrote: Op 8 mei 2015, om 03:01 heeft Khem Raj raj.k...@gmail.com het volgende geschreven: We are not able to login into angstrom images now since many chnages has gone into upstream OE-core drop libpam change to drop secure nullok add empty-root-password to EXTRA_IMAGE_FEAUTURES it should actually be controlled and added only for debug images, but thats for production folks Signed-off-by: Khem Raj raj.k...@gmail.com Acked-by: Koen Kooi k...@dominion.thruhere.net Can you push this yourself? Done ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] [PATCH] angstrom: Fix access using empty root password
We are not able to login into angstrom images now since many chnages has gone into upstream OE-core drop libpam change to drop secure nullok add empty-root-password to EXTRA_IMAGE_FEAUTURES it should actually be controlled and added only for debug images, but thats for production folks Signed-off-by: Khem Raj raj.k...@gmail.com --- conf/distro/include/angstrom-core-tweaks.inc | 2 +- recipes-tweaks/pam/libpam_1.1.6.bbappend | 4 2 files changed, 1 insertion(+), 5 deletions(-) delete mode 100644 recipes-tweaks/pam/libpam_1.1.6.bbappend diff --git a/conf/distro/include/angstrom-core-tweaks.inc b/conf/distro/include/angstrom-core-tweaks.inc index 1f0cd41..53e497f 100644 --- a/conf/distro/include/angstrom-core-tweaks.inc +++ b/conf/distro/include/angstrom-core-tweaks.inc @@ -36,7 +36,7 @@ MACHINEOVERRIDES[vardepsexclude] += SOC_FAMILY # opkg PREFERRED_PROVIDER_opkg-collateral = angstrom-feed-configs -EXTRA_IMAGE_FEATURES ?= package-management +EXTRA_IMAGE_FEATURES ?= package-management empty-root-password PREFERRED_PROVIDER_os-release = angstrom-version diff --git a/recipes-tweaks/pam/libpam_1.1.6.bbappend b/recipes-tweaks/pam/libpam_1.1.6.bbappend deleted file mode 100644 index aa8e1a3..000 --- a/recipes-tweaks/pam/libpam_1.1.6.bbappend +++ /dev/null @@ -1,4 +0,0 @@ -#allow empty password -do_install_append () { - sed -i -e 's:nullok_secure:nullok:g' ${D}${sysconfdir}/pam.d/common-auth -} -- 2.1.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] invalid upstream refs/remotes/github/fido
On Mon, May 4, 2015 at 6:20 PM, Trevor Woerner twoer...@gmail.com wrote: When I run ./setup-environment (which runs setup-environment-internal) I get an error: # sources/meta-96boards: rebasing trevor/work - refs/remotes/github/fido fatal: Needed a single revision invalid upstream refs/remotes/github/fido this is a result of line 64: repo rebase Performing this command on each repository individually (by hand), all the repositories which don't have a named branch will fail (i.e. all those that set revision=sha1) e.g. meta-96boards, meta-qualcomm, meta-handheld, ... Is this rebase needed? Is there a better way to do it? I think we changed default branch to 'fido' on 2015.06 branch that should be reverted back to master the reason is most of repos dont have 'fido' branch. ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [PATCH][next] conf/local.conf: adjust DISTRO
On May 2, 2015, at 4:38 AM, Trevor Woerner twoer...@gmail.com wrote: On 04/25/15 21:54, Khem Raj wrote: and we also have repo based setup now. See https://github.com/Angstrom-distribution/angstrom-manifest Thanks for adding an angstrom-v2015.06-yocto1.8 branch :-) yes and please let us know if you run into problems. post patches or fixes if you find issues. ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [PATCH][next] conf/local.conf: adjust DISTRO
On Sat, Apr 25, 2015 at 6:52 PM, Khem Raj raj.k...@gmail.com wrote: On Sat, Apr 25, 2015 at 6:40 PM, Trevor Woerner twoer...@gmail.com wrote: The DISTRO in meta-angstrom[next] changed from angstrom-next to angstrom, adjust the configuration to match. thanks for doing it. Can you send a github pull request ? and we also have repo based setup now. See https://github.com/Angstrom-distribution/angstrom-manifest Signed-off-by: Trevor Woerner twoer...@gmail.com --- conf/local.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/conf/local.conf b/conf/local.conf index 14ee014..660e950 100644 --- a/conf/local.conf +++ b/conf/local.conf @@ -20,7 +20,7 @@ NOISO = 1 PARALLEL_MAKE = -j2 BB_NUMBER_THREADS = 2 -DISTRO = angstrom-next +DISTRO = angstrom # Set DEPLOY_DIR outside of TMPDIR DEPLOY_DIR = ${TMPDIR}/../../deploy/${TCLIBC} -- 2.4.0.rc2.43.gfb89636 ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [PATCH][next] conf/local.conf: adjust DISTRO
On Sat, Apr 25, 2015 at 6:40 PM, Trevor Woerner twoer...@gmail.com wrote: The DISTRO in meta-angstrom[next] changed from angstrom-next to angstrom, adjust the configuration to match. thanks for doing it. Can you send a github pull request ? Signed-off-by: Trevor Woerner twoer...@gmail.com --- conf/local.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/conf/local.conf b/conf/local.conf index 14ee014..660e950 100644 --- a/conf/local.conf +++ b/conf/local.conf @@ -20,7 +20,7 @@ NOISO = 1 PARALLEL_MAKE = -j2 BB_NUMBER_THREADS = 2 -DISTRO = angstrom-next +DISTRO = angstrom # Set DEPLOY_DIR outside of TMPDIR DEPLOY_DIR = ${TMPDIR}/../../deploy/${TCLIBC} -- 2.4.0.rc2.43.gfb89636 ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] [PATCH] angstrom-v2014.12.conf: Dont mix gcc sources
In angstrom we use linaro gcc for ARM, but only for cross and target compilers, when it comes to cross sdk compilers then we switch to OE-core, this worked fine until gcc-source recipe was introduced, the implementation forces to have just 1 version of gcc sources, which happens to be provided by linaro gcc here, so as soon as it comes to building non-linaro gcc it does not know that sources are not in expected shared location Signed-off-by: Khem Raj raj.k...@gmail.com --- conf/distro/angstrom-v2014.12.conf | 1 - 1 file changed, 1 deletion(-) diff --git a/conf/distro/angstrom-v2014.12.conf b/conf/distro/angstrom-v2014.12.conf index f3ba380..9bc3e49 100644 --- a/conf/distro/angstrom-v2014.12.conf +++ b/conf/distro/angstrom-v2014.12.conf @@ -64,7 +64,6 @@ ANGSTROM_NATIVE_BINUTILS_VERSION ?= 2.24% ANGSTROM_GCC_VERSION_arm ?= linaro-4.9% ANGSTROM_GCC_VERSION_aarch64 ?= linaro-4.9% # we use OE-Core for native and nativesdk GCC -SDKGCCVERSION_arm?= 4.9% ANGSTROM_BINUTILS_VERSION_arm?= linaro-% ANGSTROM_BINUTILS_VERSION_aarch64?= linaro-% ANGSTROM_GDB_VERSION_arm ?= linaro-% -- 2.1.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] do_compile error in environment-angstrom-v2014.12
Gibson On Sat, Apr 4, 2015 at 1:53 AM, Gibson Justian guitargib...@gmail.com wrote: Hi, I applied patch for libpostproc and then made a build like 1).MACHINE=beaglebone bitbake cloud9-gnome-image -c clean 2).MACHINE=beaglebone bitbake cloud9-gnome-image I get this error, where am I going wrong? below does not tell what compiler errored on. Can you see that in /home/gibson/setup-scripts/build/tmp-angstrom_v2014_12-glibc/work/armv7at2hf-vfp-neon-angstrom-linux-gnueabi/gst-ffmpeg/0.10.13-r8/temp/log.do_compile.345 and post that snippet ? make[3]: *** [libgstffmpeg_la-gstffmpeg.lo] Error 1 | make[3]: Leaving directory `/home/gibson/setup-scripts/build/tmp-angstrom_v2014_12-glibc/work/armv7at2hf-vfp-neon-angstrom-linux-gnueabi/gst-ffmpeg/0.10.13-r8/build/ext/ffmpeg' | make[2]: *** [all-recursive] Error 1 | make[2]: Leaving directory `/home/gibson/setup-scripts/build/tmp-angstrom_v2014_12-glibc/work/armv7at2hf-vfp-neon-angstrom-linux-gnueabi/gst-ffmpeg/0.10.13-r8/build/ext' | make[1]: *** [all-recursive] Error 1 | make[1]: Leaving directory `/home/gibson/setup-scripts/build/tmp-angstrom_v2014_12-glibc/work/armv7at2hf-vfp-neon-angstrom-linux-gnueabi/gst-ffmpeg/0.10.13-r8/build' | make: *** [all] Error 2 | ERROR: oe_runmake failed | WARNING: exit code 1 from a shell command. | ERROR: Function failed: do_compile (log file is located at /home/gibson/setup-scripts/build/tmp-angstrom_v2014_12-glibc/work/armv7at2hf-vfp-neon-angstrom-linux-gnueabi/gst-ffmpeg/0.10.13-r8/temp/log.do_compile.345) ERROR: Task 6081 (/home/gibson/setup-scripts/sources/openembedded-core/meta/recipes-multimedia/gstreamer/ gst-ffmpeg_0.10.13.bb, do_compile) failed with exit code '1' -- Regards, Gibson.J ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] angstrom-v2014.12-yocto1.7 build fails
On Mar 19, 2015, at 6:50 PM, Gibson Justian guitargib...@gmail.com wrote: Hi Koen and Khem , I was building the Angstrom linux for beaglebone black. I have been trying to build it for couple of months. I tried couple of times with 64-bit machine with Debian 7.8 and Centos == failed. I tried with a 32 bit machine with Debian 7.8 = failed Actually fails in the libpostproc and opencv --- Below are the console output. --- configure: set WARNING_CFLAGS to -Wall -Wdeclaration-after-statement -Wvla -Wpointer-arith -Wmissing-declarations -Wmissing-prototypes -Wredundant-decls -Wundef -Wwrite-strings -Wformat-nonliteral -Wformat-security -Wold-style-definition -Winit-self -Wmissing-include-dirs -Waddress -Waggregate-return -Wno-multichar -Wnested-externs | configure: set ERROR_CFLAGS to | checking for BZ2_bzlibVersion in -lbz2... yes | checking bzlib.h usability... yes | checking bzlib.h presence... yes | checking for bzlib.h... yes | checking for FFMPEG... yes | checking for POSTPROC... configure: error: Package requirements (libpostproc libavcodec libavutil) were not met: | | No package 'libpostproc’ found you need something like http://lists.openembedded.org/pipermail/openembedded-core/2014-December/099751.html | | Consider adjusting the PKG_CONFIG_PATH environment variable if you | installed software in a non-standard prefix. | | Alternatively, you may set the environment variables POSTPROC_CFLAGS | and POSTPROC_LIBS to avoid the need to call pkg-config. | See the pkg-config man page for more details. | | Configure failed. The contents of all config.log files follows to aid debugging | ERROR: oe_runconf failed | WARNING: exit code 1 from a shell command. | ERROR: Function failed: do_configure (log file is located at /home/gibson/setup-scripts/build/tmp-angstrom_v2014_12-glibc/work/armv7at2hf-vfp-neon-angstrom-linux-gnueabi/gst-ffmpeg/0.10.13-r8/temp/log.do_configure.10569) ERROR: Task 6080 (/home/gibson/setup-scripts/sources/openembedded-core/meta/recipes-multimedia/gstreamer/ gst-ffmpeg_0.10.13.bb, do_configure) failed with exit code '1' Currently 1 running tasks (6333 of 7983): 0: opencv-2.4.9+gitAUTOINC+df8e28283f-r0 do_fetch (pid 28032) -- Regards, Gibson.J ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] read-only-rootfs
On Fri, Nov 14, 2014 at 1:12 AM, Jones,Michael michael.jo...@matrix-vision.de wrote: OK, I'll answer my own question: it looks like the support for 'EXTRA_IMAGE_FEATURES += read-only-rootfs' in openembedded-core only applies to sysvinit, and since Angstrom uses systemd by default, setting read-only-rootfs doesn't get you anywhere. thats right, but you can easily define the operations you want to cater in r-o-rfs ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] [RFC] repo based setup for angstrom
Hi I have been using repo based setup for angstrom distro for quite sometime now https://github.com/kraj/angstrom-manifest I would like to propose this to be included for mainline angstrom setup, therefore I am posting it here for comments and concerns Looking for feedback -Khem ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [PATCH][meta-angstrom] angstrom-next: don't pin OLDEST_KERNEL
On Wed, Oct 8, 2014 at 12:27 AM, Andreas Müller schnitzelt...@googlemail.com wrote: error caused in do_rootfs: | NOTE: Executing update_pixbuf_cache intercept ... | FATAL: kernel too old | WARNING: The postinstall intercept hook 'update_pixbuf_cache' failed (exit code: 127)! See log for details! and many other 'kernel too old' messages. So let's trust in OLDEST_KERNEL set by oe-core's bitbake.conf. Signed-off-by: Andreas Müller schnitzelt...@googlemail.com --- conf/distro/angstrom-next.conf | 2 -- 1 file changed, 2 deletions(-) diff --git a/conf/distro/angstrom-next.conf b/conf/distro/angstrom-next.conf index 03906ec..94e9226 100644 --- a/conf/distro/angstrom-next.conf +++ b/conf/distro/angstrom-next.conf @@ -21,8 +21,6 @@ DISTRO_VERSION = v${@time.strftime('%Y.%m',time.gmtime())} -OLDEST_KERNEL = 2.6.16 This is a good change but please note it will impact the feeds. They won't work with devices running older images anymore. - require conf/distro/include/sane-srcdates.inc require conf/distro/include/sane-srcrevs.inc require conf/distro/include/angstrom-preferred-versions.inc -- 1.8.3.1 ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Naming of the Angstrom derivative for resource limited systems
On Sat, Oct 4, 2014 at 12:27 AM, Koen Kooi k...@dominion.thruhere.net wrote: The current config has too many DISTRO_FEATURES, the biggest one being 'x11'. I'd love to keep systemd as init, but we might need something smaller as well. how about uselessd :) http://uselessd.darknedgy.net/ ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Naming of the Angstrom derivative for resource limited systems
On Friday, October 3, 2014, Koen Kooi k...@dominion.thruhere.net wrote: Hi, I have a number of systems on my desk (Wifi accesspoints mainly) and a few I want to buy (Arduino galileo, Intel edison) where the current angstrom config just doesn't fit. My plan is to add a config to deal with those systems and is binary incompatible with the regular angstrom. What I'm struggling with is coming up with a catchy name for it. After discussing it with a few people in person at Linaro Connect and virtually on IRC the following 2 options remain: 1) The Angstrom of Things (AoT) 2) Internet of Things - Angstrom (iota) Iota is what I like. Its in same line as measurement unit. I view it as iot answer is angstrom What are your thoughts on all this? thanks, Koen ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org javascript:; http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Regading beaglebone kernel build
On Mon, Sep 22, 2014 at 5:26 AM, Ratheendran R ratheendra...@gmail.com wrote: Can any one guide me on this build gap. am I missing something??. if you dont see it in TMPDIR that could be because by default rm_work is enabled. which means it will delete the sources after successful build. You could do bitbake -ccompile virtual/kernel and it will populate the build tree for kernel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] ExpansionError during parsing
On Fri, Aug 29, 2014 at 5:46 PM, Gibson Justian guitargib...@gmail.com wrote: make[2]: execvp: /bin/sh: Argument list too long | make[2]: *** what is /bin/sh pointing to ? are you building over nfs or do you have build directory symlinked ? ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] GNU gold vs ld
On Fri, Aug 8, 2014 at 5:07 AM, zbos...@pr.hu wrote: Hi, I am trying to create a small(ish) x86 Angström build with some updated components. One such component is MariaDB. I have some problems with the included MariaDB 5.1.67. First, it's too old. Second, it's not started automatically when I use an image that uses systemd. I had quite some obstacles with upgrading MariaDB in the new layer-based OpenEmbedded, starting with the switch to use CMake instead of autotools. Now, another biggie concerns the whole Angström build. I ran into this: https://mariadb.atlassian.net/browse/MDEV-5982 MariaDB fails to link at a very late stage because of this in meta-angstrom/conf/distro/include/angstrom-eglibc.inc : # We use gold as default linker for arm/x86 on eglibc based images DISTRO_FEATURES_append_arm = ld-is-gold DISTRO_FEATURES_append_x86 = ld-is-gold DISTRO_FEATURES_append_x86-64 = ld-is-gold Why does Angström use GNU gold? being multithreaded it speeds up the link time significantly on some large applications. You could fix this by providing own ld script where you remove the VERSION contruct. Since you may not be building all those qt libraries etc. you might consider not using gold. another option is to use ld.bfd just for mariadb package by setting LD properly for mariadb build. Because of the above, binutils builds with --enable-gold=default --enable-threads and behaves in a subtly different way than plain GNU ld. Best regards, Zoltán Böszörményi ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Building an older release
On Mon, Jul 28, 2014 at 7:18 AM, Kevin Fries kfr...@cctus.com wrote: OK, tried this again this morning... I wiped out everything and started over, including the download of the scripts: --- $ git clone https://github.com/Angstrom-distribution/setup-scripts.git Cloning into 'setup-scripts'... remote: Counting objects: 2021, done. remote: Compressing objects: 100% (14/14), done. remote: Total 2021 (delta 3), reused 0 (delta 0) Receiving objects: 100% (2021/2021), 663.37 KiB | 1.08 MiB/s, done. Resolving deltas: 100% (819/819), done. Checking connectivity... done. --- This should have given me a clean environment. Then I tied to config and checkout using the tag you gave me: --- $ cd setup-scripts/ $ ./oebb.sh config maintenance-2011.03 cd setup-scripts git checkout -b maintenance-2011.03 maintenance-2011.03 ./oebb.sh config yourmachine ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Building an older release
On Mon, Jul 28, 2014 at 10:08 AM, Kevin Fries kfr...@cctus.com wrote: So, when you say yourmachine, should I put arm-angstrom-linux-gnueabi? its the MACHINE name. look at in your machine layers under conf/machine/ there should be your machine configuration file called yourmachine.conf. ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] v2013.12 and kernel 3.2.28
On Sat, Jul 26, 2014 at 3:39 PM, Mark Ruys m...@paracas.nl wrote: Op 21 jul. 2014, om 13:35 heeft Koen Kooi k...@dominion.thruhere.net het volgende geschreven: Op 20 jul. 2014, om 00:34 heeft Mark Ruys m...@paracas.nl het volgende geschreven: I'm trying to build a Angstrom v2013.12 SD card to boot from. This is what I did essentially: git clone git://github.com/Angstrom-distribution/setup-scripts.git cd setup-scripts MACHINE=beagleboard ./oebb.sh config beagleboard ^ That says 'board', not 'bone' Ah, well, that says it all. After some effort, I've created my own eMMC flash SD-card based on Angstrom v2013.12. I tweaked the kernel so I have WATCHDOG_NOWAYOUT using 'bitbake -c menuconfig virtual/kernel'. As I don't trust SD-cards for reliable 24h operation, I want my BeagleBone to boot from eMMC under all circumstances. For this I altered the u-Boot bootcmd script. Indeed the eMMC u-Boot always runs the zImage kernel from eMMC at /dev/mmcblk1, regardless whether an SD-card is inserted or not: Hit any key to stop autoboot: 0 mmc1(part 0) is current device SD/MMC found on device 1 reading uEnv.txt 26 bytes read in 5 ms (4.9 KiB/s) Loaded environment from uEnv.txt Importing environment from mmc ... 4763976 bytes read in 303 ms (15 MiB/s) 26102 bytes read in 55 ms (462.9 KiB/s) Kernel image @ 0x8020 [ 0x00 - 0x48b148 ] ## Flattened Device Tree blob at 80f8 Booting using the fdt blob at 0x80f8 Using Device Tree in place at 80f8, end 80f895f5 Starting kernel ... But to my surprise, this kernel still wants to mount the SD-card (/dev/mmcblk0) as rootfs. I'm not sure if I ask the right mailing list this question..., but does anyone knows how to let the kernel mount eMMC as the root fs, and not try to use the SD-card? This isn't a kernel build config option, is it? There could be that option for selecting root is passed from bootloader environment. You might be able to cook a u-boot script to boot from eMMC if there already is not one. Mark ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] BB cross compile
On Thu, Jul 17, 2014 at 3:19 PM, Mark Ruys m...@paracas.nl wrote: Is this because 'hello' is compiled as a hard-float binary which the BeagleBone doesn't run, or because the hello binary is compiled for Angstrom v2013.12 which is not compatible with v2012.12. If not, what is the problem here?How do I get a 'hello' binary that does run on my bbb? yes your hello is compiled with hf ABI whereas your rootfs is softfloat ABI ___ 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][v2014.06] update-alternatives: use package created by opkg-utils
On Jul 14, 2014 12:52 PM, mk max.oss...@gmail.com wrote: Hi Khem Without this patch the opkg-utils recipe is built and the opkg-utils package is installed for VIRTUAL-RUNTIME_update-alternatives. Please cherry-pick following from master commit 14e08075a40d8959332f6f8c1f70d4d129544f9d This commit is already part of the angstrom-v2014.06-yocto1.6 branch. The issue is that each recipe which uses the update-alternatives.bbclass (e.g. busybox) gets VIRTUAL-RUNTIME_update-alternatives added to its RDEPENDS. http://cgit.openembedded.org/openembedded-core/tree/meta/classes/update-alternatives.bbclass?h=daisy#n225 Without this patch opkg-utils (plus a bunch of python packages it depends on) gets installed instead of update-alternatives-opkg. I tried this on a fresh checkout of angstrom-v2014.06-yocto1.6 and a build of MACHINE=beagleboard ./oebb.sh bitbake console-image The recipe opkg-utils builds the packages opkg-utils and update-alternatives-opkg. So PREFERRED_PROVIDER_virtual/update-alternatives-native and PREFERRED_PROVIDER_virtual/update-alternative should be set to the recipe and ANGSTROM_IPK_UPDATE_ALTERNATIVES, DISTRO_UPDATE_ALTERNATIVES, VIRTUAL-RUNTIME_update-alternatives to the package. i see. this should be ok then Am I missing something Regards Max ___ 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][v2014.06] update-alternatives: use package created by opkg-utils
On Sun, Jul 13, 2014 at 6:43 AM, Max Krummenacher max.oss...@gmail.com wrote: In daisy update-alternatives has been moved from opkg to the opkg-utils recipe. opkg-utils now creates an additional package update-alternatives-opkg. Without this patch the opkg-utils recipe is built and the opkg-utils package is installed for VIRTUAL-RUNTIME_update-alternatives. Please cherry-pick following from master commit 14e08075a40d8959332f6f8c1f70d4d129544f9d Author: Khem Raj raj.k...@gmail.com Date: Wed Jan 22 10:30:06 2014 -0800 Adjust to the omission of opkg UPDATE_ALTERNATIVES change from OE-Core Signed-off-by: Khem Raj raj.k...@gmail.com and adjust if needed. --- conf/distro/include/angstrom-package-ipk.inc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/conf/distro/include/angstrom-package-ipk.inc b/conf/distro/include/angstrom-package-ipk.inc index 7e0c68c..8a9894c 100644 --- a/conf/distro/include/angstrom-package-ipk.inc +++ b/conf/distro/include/angstrom-package-ipk.inc @@ -4,12 +4,12 @@ ANGSTROM_FEED_CONFIGS ?= angstrom-feed-configs EXTRAOPKGCONFIG = opkg-config-base ${ANGSTROM_FEED_CONFIGS} -ANGSTROM_IPK_UPDATE_ALTERNATIVES ?= opkg-utils +ANGSTROM_IPK_UPDATE_ALTERNATIVES ?= update-alternatives-opkg DISTRO_UPDATE_ALTERNATIVES = ${ANGSTROM_IPK_UPDATE_ALTERNATIVES} # we need the same provider for opkg and u-a PREFERRED_PROVIDER_virtual/update-alternatives-native ?= opkg-utils-native -PREFERRED_PROVIDER_virtual/update-alternatives = ${ANGSTROM_IPK_UPDATE_ALTERNATIVES} +PREFERRED_PROVIDER_virtual/update-alternatives = opkg-utils VIRTUAL-RUNTIME_update-alternatives = ${ANGSTROM_IPK_UPDATE_ALTERNATIVES} -- 1.8.4.5 ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] systemd FTBFS
On Sat, Jul 5, 2014 at 11:16 AM, Sergey Lapin slapi...@gmail.com wrote: which seems to be due to bug in linaro-gcc LTO support. What are plans regarding this, is temprorary fix .bbappend ongoing or we should wait for toolchain fix? Add a bbappend to disable LTO via cflags, it should be fixed in linaro GCC but this can take time. ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] systemd FTBFS
On Sun, Jul 6, 2014 at 9:13 AM, Sergey Lapin slapi...@gmail.com wrote: I'd appreciate any examples for such .bbappend file. CFLAGS += -fno-lto ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Installing on MacOSX
On Tue, May 13, 2014 at 4:06 PM, Josejulio Martínez finwemarti...@gmail.com wrote: Hello, i would like to know if is anyone aware if is possible to install the cross compilation, when i run MACHINE=beaglebone ./oebb.sh update I get: *FATAL: /dev/shm does not exist or is not writable* I have been googling a bit, and couldn't find a workaround to this. IIRC no one reported successful use of MacOSX being used as build host. ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] The mail archives are been offline (404-not found)
On Tue, May 13, 2014 at 9:15 PM, Bob Feretich bob.feret...@rafresearch.com wrote: The mailing list archives have been offline for several days, What's happening? Catastrophic server failure? you could use gmane http://www.mail-archive.com/angstrom-distro-devel@linuxtogo.org/ ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] [PATCH 1/2] openssh: Tweak sshd_config to tackle for PAM taking care of authentication
We sort of disable clear text PasswordAuthentication pam does not like it Signed-off-by: Khem Raj raj.k...@gmail.com --- recipes-tweaks/openssh/openssh_6.2p2.bbappend |3 +++ 1 file changed, 3 insertions(+) create mode 100644 recipes-tweaks/openssh/openssh_6.2p2.bbappend diff --git a/recipes-tweaks/openssh/openssh_6.2p2.bbappend b/recipes-tweaks/openssh/openssh_6.2p2.bbappend new file mode 100644 index 000..7e477c5 --- /dev/null +++ b/recipes-tweaks/openssh/openssh_6.2p2.bbappend @@ -0,0 +1,3 @@ +do_install_append () { + sed -i -e 's:^#PasswordAuthentication.*$:PasswordAuthentication no:g' ${D}${sysconfdir}/ssh/sshd_config +} -- 1.7.10.4 ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] [PATCH 2/2] libpam: Disable nullok_secure
This will let us ssh with empty password as root user. Its less secure but good for development work. Signed-off-by: Khem Raj raj.k...@gmail.com --- recipes-tweaks/pam/libpam_1.1.6.bbappend |4 1 file changed, 4 insertions(+) create mode 100644 recipes-tweaks/pam/libpam_1.1.6.bbappend diff --git a/recipes-tweaks/pam/libpam_1.1.6.bbappend b/recipes-tweaks/pam/libpam_1.1.6.bbappend new file mode 100644 index 000..aa8e1a3 --- /dev/null +++ b/recipes-tweaks/pam/libpam_1.1.6.bbappend @@ -0,0 +1,4 @@ +#allow empty password +do_install_append () { + sed -i -e 's:nullok_secure:nullok:g' ${D}${sysconfdir}/pam.d/common-auth +} -- 1.7.10.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] Creating a flashing image for Beaglebone Black
On Feb 25, 2014, at 6:51 PM, Robert Nelson robertcnel...@gmail.com wrote: Might be a little bit-rotten, but the scripts are here: https://github.com/beagleboard/meta-beagleboard/tree/master/contrib/bone-flash-tool Never used them personally, just referenced them when creating the new debian based beagleboard.org image. Regards, use https://github.com/beagleboard/meta-beagleboard/tree/master/contrib/bone-flash-tool thats maintained. signature.asc Description: Message signed with OpenPGP using GPGMail ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Creating a flashing image for Beaglebone Black
On Feb 25, 2014, at 7:00 PM, Robert Nelson robertcnel...@gmail.com wrote: On Tue, Feb 25, 2014 at 8:55 PM, Khem Raj raj.k...@gmail.com wrote: On Feb 25, 2014, at 6:51 PM, Robert Nelson robertcnel...@gmail.com wrote: Might be a little bit-rotten, but the scripts are here: https://github.com/beagleboard/meta-beagleboard/tree/master/contrib/bone-flash-tool Never used them personally, just referenced them when creating the new debian based beagleboard.org image. Regards, use https://github.com/beagleboard/meta-beagleboard/tree/master/contrib/bone-flash-tool thats maintained. I don't think you can really call that repo maintained anymore.. https://github.com/beagleboard/meta-beagleboard/commits/master If Koen, has a clone of that somewhere, his version would be considered maintained.. whats your point ? have you looked at both repositories and seen which one has activity ? signature.asc Description: Message signed with OpenPGP using GPGMail ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Building Angstrom for Beaglebone from Source - Issue
log_check: Matched keyword: [ERR] this has been fixed. Can you try 2013.12 branch please ? After step 1 *The followed steps:* *1)* git clone git://github.com/Angstrom-distribution/setup-scripts.git *OK* *do * *git checkout -b **angstrom-v2013.12-yocto1.5 origin/angstrom-v2013.12-yocto1.5* *and then follow same steps* On Wed, Feb 12, 2014 at 12:12 PM, André Araújo an...@ingeniarius.pt wrote: Hi, Thanks for help! In attach i send the corresponding log error from this: ERROR: ld.so: object 'libpseudo.so' from LD_PRELOAD cannot be preloaded: ignored. ERROR: Function failed: do_rootfs (see /home/andre/Desktop/setup-scripts/build/tmp-angstrom_v2013_06-eglibc/work/beaglebone-angstrom-linux-gnueabi/systemd-gnome-image/1.0-r0/temp/log.do_rootfs.4775 for further information) ERROR: Task 7 (/home/andre/Desktop/setup-scripts/sources/meta-angstrom/recipes-images/angstrom/ systemd-gnome-image.bb, do_rootfs) failed with exit code '1' NOTE: Tasks Summary: Attempted 7171 tasks of which 7170 didn't need to be rerun and 1 failed. No currently running tasks (7170 of 7174) Summary: 1 task failed: /home/andre/Desktop/setup-scripts/sources/meta-angstrom/recipes-images/angstrom/ systemd-gnome-image.bb, do_rootfs Kind regards, -- André Araújo 2014-02-12 20:07 GMT+00:00 Khem Raj raj.k...@gmail.com: please post the complete error log and also send to angstrom-distro-devel@linuxtogo.org as well so more folks can help you On Wed, Feb 12, 2014 at 11:26 AM, André Araújo an...@ingeniarius.ptwrote: Hi Khem, I'm trying to build a full distribution of Angstrom, to use in a BeagleBone Black to support a Texas Instrument module CC3000, using this TI tutorial ( http://processors.wiki.ti.com/index.php/CC3000_Module_with_AM335x_Using_Linux) . *All compiles well but in this step:* *MACHINE=beaglebone ./oebb.sh bitbake systemd-gnome-image* *it occurs an error, almost at the end (task 7171 of 7175) of the compilation:* ERROR: Function failed: do_rootfs (see /home/andre/Desktop/setup-scripts/build/tmp-angstrom_v2013_06-eglibc/work/beaglebone-angstrom-linux-gnueabi/systemd-gnome-image/1.0-r0/temp/log.do_rootfs.30194 for further information) ERROR: Task 7 (/home/andre/Desktop/setup-scripts/sources/meta-angstrom/recipes-images/angstrom/ systemd-gnome-image.bb, do_rootfs) failed with exit code '1' I have search in several forums and experiment some solution but unsuccessful, i am in this dead-lock for 3 days, please do you have any idea the reason to this issue? *The followed steps:* *1)* git clone git://github.com/Angstrom-distribution/setup-scripts.git *OK* *2)* MACHINE=beaglebone ./oebb.sh config beaglebone *OK* *3) *MACHINE=beaglebone ./oebb.sh update *OK* *4) *sudo apt-get install gawk wget git-core diffstat unzip texinfo build-essential chrpath libsdl1.2-dev xterm bitbake *OK* *5) *MACHINE=beaglebone ./oebb.sh bitbake virtual/kernel *OK* *6) *MACHINE=beaglebone ./oebb.sh bitbake systemd-gnome-image *ERROR* *System: *Ubuntu 12.04.4 LTS *kernel version: *3.11.0-15-generic If you could help I will be immensely grateful. And if you need any information to understand better the issue please ask. Kind Regards, -- André Araújo ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Contents of /proc/cpuinfo on the Beaglebone Black
On Tue, Jan 28, 2014 at 12:38 PM, Andrei Radulescu-Banu andrei.radulescu-b...@exfo.com wrote: With its manufacturing image, the BeagleBone Black only shows 297.40 BogoMIPS in its /proc/cpuinfo. The nominal processor speed is 1GHz, however. Does anyone know why this discrepancy? and does that happen with current release say 2013.12 as well ? ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Build error with latest sources in wp_block.c
On Monday, January 20, 2014 04:03:45 PM Andrei Radulescu-Banu wrote: enssl/crypto/whrlpool/wp_block.o ../deps/openssl/openssl/crypto/whrlpool/wp_block.c make[1]: execvp: printf: Argument list too long what is your host OS distribution and default shell ? and whats value of ARG_MAX declared in /include/linux/limits.h -- -Khem signature.asc Description: This is a digitally signed message part. ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] [PATCH 2/2] angstrom-xinit: Add recipe
This recipe will launch bare X using systemd Signed-off-by: Khem Raj raj.k...@gmail.com --- recipes-angstrom/angstrom/angstrom-xinit.bb| 18 ++ recipes-angstrom/angstrom/angstrom-xinit/X.service | 19 +++ 2 files changed, 37 insertions(+) create mode 100644 recipes-angstrom/angstrom/angstrom-xinit.bb create mode 100644 recipes-angstrom/angstrom/angstrom-xinit/X.service diff --git a/recipes-angstrom/angstrom/angstrom-xinit.bb b/recipes-angstrom/angstrom/angstrom-xinit.bb new file mode 100644 index 000..71ec944 --- /dev/null +++ b/recipes-angstrom/angstrom/angstrom-xinit.bb @@ -0,0 +1,18 @@ +DESCRIPTION = Systemd service to start a bare X session +LICENSE = MIT +LIC_FILES_CHKSUM = file://${COREBASE}/LICENSE;md5=3f40d7994397109285ec7b81fdeb3b58 + +SRC_URI = file://X.service \ + +inherit systemd + +do_install() { + install -d ${D}${systemd_unitdir}/system/ + install -m 0644 ${WORKDIR}/*.service ${D}${systemd_unitdir}/system +} + +SYSTEMD_SERVICE_${PN} = X.service + +RDEPENDS_${PN} = packagegroup-core-x11-xserver +PACKAGE_ARCH = all + diff --git a/recipes-angstrom/angstrom/angstrom-xinit/X.service b/recipes-angstrom/angstrom/angstrom-xinit/X.service new file mode 100644 index 000..54cb5f6 --- /dev/null +++ b/recipes-angstrom/angstrom/angstrom-xinit/X.service @@ -0,0 +1,19 @@ +[Unit] +Description=Xserver startup + +[Service] +ExecStart=/usr/bin/X -wr +Restart=always +KillMode=none +SendSIGKILL=no + +# the following allows 5 restarts in a 300s (5 minute) interval. If we hit the limit +# then we reboot the system +StartLimitInterval=300s +StartLimitBurst=5 +StartLimitAction=reboot + + +[Install] +WantedBy=graphical.target + -- 1.8.5.2 ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] [PATCH 1/2] angstrom-x11vnc-xinit: Add systemd service for launching X11vnc over native display
Signed-off-by: Khem Raj raj.k...@gmail.com --- recipes-angstrom/angstrom/angstrom-x11vnc-xinit.bb | 21 - .../angstrom/angstrom-x11vnc-xinit/x11vnc.service | 11 +++ 2 files changed, 23 insertions(+), 9 deletions(-) create mode 100644 recipes-angstrom/angstrom/angstrom-x11vnc-xinit/x11vnc.service diff --git a/recipes-angstrom/angstrom/angstrom-x11vnc-xinit.bb b/recipes-angstrom/angstrom/angstrom-x11vnc-xinit.bb index a860247..863fbaf 100644 --- a/recipes-angstrom/angstrom/angstrom-x11vnc-xinit.bb +++ b/recipes-angstrom/angstrom/angstrom-x11vnc-xinit.bb @@ -1,22 +1,25 @@ -DESCRIPTION = Script to start a passwordless vnc of the current X session +DESCRIPTION = Systemd service to start a passwordless vnc of the current X session LICENSE = MIT LIC_FILES_CHKSUM = file://${COREBASE}/LICENSE;md5=3f40d7994397109285ec7b81fdeb3b58 -SRC_URI = file://x11vnc.desktop +SRC_URI = file://x11vnc.desktop \ + file://x11vnc.service \ + PR = r2 -do_install() { - install -d ${D}${sysconfdir}/X11/Xinit.d - echo #!/bin/sh ${D}${sysconfdir}/X11/Xinit.d/02vnc - echo x11vnc -q -bg -display :0 -forever -avahi ${D}${sysconfdir}/X11/Xinit.d/02vnc - chmod 0755 ${D}${sysconfdir}/X11/Xinit.d/02vnc +inherit systemd +do_install() { + install -d ${D}${systemd_unitdir}/system/ + install -m 0644 ${WORKDIR}/*.service ${D}${systemd_unitdir}/system install -d ${D}${sysconfdir}/xdg/autostart install -m 0644 ${WORKDIR}/x11vnc.desktop ${D}${sysconfdir}/xdg/autostart/ } -RDEPENDS_${PN} = x11vnc -CONFFILES_${PN} += ${sysconfdir}/X11/Xinit.d/02vnc ${sysconfdir}/xdg/autostart/x11vnc.desktop +SYSTEMD_SERVICE_${PN} = x11vnc.service + +RDEPENDS_${PN} = x11vnc angstrom-xinit +CONFFILES_${PN} += ${sysconfdir}/xdg/autostart/x11vnc.desktop PACKAGE_ARCH = all diff --git a/recipes-angstrom/angstrom/angstrom-x11vnc-xinit/x11vnc.service b/recipes-angstrom/angstrom/angstrom-x11vnc-xinit/x11vnc.service new file mode 100644 index 000..1e36d3d --- /dev/null +++ b/recipes-angstrom/angstrom/angstrom-x11vnc-xinit/x11vnc.service @@ -0,0 +1,11 @@ +[Unit] +Description=X11 VNC session on Native Display +Requires=X.service +After=X.service + +[Service] +Environment=DISPLAY=:0 +ExecStart=/usr/bin/x11vnc -loop + +[Install] +WantedBy=graphical.target -- 1.8.5.2 ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] building Angstrom for BeagleBone Black
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/13/2014 01:37 PM, tibor somogyi wrote: Traceback (most recent call last): File /usr/bin/bitbake, line 234, in module did you install ubuntu/debian bitbake package ? if you did please uninstall it. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlLUYMsACgkQuwUzVZGdMxRM4QCePIm3cZvbzOlDv/sMYevvfn75 13EAn1JuoF/eN8oSTSbEnliFuOSqcqzK =W2mM -END PGP SIGNATURE- ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] building Angstrom for BeagleBone Black
On Mon, Jan 13, 2014 at 3:40 PM, tibor somogyi somog...@slb.com wrote: Hello, I just uninstalled bitbake: - user@ubuntu:/home/tibor/beagle/setup-scripts$ sudo apt-get remove bitbake Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: python-support python-ply python-progressbar Use 'apt-get autoremove' to remove them. The following packages will be REMOVED: bitbake 0 upgraded, 0 newly installed, 1 to remove and 78 not upgraded. After this operation, 1,118 kB disk space will be freed. Do you want to continue [Y/n]? y (Reading database ... 185263 files and directories currently installed.) Removing bitbake ... Processing triggers for python-support ... Processing triggers for man-db ... user@ubuntu:/home/tibor/beagle/setup-scripts$ sudo MACHINE=beagleboard bitbake virtual/kernel sudo: bitbake: command not found Did you follow the angstrom setup instructions after the uninstall? bitbake should come from angstrom metadata repositories ie, your angstrom workspace and not from system. user@ubuntu:/home/tibor/beagle/setup-scripts$ Now I re-install it: why ? ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Building Angstrom for Yocto 1.4 'Dylan'
On Nov 27, 2013, at 8:56 AM, Brandon Stafford bran...@rascalmicro.com wrote: On Tue, Nov 26, 2013 at 6:49 PM, Khem Raj raj.k...@gmail.com wrote: On Tue, Nov 26, 2013 at 3:22 PM, Brandon Stafford bran...@rascalmicro.com wrote: ERROR: No recipes available for: /home/ubuntu/poky/meta-angstrom/recipes-tweaks/libgnome/libgnome_2.32.1.bbappend /home/ubuntu/poky/meta-angstrom/recipes-core/systemd/systemd_206.bbappend /home/ubuntu/poky/meta-angstrom/recipes-tweaks/connman/connman_1.17.bbappend ERROR: Command execution failed: Exited with 1 When I inspect the directories where the files are missing, it looks like I'm asking for older files than I should be. For example, systemd_208.bbappend (but not systemd_206.bbappend) exists in recipes-core/systemd/: https://github.com/Angstrom-distribution/meta-angstrom/tree/angstrom-v2013.06-yocto1.4/recipes-core/systemd Can anyone see where I'm screwing up? yes. There was a merge problem. Please update meta-angstrom and retry this should take care of systemd and connman for libgnome you need to add meta-gnome to your bblayer mix as well. I pulled your new commits, but this appears to fix only the connman error, not systemd. It looks like the Dylan branch uses systemd_199: http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-core/systemd?h=dylan If I rename systemd_206.bbappend to systemd_199.bbappend, the error disappears, and the build succeeds (or at least makes it farther-- it's not done yet). I have already pushed a fix for this. Please update. Is that the right fix? Yes. Brandon ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Building Angstrom for Yocto 1.4 'Dylan'
On Wed, Nov 27, 2013 at 4:23 PM, Brandon Stafford bran...@rascalmicro.com wrote: On Wed, Nov 27, 2013 at 3:21 PM, Koen Kooi k...@dominion.thruhere.netwrote: Op 27 nov. 2013, om 00:22 heeft Brandon Stafford bran...@rascalmicro.com het volgende geschreven: Hi all, I'm trying to build Angstrom based on Yocto 1.4 'Dylan' for a SAMA5D3 board. You're not doing that actually, if you where, you would be using https://github.com/angstrom-distribution/setup-scripts and following the instructions in the README. Sorry. To explain, the board I'm targeting is a new board based on the SAMA5D3, so I didn't think setting MACHINE would work properly. Sounds like I was wrong. I have modified bblayers.conf: BBLAYERS ?= \ /home/ubuntu/poky/meta-angstrom \ /home/ubuntu/poky/meta-openembedded/meta-oe \ /home/ubuntu/poky/meta-openembedded/meta-systemd \ /home/ubuntu/poky/meta-atmel \ /home/ubuntu/poky/meta \ /home/ubuntu/poky/meta-yocto \ /home/ubuntu/poky/meta-yocto-bsp \ The above is an incomplete collection of incompatible layers, don't do that. How can I tell whether a layer is compatible or not? I just realized that you did not use angstrom release as it should be. best is you follow angstrom scripts git clone https://github.com/Angstrom-distribution/setup-scripts angstrom cd angstrom git checkout -b angstrom-v2013.06-yocto1.4 origin/angstrom-v2013.06-yocto1.4 ./oebb.sh setup beaglebone and then add/remove layers you want from conf/bblayers.conf etc. basically do customizations. you got me on wrong foot earlier ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Building Angstrom for Yocto 1.4 'Dylan'
On Tue, Nov 26, 2013 at 3:22 PM, Brandon Stafford bran...@rascalmicro.com wrote: Hi all, I'm trying to build Angstrom based on Yocto 1.4 'Dylan' for a SAMA5D3 board. I have modified bblayers.conf: BBLAYERS ?= \ /home/ubuntu/poky/meta-angstrom \ /home/ubuntu/poky/meta-openembedded/meta-oe \ /home/ubuntu/poky/meta-openembedded/meta-systemd \ /home/ubuntu/poky/meta-atmel \ /home/ubuntu/poky/meta \ /home/ubuntu/poky/meta-yocto \ /home/ubuntu/poky/meta-yocto-bsp \ I've also checked out what I believe to be the correct branches. Inside meta-openembedded: git checkout -b dylan origin/dylan Inside meta-angstrom: git checkout -b dylan origin/angstrom-v2013.06-yocto1.4 But the build fails with some missing recipes. bitbake core-image-minimal Loading cache: 100% |#| ETA: 00:00:00Loaded 1662 entries from dependency cache. NOTE: ['/home/ubuntu/poky/meta-angstrom/recipes-tweaks/gstreamer/gstreamer_0.10.36.bbappend'] to [] Parsing recipes: 100% |###| Time: 00:00:03Parsing of 1298 .bb files complete (1275 cached, 23 parsed). 1660 targets, 55 skipped, 0 masked, 0 errors. ERROR: No recipes available for: /home/ubuntu/poky/meta-angstrom/recipes-tweaks/libgnome/libgnome_2.32.1.bbappend /home/ubuntu/poky/meta-angstrom/recipes-core/systemd/systemd_206.bbappend /home/ubuntu/poky/meta-angstrom/recipes-tweaks/connman/connman_1.17.bbappend ERROR: Command execution failed: Exited with 1 When I inspect the directories where the files are missing, it looks like I'm asking for older files than I should be. For example, systemd_208.bbappend (but not systemd_206.bbappend) exists in recipes-core/systemd/: https://github.com/Angstrom-distribution/meta-angstrom/tree/angstrom-v2013.06-yocto1.4/recipes-core/systemd Can anyone see where I'm screwing up? yes. There was a merge problem. Please update meta-angstrom and retry this should take care of systemd and connman for libgnome you need to add meta-gnome to your bblayer mix as well. -- Brandon Stafford Rascal Micro: small computers for art and science Somerville, MA, USA ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ 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-toolchain cannot do static linking?
On Tue, Oct 29, 2013 at 7:59 PM, Grissiom chaos.pro...@gmail.com wrote: Hi all, I'm developing on BBB and I'm new to Angstrom. I have build a toolchain with the angstrom-v2013.06-yocto1.4 branch of setup-scripts ( https://github.com/Angstrom-distribution/setup-scripts/ ) using `bitbake meta-toolchain`. But when I want to use the toolchain to cross compile a program statically, I got an error: arm-angstrom-linux-gnueabi-gcc -std=gnu99 -static --sysroot=/home/grissiom/x-tools/angstrom-toolchain//sysroots/armv7ahf-vfp-neon-angstrom-linux-gnueabi tests/vbus_ser.c -o vbus_ser /home/grissiom/x-tools/angstrom-toolchain/sysroots/i686-angstromsdk-linux/usr/bin/armv7ahf-vfp-neon-angstrom-linux-gnueabi/../../libexec/armv7ahf-vfp-neon-angstrom-linux-gnueabi/gcc/arm-angstrom-linux-gnueabi/4.7.4/ld: cannot find -lc collect2: error: ld returned 1 exit status I could only find the libc.so in the sysroot but no libc.a. Is there anyway to let the toolchain install static libs? try adding IMAGE_FEATURES += staticdev-pkgs to local.conf and rebuild the SDK and see if that helps -- Cheers, Grissiom ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Looking for an Angstrom and bitbake expert to consult / contract
On Wed, Oct 23, 2013 at 3:42 PM, Edward Vidal vidal.devel...@gmail.com wrote: Hello Chris, I have been working with Yocto for beaglebone, beagleboard, pandaboard and now with the zedboard. I have tried angstrom but found yocto to be a better approach for me. I would like to emphasize that, Angstrom distribution is Yocto Project compatible and as the catchline for Yocto Project says, t's not an embedded Linux distribution – it creates a custom one for you Angstrom is one of those distributions. Now if you prefer Yocto Project's Reference Distribution and offer to customize it and create a distro for customer over something else thats fine however be clear about what you are trying to differentiate and even better why For the zedboard I need to linux systems a CentOSx6.4 x86_64 for the xilinx tools and a Fedora18x86_64 for yocto. I build my system with a liveDVD and with cobbler over the network. Are you knowledgeable in git, Linux kernel, and general Linux? What processor are you looking to build for? Is your application for a real time application or just embedded? With yocto you download the software and cross compile for you processor. You can call me at 915-595-1613 or 915-346-1476. I am located in El Paso Tex MST. My other e-mail is devel...@sbcglobal.net. If you want more information let me I can send my resume and cover letter. Regards On Wed, Oct 23, 2013 at 1:47 PM, Chris Morgan chmor...@gmail.com wrote: Hello. We are looking at using Angstrom and bitbake. There are several areas where we could use an expert that could both consult on questions and approaches as well as help implement some of the customization that we may need to ship product. This might start out as a several hour contract, phone or email consultation, and extend to a handful of weeks. We are located in the Boston area but remote is fine. If you might be interested please send me a short email letting me know what your rate would be, a little about your background and some way to get in touch. Chris ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Update Angstrom
On Thu, Oct 24, 2013 at 1:28 AM, M Pouillot m.pouil...@watteco.com wrote: Is there a command to update the file system Angstrom without lossing parameters system and application? what is it you are exactly looking for ? upgrading from which version of angstrom to which one best regards, Mathieu ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] what file kernel configuration really uses?
On Wed, Oct 23, 2013 at 3:07 AM, matti kaasinen matti.kaasi...@gmail.com wrote: Hi Ulf, Yes, linux.inc seems doing the job as you told - this clears a lot. I had been patching wrong file:${S}/defconfig instead of ${WORKDIR}/defconfig. It seems that I'm not alone with this mistake. ${S}/defconfig seems to be created by two patches: 0002-add-defconfig-file-to-use-as-.config.patch makes skeleton and 0073-defconfig-Update-bone-default-config.patch makes some modefications. ${WORKDIR}/defconfig (important one) is most likely coming from ./linux/linux-mainline-3.8/beaglebone/defconfig as there is only one difference that could have come from configuration process. It seems that configuration fragments do not work in regular Angstrom - I suppose they are just Yocto stuff. yes. Providing defconfig directly did not work - most likely it was written over by the patching the seems creating the ${WORKDIR}/defconfig what do you mean ? defconfig is provided as any other file and then munged over in WORKDIR to make a .config usually you would keep the complete defconfig in your layer and use it. You would start with the given reference defconfig and tweak it to your interest and then do make savedefconfig which should generate a defconfig like arch/arm/configs which then you can save as a defconfig file in your layer and use it to replace the defconfig file that meta-beagleboard is providing Downside is that my beaglebone version of defconfig seems to get used instead of mine even though my layer should have higher priority. I hope this is the last thing I should cleared. for conf and include files it will use the BBPATH and not priority which means your layer should appear before meta-beagleboard in BBPATH order. Thanks, Matti 2013/10/22 Ulf Samuelsson angstrom-...@emagii.com On 2013-10-22 17:20, matti kaasinen wrote: Thanks Ulf, It seems to work in that way. However, I'm a bit surprised that it works so as as I mentioned above all the procedures - patching defconfig in the kernel build directory, providing defconfig in metadata and providing configuration fragments as described in the Yocto Kernel development manual - give the same outcome in the defconfig at the kernel build directory. What is happening is dependent on the kernel recipe. Typically, you find that linux.inc does the job, and in do_configure, which is run when you do: bitbake -c configure virtual/kernel ${WORKDIR}/defconfig is altered to ensure it makes sense. A lot of options are simply deleted. ${S}/.config is created as an empty file and then the deleted options are added with a proper value. At the end, defconfig is appended to the ${S}/.config so when you run bitbake -c configure virtual/kernel both ${WORKDIR}/defconfig and ${S}/.config are changed. /Ulf What command do you use when you are using .config directly? My experience is that when I for instance run: bitbake -f -c configure virtual/kernel after bitbake -f -c patch virtual/kernel bitbake executes again do_patch, that at least rides over defconfig if I edited that. In fact it seems that bitbake -c config runs always do_patch even if previous command was patch and no modifications were in between. BR, Matti 2013/10/22 Ulf Samuelsson angstrom-...@emagii.com The defconfig file is present in the meta-layers and copied to the kernel build directory. It is used to create the .config file in the kernel source directory. If you modify the .config file, you will see changes in the kernel file. if you modify the defconfig file in the build directory, nothing happens. I typically change the .config and copy the result to the defconfig in the meta-layer. Then I rebuild from scratch. bitbake -c cleansstate virtual/kernel bitbake virtual/kernel Best Regards Ulf Samuelsson u...@emagii.com +46 (722) 427 437 22 okt 2013 kl. 14:04 skrev matti kaasinen matti.kaasi...@gmail.com: Hi! What configuration kernel build really uses - .config or defconfig? It seems, that menuconfig (bitbake -c menuconfig ) use always .config file. I have problem that changes in defconfig are not seen in kernel features. Instead they seem the same that are in .config file I have tried configuration fragments, patches and providing defconfig directly. They all seem to give proper defconfig. However, menuconfig never provide the changed configurations. Also, for instance when I try to configure HW EEC operation for NAND flash using CONFIG_MTD_NAND_OMAP_BCH. omap2.c reports that CONFIG_MTD_NAND_OMAP_BCH is not enabled. I've been workin on beaglebone variant - layer over beaglebone. Build Configuration: BB_VERSION= 1.17.0 TARGET_ARCH = arm TARGET_OS = linux-gnueabi MACHINE = beaglebone DISTRO= angstrom DISTRO_VERSION= v2012.12 TUNE_FEATURES = armv7a vfp neon cortexa8 TARGET_FPU= vfp-neon oe_sitecno oe_emergence =
Re: [Angstrom-devel] v2013.06 and v2013.12 architecture change for ARMv7A machines
On Sun, Oct 20, 2013 at 2:49 PM, Ulf Samuelsson angstrom-...@emagii.com wrote: 20 okt 2013 kl. 21:04 skrev Koen Kooi k...@dominion.thruhere.net: Hi, A while ago we decided to switch armv7a machines for hardfloat because we were worn it with explaining that there's no real world difference between softfp (which does use hw fp despite its name) and hardfp and silicon vendors started moving their evil binary only stuff to that as well. So we looked into it and set the DEFAULTTUNE to cortexa8hf-neon. That gave us a hardfp build and it had no regressions so far, so good. So how are Cortex-A5 chips without neon going to be handled? They are also armv7a! Been struggling with this, during the weekend, since some recipes assume hat if It is an arm7a, then Neon should be turned on. well then there is also Tegras and marvell stuff... we can not find a wholesome common denominator but we can find largest common denominator and thats the idea here. Best Regards Ulf Samuelsson u...@emagii.com Two weeks ago I switched jobs and had to dust off my pandaboards for the new job and that's were things starting going south. 'cortexa8hf-neon' didn't work since the buildsystem knew it was an cortex-A9 CPU, so 'cortexa9hf-neon' needed to be used. Again that built and worked. But it required two seperate feeds that were a single feed in v2012.12 and earlier. Then I started looking at cortex-A15 boards and realized this setup is wasting disk space and cpu time. Then I noticed that the 'genericarmv7a' machine in meta-linaro set the DEFAULTTUNE to armv7athf-neon. A MACHINE config shouldn't set that variable, but that's a different bug. It turns out that using that tune we can have a single feed again for all armv7a machines. Yay! If you have been using v2013.06 and your architecture for the feeds is cortexa*hf*, try doing the following: opkg update ; opkg install angstrom-feed-configs opkg update ; opkg install opkg-config-base That will update the feed configs to point to the new unified feed and drag in the /etc/opkg/arch.conf that lists the new armv7ahf-vfp-neon architecture as supported. It will throw a ton of warnings for the currently installed packages, but that's mostly harmless. Installing things from the feeds will work again, but it will try to reinstall a lot of things due to the architecture change. The v2013.12 feed will be cleaned up later, all the conferences will interfere with that. It looks like the complete angstrom cabal will be present at ELC-E in Edinburgh next week and at least 3 of us will also be attending Linaro Connect USA the week after that. If you're in the neighbourhood come say hello and please tell us about your pet peeve with angstrom or OE and we'll try to address it. thanks, Koen ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ 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-core] Using the correct xserver-xf86-config_0.1.bbappend
Ulf On Mon, Oct 21, 2013 at 9:30 AM, Ulf Samuelsson openembedded-c...@emagii.com wrote: Trying to build a systemd-gnome-image raspberrypi under Angstrom, with a few extra layers. This fails on xserver-xf86-config_0.1.[bb|bbappend] The extra layer has BBPRIORITY = 20. meta-beagleboard has BBPRIORITY = 8 meta-raspberrypi has BBPRIORITY = 6 (later changed to 120) BBLAYERS are in the order meta-extra layer meta-beagleboard meta-raspberrypi It looks like bitbake will select the bbappend in the layer with the highest priority, Not really. All bbappends are selected the order or sequence of them is governed by how the layers line up in BBPATH even if that contains a COMPATIBLE_MACHINE clause, which does not include the current MACHINE. Is there any way to make bitbake select the correct bbappend file without modifying the BBPRIORITY? Looks like the xserver-xf86-config for the raspberry-pi fails on SRC_URI_append_raspberrypi = file://xorg.conf.d/* When I change to: SRC_URI_append_raspberrypi = file://xorg.conf.d/10-evdev.conf the raspberry pi version completes. Wildcards are not allowed? This is a question of fundamental bitbake semantics/syntax for SRC_URI and nothing to do with bbappends. and I dont think wildcards in SRC_URI are reliable, so better be explicit about them. -- Best Regards Ulf Samuelsson eMagii ___ Openembedded-core mailing list openembedded-c...@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [PATCH] connman: follow oe-core to 1.18
To late see https://github.com/Angstrom-distribution/meta-angstrom/commit/ad9e6f5a6c9a38d07dde6a601523f152c8069551 On Oct 16, 2013, at 2:20 PM, Andreas Müller schnitzelt...@googlemail.com wrote: Signed-off-by: Andreas Müller schnitzelt...@googlemail.com --- recipes-tweaks/connman/{connman_1.17.bbappend = connman_1.18.bbappend} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename recipes-tweaks/connman/{connman_1.17.bbappend = connman_1.18.bbappend} (100%) diff --git a/recipes-tweaks/connman/connman_1.17.bbappend b/recipes-tweaks/connman/connman_1.18.bbappend similarity index 100% rename from recipes-tweaks/connman/connman_1.17.bbappend rename to recipes-tweaks/connman/connman_1.18.bbappend -- 1.8.3.1 ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Angstrom v2013-06 with -mfloat-abi=softfp
On Oct 14, 2013, at 12:55 PM, Diego Sueiro diego.sue...@gmail.com wrote: Thanks Khem, Using softfloat, Am I able to install the packages from Angstrom feeds? If you do not tweak the defaults then yes. Otherwise, no. soft-fp feeds are not compatible with hardfp Abraços, -- *dS Diego Sueiro Administrador do Embarcados www.embarcados.com.br Engenheiro de Controle e Automação UNIVERSIDADE FEDERAL DE ITAJUBÀ /*long live rock 'n roll*/ 2013/10/14 Khem Raj raj.k...@gmail.com On Oct 14, 2013, at 11:38 AM, Diego Sueiro diego.sue...@gmail.com wrote: Folks, I want to generate an Angstrom distribution with soft and hard float point compatible ABI. Reading the page below I believe that I must compile the packages with -mfloat-abi=softfp option. Is it correct? https://wiki.debian.org/ArmHardFloatPort To achieve this, I think I have to change the file meta-angstrom/conf/distro/include/arm-defaults.inc to: DEFAULTTUNE_beaglebone = cortexa8hf-vfp or DEFAULTTUNE_beaglebone = cortexa8hf-vfp-neon Place it right. change is wrong. Defaults are to build for hardfloat, in angstrom now as you see if you want to change it to use softfloat then you would change it to DEFAULTTUNE_beaglebone = cortexa8-neon ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ 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-core] Problems when building Angstrom master 1.3 1.4 for Beagleboard Black
On Oct 11, 2013, at 8:33 AM, Ulf Samuelsson angstrom-...@emagii.com wrote: On 2013-10-11 16:58, Koen Kooi wrote: Op 11 okt. 2013, om 16:32 heeft Ulf Samuelsson angstrom-...@emagii.com het volgende geschreven: Have tried out building Angstrom for Beaglebone Black on a Quad-Core i7/Ubuntu 12.04 i386 with: I strongly recommend ditching ubuntu and installing linux instead. I don't know what causes it, but switching to debian, arch, gentoo, fedora, opensuse or anything else not ubuntu based gets rid off all problems with builds not working, not booting, etc. OK, after installing 12.04LTS I have to 1. left-click (hold) 2. alt (hold) 3. right click just to add an item to the panel, I guess they are trying to prove that Ubuntu One is superior to gnome, by making gnome successively worse. so I am quite pissed of with Ubuntu Getting a dual Xeon 6-core next week, so I'll wait until then, but that is not going to be exposed to Ubuntu ever… What is your default shell ? I would recomment to use bash. BR Ulf PARALLEL_MAKE = -j8 BB_NUMBER_THREADS = 8 I bitbake cloud9-gnome-image RESULTS: * remotes/origin/angstrom-v2013.06-yocto1.4commit 246357a1cc4977683ada564d38218e837ac615e3 image builds but does not boot. * remotes/origin/angstrom-v2012.12-yocto1.3commit 01984cc460acfe5e7d5bab4feeb0888d5c6fe77f image builds but does not boot. * origin/master commit 7a3b004f7bfa24ea54b0da78bd80e4dd7839321d Build fails on two issues. 1.libxklavier compile fails. | xklavier.c: In function 'xkl_engine_class_init': | xklavier.c:846:8: error: 'XKL_TYPE_ENGINE_FEATURES' undeclared (first use in this function) ... Summary: 1 task failed: /home/ulf/projects/ICU/Angstrom/setup-scripts/sources/meta-openembedded/meta-gnome/recipes-gnome/libxklavier/libxklavier_5.0.bb, do_compile Did bitbake -c cleansstate libxklavier and restarted, and then it continued without problem, so there seem to be a dependency problem. 2.nodejs compiles fails with error: | arm-angstrom-linux-gnueabi-gcc -march=armv7-a -mthumb-interwork -mfloat-abi=softfp -mfpu=neon -mtune=cortex-a8 --sysroot=/home/ulf/projects/ICU/Angstrom/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/sysroots/beaglebone '-D_LARGEFILE_SOURCE' '-D_FILE_OFFSET_BITS=64' '-DL_ENDIAN' '-DOPENSSL_THREADS' '-DPURIFY' '-D_REENTRANT' '-DOPENSSL_NO_DTLS1' '-DOPENSSL_NO_SOCK' '-DOPENSSL_NO_DGRAM' '-DOPENSSL_NO_GOST' '-DOPENSSL_NO_HW_PADLOCK' '-DOPENSSL_NO_ASM' '-DENGINESDIR=/dev/null' '-DOPENSSLDIR=/etc/ssl' '-DTERMIOS' -I../deps/openssl -I../deps/openssl/openssl -I../deps/openssl/openssl/crypto -I../deps/openssl/openssl/crypto/asn1 -I../deps/openssl/openssl/crypto/evp -I../deps/openssl/openssl/crypto/store -I../deps/openssl/openssl/include -I../deps/openssl/config/android -Wall -pthread -O2 -fno-strict-aliasing -fno-tree-vrp -MMD -MF /home/ulf/projects/ICU/Angstrom/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/work/armv7a-vfp-neon-angstrom-linux-gnueabi/node js-0.8.22-r0/node-v0.8.22/out/Release/.deps//home/ulf/projects/ICU/Angstrom/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/work/armv7a-vfp-neon-angstrom-linux-gnueabi/nodejs-0.8.22-r0/node-v0.8.22/out/Release/obj.target/openssl/deps/openssl/openssl/crypto/whrlpool/wp_block.o.d.raw -O2 -pipe -g -feliminate-unused-debug-types -c -o /home/ulf/projects/ICU/Angstrom/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/work/armv7a-vfp-neon-angstrom-linux-gnueabi/nodejs-0.8.22-r0/node-v0.8.22/out/Release/obj.target/openssl/deps/openssl/openssl/crypto/whrlpool/wp_block.o ../deps/openssl/openssl/crypto/whrlpool/wp_block.c | make[1]: execvp: printf: Argument list too long I get the second problem when I run from: /home/ulf/projects/ICU/Angstrom/setup-scripts/ When I install Angstrom in /home/icu/v2012.12 I do not see the problem. --- Have tried recompiling my kernel changing include/linux/binfmts.h # define MAX_ARG_PAGES32 # define MAX_ARG_PAGES64 based on something I found on Internet, to no avail. Checking a little bit more, I see it looks like: #ifdef CONFIG_MMU ... #else # define MAX_ARG_PAGES64 struct page *page[MAX_ARG_PAGES]; #endif CONFIG_MMU is set, so the change is in part of the code which is not used Maybe there should be some kind of warning about how deep in the directory structure Angstrom can be. --- The resulting kernel/filesystem will run on the Beagleboard Black. Anyone knows what to change to increase the argument area on linux-3.2.x? BR Ulf Samuelsson ___ Openembedded-core mailing list openembedded-c...@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [Angstrom-devel] Angstrom v2013-06 with -mfloat-abi=softfp
On Oct 14, 2013, at 11:38 AM, Diego Sueiro diego.sue...@gmail.com wrote: Folks, I want to generate an Angstrom distribution with soft and hard float point compatible ABI. Reading the page below I believe that I must compile the packages with -mfloat-abi=softfp option. Is it correct? https://wiki.debian.org/ArmHardFloatPort To achieve this, I think I have to change the file meta-angstrom/conf/distro/include/arm-defaults.inc to: DEFAULTTUNE_beaglebone = cortexa8hf-vfp or DEFAULTTUNE_beaglebone = cortexa8hf-vfp-neon Place it right. change is wrong. Defaults are to build for hardfloat, in angstrom now as you see if you want to change it to use softfloat then you would change it to DEFAULTTUNE_beaglebone = cortexa8-neon ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Angstrom v2013.12 branched
On Oct 9, 2013, at 11:12 PM, Koen Kooi k...@dominion.thruhere.net wrote: Op 9 okt. 2013, om 17:29 heeft Khem Raj raj.k...@gmail.com het volgende geschreven: On Oct 9, 2013, at 12:09 AM, Koen Kooi k...@dominion.thruhere.net wrote: All, The Angstrom v2013.12 release branch was opened today. This release will match the Yocto Project 1.5 release. Patches are very welcome, but keep in mind that it's not ready for consumption till the official release point in december. I would like to turn on gold as default linker, if people think its too late then we can skip it for 2013.12 I have no strong opinion on that. There will be a lot of toolchain changes (for ARM based platforms) before the release because we'll be tracking meta-linaro closely. OK, are we going to change defaults for ARM architecture to track meta-linaro as well or provide it as an integral easily switchable option. ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Angstrom v2013.12 branched
On Oct 9, 2013, at 12:09 AM, Koen Kooi k...@dominion.thruhere.net wrote: All, The Angstrom v2013.12 release branch was opened today. This release will match the Yocto Project 1.5 release. Patches are very welcome, but keep in mind that it's not ready for consumption till the official release point in december. I would like to turn on gold as default linker, if people think its too late then we can skip it for 2013.12 regards, Koen ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Angstrom v2013.12 branched
On Oct 9, 2013, at 9:06 AM, Philip Balister phi...@balister.org wrote: On 10/09/2013 11:29 AM, Khem Raj wrote: On Oct 9, 2013, at 12:09 AM, Koen Kooi k...@dominion.thruhere.net wrote: All, The Angstrom v2013.12 release branch was opened today. This release will match the Yocto Project 1.5 release. Patches are very welcome, but keep in mind that it's not ready for consumption till the official release point in december. I would like to turn on gold as default linker, if people think its too late then we can skip it for 2013.12 I'd like to stay as close to 1.5 as possible. I'm assuming 1.5 does not use gold as a default? Yes oe-core and poky both don't yet use gold as default distro feature. However angstrom ecosystem builds more of those large applications more than anyone else in OE ecosystem where using gold would be an advantage ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Error building angstrom 2013.06 for raspberry pi
On Aug 27, 2013, at 4:34 AM, Cristian Astorino cristian.astor...@gmail.com wrote: I solved by installing uuid devel package on my system (ubuntu 12.04.3 lts) hmmm, I think this means we either need to mention it in prerequisites or add a recipe for uuidgen-native ___ 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] angstrom-next: add versions to build for aarch64
On Aug 20, 2013, at 1:45 AM, Koen Kooi k...@dominion.thruhere.net wrote: Op 15 aug. 2013, om 12:21 heeft Graeme Gregory g...@slimlogic.co.uk het volgende geschreven: aarch64 needs gcc and egibc from meta-linaro to build for now. Signed-off-by: Graeme Gregory g...@slimlogic.co.uk Acked-by: Koen Kooi k...@dominion.thruhere.net --- conf/distro/angstrom-next.conf |5 + 1 file changed, 5 insertions(+) diff --git a/conf/distro/angstrom-next.conf b/conf/distro/angstrom-next.conf index a1bedbb..7dd57cd 100644 --- a/conf/distro/angstrom-next.conf +++ b/conf/distro/angstrom-next.conf @@ -63,6 +63,11 @@ ANGSTROM_GCC_VERSION_bfin = 4.1.2 #avr32 only has support for gcc 4.2.2 ANGSTROM_GCC_VERSION_avr32?= 4.2.2 +#aarch64 needs linaro tools +ANGSTROM_GCC_VERSION_aarch64 ?= linaro-4.7% +PREFERRED_VERSION_eglibc_aarch64 ?= 2.17 +PREFERRED_VERSION_eglibc-initial_aarch64 ?= 2.17 + #Everybody else can just use this: ANGSTROM_GCC_VERSION ?= 4.8% I have installed this patch. However I would really like to see if we could use gcc 4.8 and eglibc 2.18 for aarch64 as well. Since I had plans to deprecate eglibc 2.17 from OE-Core into meta-toolchain layer ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] angstrom world build
Hi I have started a world build of angstrom for beaglebone and soon will extend it to more machines. Angstrom uses most layers in OE universe and nothing gives better coverage The wold log for bb is here http://sakrah.homelinux.org/files/world/beaglebone-world.log There are interesting failures. Feel free to peruse and lets fix them all ! -Khem ___ 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] angstrom-next: add versions to build for aarch64
On Sat, Aug 17, 2013 at 8:16 AM, Graeme Gregory g...@slimlogic.co.uk wrote: On Fri, Aug 16, 2013 at 12:30:09PM -0700, Khem Raj wrote: On Fri, Aug 16, 2013 at 2:44 AM, Graeme Gregory g...@slimlogic.co.uk wrote: aarch64 needs gcc and egibc from meta-linaro to build for now. Signed-off-by: Graeme Gregory g...@slimlogic.co.uk --- conf/distro/angstrom-next.conf |5 + 1 file changed, 5 insertions(+) diff --git a/conf/distro/angstrom-next.conf b/conf/distro/angstrom-next.conf index a1bedbb..7dd57cd 100644 --- a/conf/distro/angstrom-next.conf +++ b/conf/distro/angstrom-next.conf @@ -63,6 +63,11 @@ ANGSTROM_GCC_VERSION_bfin= 4.1.2 #avr32 only has support for gcc 4.2.2 ANGSTROM_GCC_VERSION_avr32 ?= 4.2.2 +#aarch64 needs linaro tools +ANGSTROM_GCC_VERSION_aarch64 ?= linaro-4.7% +PREFERRED_VERSION_eglibc_aarch64 ?= 2.17 +PREFERRED_VERSION_eglibc-initial_aarch64 ?= 2.17 + #Everybody else can just use this: ANGSTROM_GCC_VERSION ?= 4.8% what does gcc 4.8 and eglibc 2.18 does not work ? eglibc 2.18 should support aarch64 gcc 4.8 both linaro and OE were unbuildable for arm64 when I tried. hmm interesting. I would be interested to know the failures, did you report them to OE-Core ml ? if not please do eglibc 2.18 produces bogus executeables for arm64. Thats interesting since the sole reason we were hung on release glibc 2.18 were some fixes needed for aarch64 so I think it should work better. We havent yet created eglibc 2.18 branch but when we do I will refresh the recipes to use them. As arm64 developer I will monitor situation regularly and update these when stuff becomes working. OK. Please do. Graeme ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [PATCH] angstrom-next: add versions to build for aarch64
Graeme On Tue, Aug 13, 2013 at 2:29 AM, Graeme Gregory g...@slimlogic.co.uk wrote: aarch64 needs gcc and egibc from meta-linaro to build for now. Signed-off-by: Graeme Gregory g...@slimlogic.co.uk --- conf/distro/angstrom-next.conf |4 1 file changed, 4 insertions(+) diff --git a/conf/distro/angstrom-next.conf b/conf/distro/angstrom-next.conf index a1bedbb..c7d8353 100644 --- a/conf/distro/angstrom-next.conf +++ b/conf/distro/angstrom-next.conf @@ -63,6 +63,10 @@ ANGSTROM_GCC_VERSION_bfin= 4.1.2 #avr32 only has support for gcc 4.2.2 ANGSTROM_GCC_VERSION_avr32 ?= 4.2.2 +#aarch64 needs linaro tools +ANGSTROM_GCC_VERSION_aarch64 ?= linaro-4.7% +PREFERRED_VERSION_eglibc_aarch64 ?= 2.17 + even with gcc 4.8 and eglibc 2.18? #Everybody else can just use this: ANGSTROM_GCC_VERSION ?= 4.8% -- 1.7.10.4 ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ 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] angstrom-next: add versions to build for aarch64
On Fri, Aug 16, 2013 at 2:44 AM, Graeme Gregory g...@slimlogic.co.uk wrote: aarch64 needs gcc and egibc from meta-linaro to build for now. Signed-off-by: Graeme Gregory g...@slimlogic.co.uk --- conf/distro/angstrom-next.conf |5 + 1 file changed, 5 insertions(+) diff --git a/conf/distro/angstrom-next.conf b/conf/distro/angstrom-next.conf index a1bedbb..7dd57cd 100644 --- a/conf/distro/angstrom-next.conf +++ b/conf/distro/angstrom-next.conf @@ -63,6 +63,11 @@ ANGSTROM_GCC_VERSION_bfin= 4.1.2 #avr32 only has support for gcc 4.2.2 ANGSTROM_GCC_VERSION_avr32 ?= 4.2.2 +#aarch64 needs linaro tools +ANGSTROM_GCC_VERSION_aarch64 ?= linaro-4.7% +PREFERRED_VERSION_eglibc_aarch64 ?= 2.17 +PREFERRED_VERSION_eglibc-initial_aarch64 ?= 2.17 + #Everybody else can just use this: ANGSTROM_GCC_VERSION ?= 4.8% what does gcc 4.8 and eglibc 2.18 does not work ? eglibc 2.18 should support aarch64 ___ 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-core] boost recipe, fatal error: zlib.h
On Thu, Aug 15, 2013 at 2:28 AM, Víctor MV v.mayor...@gmail.com wrote: Hi, I'm getting an error when trying to bitbake the *boost* recipe: ... | gcc.compile.c++ bin.v2/libs/iostreams/build/gcc-4.3.1/release/threading-multi/zlib.o | libs/iostreams/src/zlib.cpp:20:76: fatal error: zlib.h: No such file or directory | compilation terminated. | You need to install zlib-dev either on your host or add zlib to DEPENDS list in boost recipe | g++ -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -fPIC -DBOOST_ALL_NO_LIB=1 -DBOOST_IOSTREAMS_DYN_LINK=1 -DBOOST_IOSTREAMS_USE_DEPRECATED -DNDEBUG -I. -c -o bin.v2/libs/iostreams/build/gcc-4.3.1/release/threading-multi/zlib.o libs/iostreams/src/zlib.cpp | | ...failed gcc.compile.c++ bin.v2/libs/iostreams/build/gcc-4.3.1/release/threading-multi/zlib.o... | ...skipped pbin.v2/libs/iostreams/build/gcc-4.3.1/release/threading-multilibboost_iostreams.so.1.53.0 for lack of pbin.v2/libs/iostreams/build/gcc-4.3.1/release/threading-multizlib.o... | ...skipped pstage/liblibboost_iostreams.so.1.53.0 for lack of pbin.v2/libs/iostreams/build/gcc-4.3.1/release/threading-multilibboost_iostreams.so.1.53.0... | ...skipped pstage/liblibboost_iostreams.so for lack of pstage/liblibboost_iostreams.so.1.53.0... | gcc.compile.c++ bin.v2/libs/iostreams/build/gcc-4.3.1/release/link-static/threading-multi/zlib.o | libs/iostreams/src/zlib.cpp:20:76: fatal error: zlib.h: No such file or directory | compilation terminated. | | g++ -ftemplate-depth-128 -O3 -finline-functions -Wno-inline -Wall -pthread -DBOOST_ALL_NO_LIB=1 -DBOOST_IOSTREAMS_USE_DEPRECATED -DNDEBUG -I. -c -o bin.v2/libs/iostreams/build/gcc-4.3.1/release/link-static/threading-multi/zlib.o libs/iostreams/src/zlib.cpp | | ...failed gcc.compile.c++ bin.v2/libs/iostreams/build/gcc-4.3.1/release/link-static/threading-multi/zlib.o... | ...skipped pbin.v2/libs/iostreams/build/gcc-4.3.1/release/link-static/threading-multilibboost_iostreams.a(clean) for lack of pbin.v2/libs/iostreams/build/gcc-4.3.1/release/link-static/threading-multizlib.o... | ...skipped pbin.v2/libs/iostreams/build/gcc-4.3.1/release/link-static/threading-multilibboost_iostreams.a for lack of pbin.v2/libs/iostreams/build/gcc-4.3.1/release/link-static/threading-multizlib.o... | ...skipped pstage/liblibboost_iostreams.a for lack of pbin.v2/libs/iostreams/build/gcc-4.3.1/release/link-static/threading-multilibboost_iostreams.a... | ...failed updating 2 targets... | ...skipped 6 targets... | ERROR: Function failed: do_compile (see /home/victor/setup-scripts/build/tmp-angstrom_v2012_12-eglibc/work/i686-linux/boost-native-1.53.0-r1/temp/log.do_compile.2901 for further information) ERROR: Task 7 (virtual:native:/home/victor/setup-scripts/sources/openembedded-core/meta/recipes-support/boost/ boost_1.53.0.bb, do_compile) failed with exit code '1' Regards, Víctor. ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Strategies for freezing and building Angstrom offline?
On Jun 28, 2013, at 11:21 AM, Charles Nicholson charles.nichol...@gmail.com wrote: Hi all, First off, thanks a lot for the Angstrom effort, it's a great distro and we're committing to use it on BeagleBone Blacks to manage our automated test rack at work. We are trying to figure out the best way to capture a full Angstrom codebase snapshot so that we can iterate locally on it and make private changes. I see that invoking bitbake virtual/kernel performs an update before doing a build, so our current strategy is failing. bitbake -cfetchall yourimage will download the needed sources and then you can add BB_NO_NETWORK = 1 to you local.conf from thereon it will not access web anymore My naive first attempt to capture Angstrom was to pull it down and do a full build as per the instructions on the Angstrom site. After confirming that this gave me a good output image, I deleted the entire /build directory, and then recursively deleted the .git metadata (find . -type d -name .git -exec rm -rf {}\;). I committed the results to our local private git repository. When our build slave machine tries to sync and build, it gives us this: MACHINE=beaglebone ./oebb.sh bitbake console-image dont se oebb.sh wrapper to run builds once you have create the sandbox. using oebb.sh config then source ~/.oe/angstrom-* in your shell and after that issue normal bitbake commands directly bitbake sytemd-image and so on and once everything works for you. Contributions are welcome col: write error grotty:standard input (standard input):25092:fatal error: output error WARNING WARNING: bitbake is using a different uri 'g...@git.mycompany.com:hardware/bbb-angstrom.git' than configured in layers.txt 'git://github.com/openembedded/bitbake.git' WARNING: Changing uri to: 'git://github.com/openembedded/bitbake.git' WARNING Fetching origin This makes sense, because the conf/layers.txt file references all of the subprojects on the public github. Can I tell bitbake to use the local versions? Do I need to host each subproject on our internal git and point layers.txt towards that? Is what I'm doing sensible? :) All advice, comments, flames welcome, and thanks for taking the time to read this. Best Regards, Charles Nicholson ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Strategies for freezing and building Angstrom offline?
On Jun 29, 2013, at 11:17 AM, Charles Nicholson charles.nichol...@gmail.com wrote: Thanks everyone for the quick response. Once we get things working, I'd be happy to contribute a page to the wiki about how to freeze and build Angstrom locally without further updates, if people think that would be helpful. (BTW, the build machine in question has no access to the outside internet, which might also be contributing to the errors I'm seeing? All git commands against github etc. fail…) We strive to make it such that it doesn't have to enquire once you download. So when you see that some recipe is trying to query the sources from www you should check if it has SRCREV set to a hardcoded git SHA sometimes it might have tagnames or AUTOREV assigned to SRCREV that will need to be changed to specific git commit SHAs So that can be your first contribution. Best, and thanks again, Charles On Sat, Jun 29, 2013 at 7:17 AM, Khem Raj raj.k...@gmail.com wrote: On Jun 28, 2013, at 11:21 AM, Charles Nicholson charles.nichol...@gmail.com wrote: Hi all, First off, thanks a lot for the Angstrom effort, it's a great distro and we're committing to use it on BeagleBone Blacks to manage our automated test rack at work. We are trying to figure out the best way to capture a full Angstrom codebase snapshot so that we can iterate locally on it and make private changes. I see that invoking bitbake virtual/kernel performs an update before doing a build, so our current strategy is failing. bitbake -cfetchall yourimage will download the needed sources and then you can add BB_NO_NETWORK = 1 to you local.conf from thereon it will not access web anymore My naive first attempt to capture Angstrom was to pull it down and do a full build as per the instructions on the Angstrom site. After confirming that this gave me a good output image, I deleted the entire /build directory, and then recursively deleted the .git metadata (find . -type d -name .git -exec rm -rf {}\;). I committed the results to our local private git repository. When our build slave machine tries to sync and build, it gives us this: MACHINE=beaglebone ./oebb.sh bitbake console-image dont se oebb.sh wrapper to run builds once you have create the sandbox. using oebb.sh config then source ~/.oe/angstrom-* in your shell and after that issue normal bitbake commands directly bitbake sytemd-image and so on and once everything works for you. Contributions are welcome col: write error grotty:standard input (standard input):25092:fatal error: output error WARNING WARNING: bitbake is using a different uri 'g...@git.mycompany.com:hardware/bbb-angstrom.git' than configured in layers.txt 'git://github.com/openembedded/bitbake.git' WARNING: Changing uri to: 'git://github.com/openembedded/bitbake.git' WARNING Fetching origin This makes sense, because the conf/layers.txt file references all of the subprojects on the public github. Can I tell bitbake to use the local versions? Do I need to host each subproject on our internal git and point layers.txt towards that? Is what I'm doing sensible? :) All advice, comments, flames welcome, and thanks for taking the time to read this. Best Regards, Charles Nicholson ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [PATCH] set default tune for Overo to cortexa8hf-neon
On May 28, 2013, at 10:42 PM, Andreas Müller schnitzelt...@googlemail.com wrote: On Wed, May 29, 2013 at 3:20 AM, Khem Raj raj.k...@gmail.com wrote: On May 26, 2013, at 2:41 PM, Khem Raj raj.k...@gmail.com wrote: On Thu, May 23, 2013 at 12:36 AM, Andreas Müller schnitzelt...@googlemail.com wrote: On Thu, May 23, 2013 at 9:17 AM, Khem Raj raj.k...@gmail.com wrote: On May 22, 2013, at 8:16 AM, Cliff Brake cbr...@bec-systems.com wrote: there is a missing DEPENDS to gconf. After I built gconf, I get: https://gist.github.com/cbrake/5628386 well I think this here http://src.chromium.org/viewvc/chrome?revision=135388view=revision Thanks for the hint - I will look into that (am working on chrome anyway - for gcc 4.8 fix). Still I would like to have tests on my images with hardfp before applying - I don't want to open another WIP with unpredictable efforts. Please test out. http://patchwork.openembedded.org/patch/50553/ http://patchwork.openembedded.org/patch/50555/ I have compile tested the new chromium v29 recipe on hardfp/beaglebone/gcc-4.8 may be we should get rid of older chromium recipes in there but that can be done once v29 works out ok. Let me know if you run into issues. Andreas, Cliff Now that above patches are applied to meta-browser, can one of you test out the hardfp build on overo ? I don't have hardware myself to try it out. I would like to pull the above patch in question into angstrom. I have run tested most of my images with this patch applied - I don't see any issues. Especially chromium 29.x builds (also for gcc 4.8) and runs fine - thanks for taking care. The only issue I see after this patch is broken TI's libgles. Since this is useless for many years anyway (just running demos at predefined size and 'mouse eating' is not what I expect when I ask for gles/egl support), we can take this patch in. I don't expect a working gles support from TI anyway. Thanks, patch is installed. ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [PATCH] oebb.sh: grep for word DISTRO
On May 28, 2013, at 1:34 PM, Eric Bénard e...@eukrea.com wrote: so that the DISTRO variable won't be wrongly assigned if, for example, local.conf contains DISTRO_FEATURES Signed-off-by: Eric Bénard e...@eukrea.com pulled into next branch Thx --- oebb.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/oebb.sh b/oebb.sh index a4ffb0a..ac50719 100755 --- a/oebb.sh +++ b/oebb.sh @@ -120,7 +120,7 @@ else #-- # Specify distribution information #-- -DISTRO=$(grep DISTRO conf/local.conf | grep -v '^#' | awk -F\ '{print $2}') +DISTRO=$(grep -w DISTRO conf/local.conf | grep -v '^#' | awk -F\ '{print $2}') DISTRO_DIRNAME=`echo $DISTRO | sed s#[.-]#_#g` echo export SCRIPTS_BASE_VERSION=${BASE_VERSION} ${OE_ENV_FILE} -- 1.8.1.4 ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [PATCH] set default tune for Overo to cortexa8hf-neon
On May 26, 2013, at 2:41 PM, Khem Raj raj.k...@gmail.com wrote: On Thu, May 23, 2013 at 12:36 AM, Andreas Müller schnitzelt...@googlemail.com wrote: On Thu, May 23, 2013 at 9:17 AM, Khem Raj raj.k...@gmail.com wrote: On May 22, 2013, at 8:16 AM, Cliff Brake cbr...@bec-systems.com wrote: there is a missing DEPENDS to gconf. After I built gconf, I get: https://gist.github.com/cbrake/5628386 well I think this here http://src.chromium.org/viewvc/chrome?revision=135388view=revision Thanks for the hint - I will look into that (am working on chrome anyway - for gcc 4.8 fix). Still I would like to have tests on my images with hardfp before applying - I don't want to open another WIP with unpredictable efforts. Please test out. http://patchwork.openembedded.org/patch/50553/ http://patchwork.openembedded.org/patch/50555/ I have compile tested the new chromium v29 recipe on hardfp/beaglebone/gcc-4.8 may be we should get rid of older chromium recipes in there but that can be done once v29 works out ok. Let me know if you run into issues. Andreas, Cliff Now that above patches are applied to meta-browser, can one of you test out the hardfp build on overo ? I don't have hardware myself to try it out. I would like to pull the above patch in question into angstrom. -Khem ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [PATCH] set default tune for Overo to cortexa8hf-neon
On Thu, May 23, 2013 at 12:36 AM, Andreas Müller schnitzelt...@googlemail.com wrote: On Thu, May 23, 2013 at 9:17 AM, Khem Raj raj.k...@gmail.com wrote: On May 22, 2013, at 8:16 AM, Cliff Brake cbr...@bec-systems.com wrote: there is a missing DEPENDS to gconf. After I built gconf, I get: https://gist.github.com/cbrake/5628386 well I think this here http://src.chromium.org/viewvc/chrome?revision=135388view=revision Thanks for the hint - I will look into that (am working on chrome anyway - for gcc 4.8 fix). Still I would like to have tests on my images with hardfp before applying - I don't want to open another WIP with unpredictable efforts. Please test out. http://patchwork.openembedded.org/patch/50553/ http://patchwork.openembedded.org/patch/50555/ I have compile tested the new chromium v29 recipe on hardfp/beaglebone/gcc-4.8 may be we should get rid of older chromium recipes in there but that can be done once v29 works out ok. Let me know if you run into issues. ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] [PATCH] set default tune for Overo to cortexa8hf-neon
On May 22, 2013, at 8:16 AM, Cliff Brake cbr...@bec-systems.com wrote: there is a missing DEPENDS to gconf. After I built gconf, I get: https://gist.github.com/cbrake/5628386 well I think this here http://src.chromium.org/viewvc/chrome?revision=135388view=revision should have fixed it. it should be fixed in recipe how float ABI is passed to chromium build Thanks, Cliff On Wed, May 22, 2013 at 10:44 AM, Andreas Müller schnitzelt...@googlemail.com wrote: On Wed, May 22, 2013 at 4:37 PM, Cliff Brake cliff.br...@gmail.com wrote: From: Cliff Brake cbr...@bec-systems.com Signed-off-by: Cliff Brake cbr...@bec-systems.com --- conf/distro/include/arm-defaults.inc | 1 + 1 file changed, 1 insertion(+) diff --git a/conf/distro/include/arm-defaults.inc b/conf/distro/include/arm-defaults.inc index 6e29332..89ed530 100644 --- a/conf/distro/include/arm-defaults.inc +++ b/conf/distro/include/arm-defaults.inc @@ -1,2 +1,3 @@ DEFAULTTUNE_beagleboard = cortexa8hf-neon DEFAULTTUNE_beaglebone = cortexa8hf-neon +DEFAULTTUNE_overo = cortexa8hf-neon -- 1.8.2.3 I got the information (never tested by myself) that hardfp causes chromium build to fail. Can you test that, because I would like to keep that working. Andreas ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] world build on angstrom-next
Hi All I have run world build on angstrom and here are results if anyone is interested and provide fixes. http://sakrah.dontexist.org/files/eglibc.beaglebone.world.log There are a lot of parsing errors especially from meta-opie Thanks -Khem ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] world build on angstrom-next
On May 21, 2013, at 12:24 PM, Ankit Mishra mishr...@gmail.com wrote: Please remove me from the mail list for angstrom. go here http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel and help yourself Thank you On May 21, 2013 11:48 PM, Khem Raj raj.k...@gmail.com wrote: Hi All I have run world build on angstrom and here are results if anyone is interested and provide fixes. http://sakrah.dontexist.org/files/eglibc.beaglebone.world.log There are a lot of parsing errors especially from meta-opie Thanks -Khem ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ 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] world build on angstrom-next
On May 21, 2013, at 12:47 PM, Andreas Müller schnitzelt...@googlemail.com wrote: I was also wondering of the passed chromium in the last logs you sent. Was this build performed with gcc 4.8 - or was there an update fixing builds with gcc 4.8 which I have missed? yes gcc 4.8 and no local patches to chromium ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] world build on angstrom-next
On May 21, 2013, at 12:24 PM, Ankit Mishra mishr...@gmail.com wrote: Please remove me from the mail list for angstrom. go here http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel and help yourself Thank you On May 21, 2013 11:48 PM, Khem Raj raj.k...@gmail.com wrote: Hi All I have run world build on angstrom and here are results if anyone is interested and provide fixes. http://sakrah.dontexist.org/files/eglibc.beaglebone.world.log There are a lot of parsing errors especially from meta-opie Thanks -Khem ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ 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-core] gcc-cross-initial Failure (is a meta-aarch64 screw up)
Hi Jack since I was playing with archlinux today, I could reproduce this gcc ICE problem with angstrom. Actual issue has been already fixed with http://git.openembedded.org/openembedded-core/commit/?id=b1dc91969f9bb0c2a3a4336f5e9a2f57aabb9f78 but it was still failing on angstrom/cortex-a8-hf and it took some time to realize that angstrom is including meta-aarch64 layer and it has totally totally screwed up the toolchain build since this layer forked the .inc files from oe-core gcc at some point and never did kept them in sync with OE-Core it meant that even when I wanted to use gcc 4.7 from OE-Core it was picking .incs from meta-aarch64 and the patch which was applied to OE-Core recently has been ignored and hence the gcc ICE meta-aarch64 has $ find . -name *.inc ./recipes-devtools/binutils/binutils-cross-canadian.inc ./recipes-devtools/binutils/binutils-git.inc ./recipes-devtools/binutils/binutils-cross.inc ./recipes-devtools/binutils/binutils.inc ./recipes-devtools/gcc/gcc-crosssdk-initial.inc ./recipes-devtools/gcc/gcc-common.inc ./recipes-devtools/gcc/gcc-configure-common.inc ./recipes-devtools/gcc/gcc-cross4.inc ./recipes-devtools/gcc/gcc-cross-canadian.inc ./recipes-devtools/gcc/gcc-cross-initial.inc ./recipes-devtools/gcc/gcc-package-sdk.inc ./recipes-devtools/gcc/gcc-package-runtime.inc ./recipes-devtools/gcc/gcc-package-target.inc ./recipes-devtools/gcc/gcc-crosssdk.inc ./recipes-devtools/gcc/gcc-4.7.inc ./recipes-devtools/gcc/gcc-configure-sdk.inc ./recipes-devtools/gcc/gcc-configure-runtime.inc ./recipes-devtools/gcc/gcc-configure-cross.inc ./recipes-devtools/gcc/gcc-package-cross.inc ./recipes-devtools/gcc/gcc-cross.inc ./recipes-devtools/gcc/gcc-configure-target.inc ./recipes-devtools/gdb/gdb-cross.inc ./recipes-devtools/gdb/gdb.inc ./recipes-devtools/gdb/gdb-common.inc This seems totally wrong to me to since it overrides recipes in subtle ways and does not document it anywhere firstly, README is not there and as it seems its a BSP layer but it has much more than a BSP metadata in it. even then if it needed a new toolchain then it should have used different names for includes like meta-linaro-toolchain does. if it needed to enhance existing recipes from OE-Core or reuse them then it should have included them as it is and tweaked with bbappend or created new recipes itself for aarch64 compiler tools. I will leave this to meta-linaro devs to sort out and let it play better with rest of layers meanwhile I will propose to disable meta-aarch64 in angstrom. Thanks On Apr 8, 2013, at 2:06 AM, Jack Mitchell m...@communistcode.co.uk wrote: On 08/04/13 09:52, Jack Mitchell wrote: On 05/04/13 18:03, Khem Raj wrote: On Apr 5, 2013, at 9:36 AM, Jack Mitchell m...@communistcode.co.uk wrote: I build for the beaglebone and I changed them in line with your default beaglebone build patch you posted a week or so ago. I think it moved it form soft to hard float possibly... yes do a clean build if possible Hi Khem, Clean build results in the same failure. Host GCC: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.0/lto-wrapper Target: x86_64-unknown-linux-gnu Configured with: /build/src/gcc-4.8.0/configure --prefix=/usr --libdir=/usr/lib --libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=https://bugs.archlinux.org/ --enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++ --enable-shared --enable-threads=posix --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-clocale=gnu --disable-libstdcxx-pch --enable-gnu-unique-object --enable-linker-build-id --enable-cloog-backend=isl --disable-cloog-version-check --enable-lto --enable-gold --enable-ld=default --enable-plugin --with-plugin-ld=ld.gold --with-linker-hash-style=gnu --disable-install-libiberty --disable-multilib --disable-libssp --disable-werror --enable-checking=release Thread model: posix gcc version 4.8.0 (GCC) Tune: DEFAULTTUNE_beaglebone = cortexa8hf-neon Cheers, Ok, looks like it might have been fluke that it just failed when I changed tune, as it also fails with the old tune, please see attached. Cheers, Jack. -- Jack Mitchell (j...@embed.me.uk) Embedded Systems Engineer http://www.embed.me.uk -- log.do_compile.25230___ Openembedded-core mailing list openembedded-c...@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Narcissus update to v2012.12, please read
On Apr 8, 2013, at 10:43 AM, Ulf Samuelsson angstrom-...@emagii.com wrote: DEFAULTTUNE=cortexa8hf-neon Hardfloat/softfp t is a DISTRO decision, not a machine decision, so I can't add meta-allwinner and meta-cubox to Angstrom with that setting in the machine configs. Does that mean that Angstrom cannot be used for ARM9 nowadays? absolutely it can be. Above default tunes are machine specific but are part of distro policy and not machine policy Cortex-A5 without Neon? ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] bug in libgdbm-devel
On Mar 25, 2013, at 9:42 AM, andrew hutchison drew.hutchi...@smartqloud.com wrote: Greetings all. I'm new to the list (and pretty much to angstrom), but discovered a problem attempting to compile something which depends libgdbm. /usr/bin/libgdbm_compat.la line 20 reads: dependency_libs=' =/usr/lib/libgdbm.la' and this causes libtool to puke. Changing it to dependency_libs='/usr/lib/libgdbm.la' works. which version of cross libtool are you running.? =/x/y/z/ is perfectly alright if libtool understands sysroot Again, sorry if this isn't the correct place to bring this up. ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] bug in libgdbm-devel
On Mar 25, 2013, at 3:30 PM, andrew hutchison drew.hutchi...@smartqloud.com wrote: I was trying a default build of freeradius v2.2.0 on the target. This seems to have brought his own copy of libtool v1.5.22, so I can see how that might have been the problem. Thanks! for sysroot to work you need libtool 2.4+ On Mon, Mar 25, 2013 at 3:53 PM, Khem Raj raj.k...@gmail.com wrote: On Mar 25, 2013, at 9:42 AM, andrew hutchison drew.hutchi...@smartqloud.com wrote: Greetings all. I'm new to the list (and pretty much to angstrom), but discovered a problem attempting to compile something which depends libgdbm. /usr/bin/libgdbm_compat.la line 20 reads: dependency_libs=' =/usr/lib/libgdbm.la' and this causes libtool to puke. Changing it to dependency_libs='/usr/lib/libgdbm.la' works. which version of cross libtool are you running.? =/x/y/z/ is perfectly alright if libtool understands sysroot Again, sorry if this isn't the correct place to bring this up. ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Narcissus update to v2012.12, please read
On Mar 24, 2013, at 2:59 AM, Koen Kooi k...@dominion.thruhere.net wrote: Thanks! Can you apply it to meta-angstrom master please? yes. I plan to. I am running a build for beagleboard systemd-image once it passes and I am able to boot beaglebone with the image I built for bone I will commit it. Should be done by tomorrow. ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Narcissus update to v2012.12, please read
On Mar 22, 2013, at 3:35 AM, Koen Kooi k...@dominion.thruhere.net wrote: Op 21 mrt. 2013, om 18:33 heeft Nicolas Aguirre aguirre.nico...@gmail.com het volgende geschreven: Hi, I'm currently working on an home automation project (calaos), which uses angstrom and oe-core + my own recipes [1][2]. I maitains a set of machine for this project : n450 cubieboard mele a1000/2000 cubox olinuxino-a13 rasberry-pi mele a1000/2000, cubieboard and olinuxino-a13 is based on meta-allwinner [3] cubox is based on meta-cubox [4] I'm using the danny branch for all my layers, so i guess i can help here. I attached the patch for the support of allwinner and cubox. I will run a build for mele/cubieboard/olinuxino and cubox during the night and tomorrow to check that everything build correctly with setup-scripts. Same comment I made a few months ago: DEFAULTTUNE=cortexa8hf-neon Hardfloat/softfp t is a DISTRO decision, I agree. I have a patch that I am testing right now which switches beaglebone and beagleboard to use hardfp ABI how its implemented in OE-Core it comes out to be a machine feature. Since if you set DEFAULTTUNE=cortexa8hf-neon then its set for all machines in the distro and there is no way to sat append callconvention-hard to TUNE_FEATURES What I have is something like this patch here 0001-angstrom-next-Switch-beaglebone-and-beagleboar-to-us.patch Description: Binary data not a machine decision, so I can't add meta-allwinner and meta-cubox to Angstrom with that setting in the machine configs. regards, Koen ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Narcissus update to v2012.12, please read
On Mar 22, 2013, at 6:39 AM, Philip Balister phi...@balister.org wrote: The main change (in my understanding) with the hf abi is that a function can return a value in one of the NEON registers. VFP registers ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] How do I Replace journld.conf
On Mar 7, 2013, at 7:02 AM, Wayne Tams wayne.t...@gmail.com wrote: Hi, I have created a bbappend in recipes-core/systemd inside my meta layer but it doesn't seem to apply to anything. I have done similar bbappends for different recipes without issue but the difference is that I can navigate to the recipes in question. show the bbappend which is failing Which recipe installs journld.conf to the angstrom filesystem? systemd. I am using a mostly unmodified version of set-up scripts using the 1.2 denzil branch and building for arm. Thanks Wayne ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] kernel images get wiped out
On Tue, Feb 26, 2013 at 11:07 AM, Peter Kurrasch gtin...@hotmail.com wrote: I'm using angstrom 2012.12 w/ yocto 1.3 (for Beagleboard-xM) and I keep running into this frustrating problem as I'm making kernel updates and rebuild my system image. Basically I make my kernel updates, rebuild it, etc. and get a suitable uImage that works. Then I go build anything else OK what is this you did here. Concrete examples will help understand the issue better. and the first thing bitbake does is run the SetScene scripts that wipe out my kernel updates and the images. In fact in the deploy/images/beagleboard directory not only has my uImage removed but 4 old ones appear in it's place--from Feb 8th! I can't figure out where those old things are squirreled away nor how to get rid of them. It could be because rm_work is enabled in local.conf. You could experiment by disabling that. Any thoughts and/or anyone know when this situation might get corrected? Thanks, Peter ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Systemd timers
On Wed, Feb 20, 2013 at 10:14 AM, Wayne Tams wayne.t...@gmail.com wrote: Hi, I am making some modifications to Angstrom and I need to add a new timer to systemd. Now my timer works fine when I start it manually using systemctl but I just can't figure out how to get it to start auto-magically when systemd brings all the other services online? Is the behaviour I am expecting not what systemd timer units provide? I have created some other standard services which initialise normally. I am now considering just adding the systemctl start myservice.timer to another startup script to drag it into existence. Here is my bb if that is of any help. All the best Wayne //--- inherit allarch systemd SRC_URI = \ file://myservice.service \ file://myservice.timer \ do_install () { install -d ${D}/${base_libdir}/systemd/system install -m 0644 ${WORKDIR}/myservice.service ${D}/${base_libdir}/systemd/system/ install -m 0644 ${WORKDIR}/myservice.timer ${D}/${base_libdir}/systemd/system/ } Whats your target arch ? you do not need the above do install step if you are using meta-systemd but using ${base_libdir} to install unit files is wrong. You should use ${D}${systemd_unitdir}/system instead. it would also help if you could show the unitfile contents too NATIVE_SYSTEMD_SUPPORT = 1 SYSTEMD_PACKAGES = ${PN} SYSTEMD_SERVICE_${PN} = myservice.timer FILES_${PN} += ${base_libdir}/systemd // ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] add gudev to systemd
On Sun, Jan 20, 2013 at 8:17 AM, Kovesdi Gyorgy k...@teledigit.eu wrote: Hi, I need gudev-1.0 package for building clutter with evdev input. I found that it is merged into systemd, so the followings are added to the systemd recipe: PACKAGES+= gudev-1.0 RDEPENDS_udev += gudev-1.0 FILES_gudev-1.0 = \ /usr/include/gudev-1.0/gudev/*.h \ I see that those header files are put in the directories image/, package/, and sysroot-destdir/ under the build directory during build phase, but nothing is provided in the package gudev-1.0. Currently i don't know why. Please help me about it. are you using master ? $ rpm -qlp libgudev-1.0-0-197-r3.1.ppce500v2.rpm warning: libgudev-1.0-0-197-r3.1.ppce500v2.rpm: Header V4 DSA/SHA1 Signature, key ID e0c428fd: NOKEY /lib /lib/libgudev-1.0.so.0 /lib/libgudev-1.0.so.0.1.3 Thanx Gyorgy Kovesdi ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Erroin rebuilding angstrom image using bitbake
On Sun, Jan 20, 2013 at 9:45 AM, Amlekar Gopal gopal_amle...@yahoo.com wrote: | checking whether the C compiler works... no | configure: error: in `/home/beagle/setup-scripts/build/tmp-angstrom_v2012_05-eglibc/work/armv7a-angstrom-linux-gnueabi/systemd-v189-r6/git': | configure: error: C compiler cannot create executables | See `config.log' for more details if your C compiler is not working it wont fly far. So please post the config.log as it advised above so we can get more info ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
[Angstrom-devel] [angstrom-scripts][PATCH] scripts/layerman: Run gc and prune dead branches
This would run git garbage collector and prune the branches which has been deleted in upstream repo. Signed-off-by: Khem Raj raj.k...@gmail.com --- scripts/layerman |1 + 1 file changed, 1 insertion(+) diff --git a/scripts/layerman b/scripts/layerman index 777cdb1..0ca4d74 100755 --- a/scripts/layerman +++ b/scripts/layerman @@ -74,6 +74,7 @@ function update_layers() { if [ ${REV} = HEAD ] ; then cd ${LAYERDIR} || exit 1 git stash /dev/null git pull --rebase git stash pop /dev/null + git gc /dev/null git remote prune origin /dev/null else cd ${LAYERDIR} || exit 1 CURRENTCOMMIT=$(git log --oneline --no-abbrev -1 | awk '{print $1}') -- 1.7.9.5 ___ 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 3/6] base-files: make PRINC work properly for multiple bbappends
From: Andreas Müller schnitzelt...@googlemail.com --- recipes-core/base-files/base-files_3.0.14.bbappend |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/recipes-core/base-files/base-files_3.0.14.bbappend b/recipes-core/base-files/base-files_3.0.14.bbappend index 5420ddb..ca719ed 100644 --- a/recipes-core/base-files/base-files_3.0.14.bbappend +++ b/recipes-core/base-files/base-files_3.0.14.bbappend @@ -1,6 +1,6 @@ FILESEXTRAPATHS := ${THISDIR}/${PN} -PRINC = 15 +PRINC := ${@int(PRINC) + 15} # Original: volatiles = cache run log lock tmp # We don't any of those in volatiles, so: -- 1.7.9.5 ___ 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 5/6] update-rc.d: make PRINC work properly for multiple bbappends
From: Andreas Müller schnitzelt...@googlemail.com --- recipes-core/update-rc.d/update-rc.d_0.7.bbappend |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/recipes-core/update-rc.d/update-rc.d_0.7.bbappend b/recipes-core/update-rc.d/update-rc.d_0.7.bbappend index 8e9b0c0..86aed8e 100644 --- a/recipes-core/update-rc.d/update-rc.d_0.7.bbappend +++ b/recipes-core/update-rc.d/update-rc.d_0.7.bbappend @@ -2,5 +2,5 @@ FILESEXTRAPATHS := ${THISDIR}/${PN} SRC_URI += file://0001-update-rc.d-make-s-a-noop-when-systemd-is-present.patch -PRINC = 1 +PRINC := ${@int(PRINC) + 1} -- 1.7.9.5 ___ 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 1/6] angstrom-next: Adapt to nativesdk renaming
Signed-off-by: Khem Raj raj.k...@gmail.com --- conf/distro/angstrom-next.conf | 18 +- conf/distro/include/angstrom-uclibc.inc | 10 +- 2 files changed, 14 insertions(+), 14 deletions(-) diff --git a/conf/distro/angstrom-next.conf b/conf/distro/angstrom-next.conf index 675bcaf..30c5e42 100644 --- a/conf/distro/angstrom-next.conf +++ b/conf/distro/angstrom-next.conf @@ -54,7 +54,7 @@ FEED_BASEPATH = feeds/core/${ANGSTROM_PKG_FORMAT}/${TCLIBC}/ LINUX_LIBC_HEADERS_VERSION ?= 3.4% PREFERRED_VERSION_linux-libc-headers = ${LINUX_LIBC_HEADERS_VERSION} PREFERRED_VERSION_linux-libc-headers-native = ${LINUX_LIBC_HEADERS_VERSION} -PREFERRED_VERSION_linux-libc-headers-nativesdk = ${LINUX_LIBC_HEADERS_VERSION} +PREFERRED_VERSION_nativesdk-linux-libc-headers = ${LINUX_LIBC_HEADERS_VERSION} ANGSTROM_EGLIBC_VERSION ?= 2.16 @@ -62,13 +62,13 @@ ANGSTROM_UCLIBC_VERSION ?= 0.9.33+git% PREFERRED_VERSION_uclibc ?= ${ANGSTROM_UCLIBC_VERSION} PREFERRED_VERSION_uclibc-initial ?= ${ANGSTROM_UCLIBC_VERSION} -PREFERRED_VERSION_uclibc-nativesdk ?= ${ANGSTROM_UCLIBC_VERSION} -PREFERRED_VERSION_uclibc-initial-nativesdk ?= ${ANGSTROM_UCLIBC_VERSION} +PREFERRED_VERSION_nativesdk-uclibc ?= ${ANGSTROM_UCLIBC_VERSION} +PREFERRED_VERSION_nativesdk-uclibc-initial ?= ${ANGSTROM_UCLIBC_VERSION} PREFERRED_VERSION_eglibc ?= ${ANGSTROM_EGLIBC_VERSION} PREFERRED_VERSION_eglibc-initial ?= ${ANGSTROM_EGLIBC_VERSION} -PREFERRED_VERSION_eglibc-nativesdk ?= ${ANGSTROM_EGLIBC_VERSION} -PREFERRED_VERSION_eglibc-initial-nativesdk ?= ${ANGSTROM_EGLIBC_VERSION} +PREFERRED_VERSION_nativesdk-eglibc ?= ${ANGSTROM_EGLIBC_VERSION} +PREFERRED_VERSION_nativesdk-eglibc-initial ?= ${ANGSTROM_EGLIBC_VERSION} PREFERRED_VERSION_eglibc-locale?= ${ANGSTROM_EGLIBC_VERSION} PREFERRED_VERSION_cross-localedef-native ?= ${ANGSTROM_EGLIBC_VERSION} @@ -98,9 +98,9 @@ PREFERRED_VERSION_gcc-crosssdk ?= ${ANGSTROM_GCC_VERSION} PREFERRED_VERSION_gcc-crosssdk-initial ?= ${ANGSTROM_GCC_VERSION} PREFERRED_VERSION_gcc-crosssdk-intermediate ?= ${ANGSTROM_GCC_VERSION} PREFERRED_VERSION_gcc-runtime?= ${ANGSTROM_GCC_VERSION} -PREFERRED_VERSION_gcc-runtime-nativesdk ?= ${ANGSTROM_GCC_VERSION} +PREFERRED_VERSION_nativesdk-gcc-runtime ?= ${ANGSTROM_GCC_VERSION} PREFERRED_VERSION_libgcc ?= ${ANGSTROM_GCC_VERSION} -PREFERRED_VERSION_libgcc-nativesdk ?= ${ANGSTROM_GCC_VERSION} +PREFERRED_VERSION_nativesdk-libgcc ?= ${ANGSTROM_GCC_VERSION} #avr32 only has patches for binutils 2.17 in OE PREFERRED_VERSION_binutils_avr32 = 2.17 @@ -185,6 +185,6 @@ SPLASH ?= ' ${@base_contains(MACHINE_FEATURES, screen, psplash-angstrom, DISTRO_FEATURES += ${LDISGOLD} #LDISGOLD_arm = ld-is-gold -LDISGOLD_x86 = ld-is-gold -LDISGOLD_x86_64 = ld-is-gold +#LDISGOLD_x86 = ld-is-gold +#LDISGOLD_x86_64 = ld-is-gold LDISGOLD = diff --git a/conf/distro/include/angstrom-uclibc.inc b/conf/distro/include/angstrom-uclibc.inc index 660ce5f..a17e8c2 100644 --- a/conf/distro/include/angstrom-uclibc.inc +++ b/conf/distro/include/angstrom-uclibc.inc @@ -12,11 +12,11 @@ PREFERRED_PROVIDER_virtual/libintl_avr32 = proxy-libintl PREFERRED_PROVIDER_virtual/gettext_avr32 = proxy-libintl PREFERRED_PROVIDER_virtual/${TARGET_PREFIX}libc-initial = uclibc-initial PREFERRED_PROVIDER_virtual/${TARGET_PREFIX}libc-for-gcc = uclibc -PREFERRED_PROVIDER_virtual/libiconv-nativesdk = eglibc-nativesdk -PREFERRED_PROVIDER_virtual/libc-nativesdk = eglibc-nativesdk -PREFERRED_PROVIDER_virtual/${SDK_PREFIX}libc-initial-nativesdk = eglibc-initial-nativesdk -PREFERRED_PROVIDER_virtual/${SDK_PREFIX}libc-nativesdk = eglibc-nativesdk -PREFERRED_PROVIDER_virtual/${SDK_PREFIX}libc-for-gcc-nativesdk = eglibc-nativesdk +PREFERRED_PROVIDER_virtual/libiconv-nativesdk = nativesdk-eglibc +PREFERRED_PROVIDER_virtual/libc-nativesdk = nativesdk-eglibc +PREFERRED_PROVIDER_virtual/${SDK_PREFIX}libc-initial-nativesdk = nativesdk-eglibc-initial +PREFERRED_PROVIDER_virtual/${SDK_PREFIX}libc-nativesdk = nativesdk-eglibc +PREFERRED_PROVIDER_virtual/${SDK_PREFIX}libc-for-gcc-nativesdk = nativesdk-eglibc # libc settings DISTRO_FEATURES += ${@['', ' nls'][bb.data.getVar('ENABLE_BINARY_LOCALE_GENERATION', d, 1) == '1']} # FIXME: We enable IPv4 per default to avoid alot of breakage. -- 1.7.9.5 ___ 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 6/6] angstrom: fix java versions
From: Koen Kooi k...@dominion.thruhere.net Signed-off-by: Koen Kooi k...@dominion.thruhere.net --- conf/distro/include/angstrom-jalimo.conf |4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/conf/distro/include/angstrom-jalimo.conf b/conf/distro/include/angstrom-jalimo.conf index 61ec693..9daa68f 100644 --- a/conf/distro/include/angstrom-jalimo.conf +++ b/conf/distro/include/angstrom-jalimo.conf @@ -22,7 +22,5 @@ PREFERRED_VERSION_jamvm = 1.5.2 PREFERRED_PROVIDER_swt3.4-gtk = swt3.4-gtk PREFERRED_PROVIDER_classpath = classpath -PREFERRED_VERSION_openjdk-6-jre = 6b18-1.8.11 +PREFERRED_VERSION_openjdk-6-jre = 6b24-1.11.1 PREFERRED_VERSION_icedtea6-native = 1.8.11 - - -- 1.7.9.5 ___ 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/next][PATCH 2/2] angstrom-next: Adapt to nativesdk renaming
Signed-off-by: Khem Raj raj.k...@gmail.com --- conf/distro/angstrom-next.conf | 18 +- conf/distro/include/angstrom-uclibc.inc | 10 +- 2 files changed, 14 insertions(+), 14 deletions(-) diff --git a/conf/distro/angstrom-next.conf b/conf/distro/angstrom-next.conf index 675bcaf..30c5e42 100644 --- a/conf/distro/angstrom-next.conf +++ b/conf/distro/angstrom-next.conf @@ -54,7 +54,7 @@ FEED_BASEPATH = feeds/core/${ANGSTROM_PKG_FORMAT}/${TCLIBC}/ LINUX_LIBC_HEADERS_VERSION ?= 3.4% PREFERRED_VERSION_linux-libc-headers = ${LINUX_LIBC_HEADERS_VERSION} PREFERRED_VERSION_linux-libc-headers-native = ${LINUX_LIBC_HEADERS_VERSION} -PREFERRED_VERSION_linux-libc-headers-nativesdk = ${LINUX_LIBC_HEADERS_VERSION} +PREFERRED_VERSION_nativesdk-linux-libc-headers = ${LINUX_LIBC_HEADERS_VERSION} ANGSTROM_EGLIBC_VERSION ?= 2.16 @@ -62,13 +62,13 @@ ANGSTROM_UCLIBC_VERSION ?= 0.9.33+git% PREFERRED_VERSION_uclibc ?= ${ANGSTROM_UCLIBC_VERSION} PREFERRED_VERSION_uclibc-initial ?= ${ANGSTROM_UCLIBC_VERSION} -PREFERRED_VERSION_uclibc-nativesdk ?= ${ANGSTROM_UCLIBC_VERSION} -PREFERRED_VERSION_uclibc-initial-nativesdk ?= ${ANGSTROM_UCLIBC_VERSION} +PREFERRED_VERSION_nativesdk-uclibc ?= ${ANGSTROM_UCLIBC_VERSION} +PREFERRED_VERSION_nativesdk-uclibc-initial ?= ${ANGSTROM_UCLIBC_VERSION} PREFERRED_VERSION_eglibc ?= ${ANGSTROM_EGLIBC_VERSION} PREFERRED_VERSION_eglibc-initial ?= ${ANGSTROM_EGLIBC_VERSION} -PREFERRED_VERSION_eglibc-nativesdk ?= ${ANGSTROM_EGLIBC_VERSION} -PREFERRED_VERSION_eglibc-initial-nativesdk ?= ${ANGSTROM_EGLIBC_VERSION} +PREFERRED_VERSION_nativesdk-eglibc ?= ${ANGSTROM_EGLIBC_VERSION} +PREFERRED_VERSION_nativesdk-eglibc-initial ?= ${ANGSTROM_EGLIBC_VERSION} PREFERRED_VERSION_eglibc-locale?= ${ANGSTROM_EGLIBC_VERSION} PREFERRED_VERSION_cross-localedef-native ?= ${ANGSTROM_EGLIBC_VERSION} @@ -98,9 +98,9 @@ PREFERRED_VERSION_gcc-crosssdk ?= ${ANGSTROM_GCC_VERSION} PREFERRED_VERSION_gcc-crosssdk-initial ?= ${ANGSTROM_GCC_VERSION} PREFERRED_VERSION_gcc-crosssdk-intermediate ?= ${ANGSTROM_GCC_VERSION} PREFERRED_VERSION_gcc-runtime?= ${ANGSTROM_GCC_VERSION} -PREFERRED_VERSION_gcc-runtime-nativesdk ?= ${ANGSTROM_GCC_VERSION} +PREFERRED_VERSION_nativesdk-gcc-runtime ?= ${ANGSTROM_GCC_VERSION} PREFERRED_VERSION_libgcc ?= ${ANGSTROM_GCC_VERSION} -PREFERRED_VERSION_libgcc-nativesdk ?= ${ANGSTROM_GCC_VERSION} +PREFERRED_VERSION_nativesdk-libgcc ?= ${ANGSTROM_GCC_VERSION} #avr32 only has patches for binutils 2.17 in OE PREFERRED_VERSION_binutils_avr32 = 2.17 @@ -185,6 +185,6 @@ SPLASH ?= ' ${@base_contains(MACHINE_FEATURES, screen, psplash-angstrom, DISTRO_FEATURES += ${LDISGOLD} #LDISGOLD_arm = ld-is-gold -LDISGOLD_x86 = ld-is-gold -LDISGOLD_x86_64 = ld-is-gold +#LDISGOLD_x86 = ld-is-gold +#LDISGOLD_x86_64 = ld-is-gold LDISGOLD = diff --git a/conf/distro/include/angstrom-uclibc.inc b/conf/distro/include/angstrom-uclibc.inc index 660ce5f..a17e8c2 100644 --- a/conf/distro/include/angstrom-uclibc.inc +++ b/conf/distro/include/angstrom-uclibc.inc @@ -12,11 +12,11 @@ PREFERRED_PROVIDER_virtual/libintl_avr32 = proxy-libintl PREFERRED_PROVIDER_virtual/gettext_avr32 = proxy-libintl PREFERRED_PROVIDER_virtual/${TARGET_PREFIX}libc-initial = uclibc-initial PREFERRED_PROVIDER_virtual/${TARGET_PREFIX}libc-for-gcc = uclibc -PREFERRED_PROVIDER_virtual/libiconv-nativesdk = eglibc-nativesdk -PREFERRED_PROVIDER_virtual/libc-nativesdk = eglibc-nativesdk -PREFERRED_PROVIDER_virtual/${SDK_PREFIX}libc-initial-nativesdk = eglibc-initial-nativesdk -PREFERRED_PROVIDER_virtual/${SDK_PREFIX}libc-nativesdk = eglibc-nativesdk -PREFERRED_PROVIDER_virtual/${SDK_PREFIX}libc-for-gcc-nativesdk = eglibc-nativesdk +PREFERRED_PROVIDER_virtual/libiconv-nativesdk = nativesdk-eglibc +PREFERRED_PROVIDER_virtual/libc-nativesdk = nativesdk-eglibc +PREFERRED_PROVIDER_virtual/${SDK_PREFIX}libc-initial-nativesdk = nativesdk-eglibc-initial +PREFERRED_PROVIDER_virtual/${SDK_PREFIX}libc-nativesdk = nativesdk-eglibc +PREFERRED_PROVIDER_virtual/${SDK_PREFIX}libc-for-gcc-nativesdk = nativesdk-eglibc # libc settings DISTRO_FEATURES += ${@['', ' nls'][bb.data.getVar('ENABLE_BINARY_LOCALE_GENERATION', d, 1) == '1']} # FIXME: We enable IPv4 per default to avoid alot of breakage. -- 1.7.9.5 ___ 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/next][PATCH 1/2] omap3-mkcard: Remove hardlink and add LIC_FILES_CHKSUM
Instead of hard linking omap3-mkcard.sh refer to it using FILESPATH. This avoids the parse warning WARNING: Unable to get checksum for omap3-mkcard SRC_URI entry omap3-mkcard.sh: file could not be found Signed-off-by: Khem Raj raj.k...@gmail.com Signed-off-by: Koen Kooi k...@dominion.thruhere.net --- recipes-angstrom/angstrom/omap3-mkcard.bb |6 +- .../angstrom/omap3-mkcard/omap3-mkcard.sh |1 - 2 files changed, 5 insertions(+), 2 deletions(-) delete mode 12 recipes-angstrom/angstrom/omap3-mkcard/omap3-mkcard.sh diff --git a/recipes-angstrom/angstrom/omap3-mkcard.bb b/recipes-angstrom/angstrom/omap3-mkcard.bb index 31a20a3..f09cfe5 100644 --- a/recipes-angstrom/angstrom/omap3-mkcard.bb +++ b/recipes-angstrom/angstrom/omap3-mkcard.bb @@ -1,8 +1,12 @@ DESCRIPTION=Format a card for omap3 booting LICENSE = GPLv2 +LIC_FILES_CHKSUM = file://${COREBASE}/meta/files/common-licenses/GPL-2.0;md5=801f80980d171dd6425610833a22dbe6 + SRC_URI = file://omap3-mkcard.sh -PR = r1 +FILESPATH =. ${FILE_DIRNAME}/../../contrib: + +PR = r2 do_install() { install -d ${D}${bindir}/ diff --git a/recipes-angstrom/angstrom/omap3-mkcard/omap3-mkcard.sh b/recipes-angstrom/angstrom/omap3-mkcard/omap3-mkcard.sh deleted file mode 12 index b8c8a70..000 --- a/recipes-angstrom/angstrom/omap3-mkcard/omap3-mkcard.sh +++ /dev/null @@ -1 +0,0 @@ -../../../contrib/angstrom/omap3-mkcard.sh \ No newline at end of file -- 1.7.9.5 ___ 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/next][PATCH 1/2] omap3-mkcard: Remove hardlink and add LIC_FILES_CHKSUM
oops ignore this patch since it has already been applied. On Wed, Nov 28, 2012 at 11:34 AM, Khem Raj raj.k...@gmail.com wrote: Instead of hard linking omap3-mkcard.sh refer to it using FILESPATH. This avoids the parse warning WARNING: Unable to get checksum for omap3-mkcard SRC_URI entry omap3-mkcard.sh: file could not be found Signed-off-by: Khem Raj raj.k...@gmail.com Signed-off-by: Koen Kooi k...@dominion.thruhere.net --- recipes-angstrom/angstrom/omap3-mkcard.bb |6 +- .../angstrom/omap3-mkcard/omap3-mkcard.sh |1 - 2 files changed, 5 insertions(+), 2 deletions(-) delete mode 12 recipes-angstrom/angstrom/omap3-mkcard/omap3-mkcard.sh diff --git a/recipes-angstrom/angstrom/omap3-mkcard.bbb/recipes-angstrom/angstrom/ omap3-mkcard.bb index 31a20a3..f09cfe5 100644 --- a/recipes-angstrom/angstrom/omap3-mkcard.bb +++ b/recipes-angstrom/angstrom/omap3-mkcard.bb @@ -1,8 +1,12 @@ DESCRIPTION=Format a card for omap3 booting LICENSE = GPLv2 +LIC_FILES_CHKSUM = file://${COREBASE}/meta/files/common-licenses/GPL-2.0;md5=801f80980d171dd6425610833a22dbe6 + SRC_URI = file://omap3-mkcard.sh -PR = r1 +FILESPATH =. ${FILE_DIRNAME}/../../contrib: + +PR = r2 do_install() { install -d ${D}${bindir}/ diff --git a/recipes-angstrom/angstrom/omap3-mkcard/omap3-mkcard.sh b/recipes-angstrom/angstrom/omap3-mkcard/omap3-mkcard.sh deleted file mode 12 index b8c8a70..000 --- a/recipes-angstrom/angstrom/omap3-mkcard/omap3-mkcard.sh +++ /dev/null @@ -1 +0,0 @@ -../../../contrib/angstrom/omap3-mkcard.sh \ No newline at end of file -- 1.7.9.5 ___ 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] bblayers.conf: Remove meta-fishriver
It has been retired from meta-intel Signed-off-by: Khem Raj raj.k...@gmail.com --- conf/bblayers.conf |1 - 1 file changed, 1 deletion(-) diff --git a/conf/bblayers.conf b/conf/bblayers.conf index 7592371..9f6ac2a 100644 --- a/conf/bblayers.conf +++ b/conf/bblayers.conf @@ -38,7 +38,6 @@ BSPLAYERS ?= \ ${TOPDIR}/sources/meta-intel/meta-sugarbay \ ${TOPDIR}/sources/meta-intel/meta-crownbay \ ${TOPDIR}/sources/meta-intel/meta-emenlow \ - ${TOPDIR}/sources/meta-intel/meta-fishriver \ ${TOPDIR}/sources/meta-intel/meta-fri2 \ ${TOPDIR}/sources/meta-intel/meta-jasperforest \ ${TOPDIR}/sources/meta-intel/meta-n450 \ -- 1.7.9.5 ___ 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][PATCH] omap3-mkcard: Remove hardlink and add LIC_FILES_CHKSUM
ping ^^ On Sat, Sep 22, 2012 at 10:43 AM, Khem Raj raj.k...@gmail.com wrote: ping^ On Sun, Sep 9, 2012 at 1:07 PM, Khem Raj raj.k...@gmail.com wrote: Instead of hard linking omap3-mkcard.sh refer to it using FILESPATH. This avoids the parse warning WARNING: Unable to get checksum for omap3-mkcard SRC_URI entry omap3-mkcard.sh: file could not be found Signed-off-by: Khem Raj raj.k...@gmail.com --- recipes-angstrom/angstrom/omap3-mkcard.bb |6 +- .../angstrom/omap3-mkcard/omap3-mkcard.sh |1 - 2 files changed, 5 insertions(+), 2 deletions(-) delete mode 12 recipes-angstrom/angstrom/omap3-mkcard/omap3-mkcard.sh diff --git a/recipes-angstrom/angstrom/omap3-mkcard.bb b/recipes-angstrom/angstrom/omap3-mkcard.bb index 31a20a3..f09cfe5 100644 --- a/recipes-angstrom/angstrom/omap3-mkcard.bb +++ b/recipes-angstrom/angstrom/omap3-mkcard.bb @@ -1,8 +1,12 @@ DESCRIPTION=Format a card for omap3 booting LICENSE = GPLv2 +LIC_FILES_CHKSUM = file://${COREBASE}/meta/files/common-licenses/GPL-2.0;md5=801f80980d171dd6425610833a22dbe6 + SRC_URI = file://omap3-mkcard.sh -PR = r1 +FILESPATH =. ${FILE_DIRNAME}/../../contrib: + +PR = r2 do_install() { install -d ${D}${bindir}/ diff --git a/recipes-angstrom/angstrom/omap3-mkcard/omap3-mkcard.sh b/recipes-angstrom/angstrom/omap3-mkcard/omap3-mkcard.sh deleted file mode 12 index b8c8a70..000 --- a/recipes-angstrom/angstrom/omap3-mkcard/omap3-mkcard.sh +++ /dev/null @@ -1 +0,0 @@ -../../../contrib/angstrom/omap3-mkcard.sh \ No newline at end of file -- 1.7.9.5 ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel