Re: [yocto] [bitbake-devel] [oe] Infra Full Stop 12/26-12/29
On Sun, Dec 25, 2016 at 08:06:50PM -0800, Michael Halstead wrote: > In preparation for the scheduled maintenance I have moved > git.openembedded.org to a new server temporarily. E-mail and Patchwork > hooks may not work correctly. All other git operations as well as > listings at http://git.openembedded.org/ should continue working. > > If you have a git remote pointed directly at openembedded.org it will > fail. Please update your remote to point at git.openembedded.org and try > again. It doesn't seem to be working here: error: Could not fetch origin fatal: unable to connect to git.openembedded.org: git.openembedded.org[0: 104.236.212.160]: errno=Connection refused git.openembedded.org[1: 2604:a880:800:10::2127:2001]: errno=Network is unreachable But that's OK for me, I was prepared to do some holiday celebrations thanks to planned downtime :). And I have some local mirrors in case I got tired of celebrations before the downtime is over. > Other services that will stay up during the maintenance are: > > Layerindex https://layers.openembedded.org/ > Mailman http://lists.openembedded.org/ > Patchwork https://patchwork.openembedded.org/ > > I'd like the share my appreciation for the OpenEmbedded volunteer > sysadmins who are taking time away from their holiday celebrations to > make this downtime as convenient for the rest of us as possible. > > > On 12/22/2016 09:19 AM, Tom King wrote: > > Schedule is 06:00UTC 27DEC16 for the full stop. Things will start coming > > back (estimated) about 48hrs later. > > > > Tom > > > > On Tue, Dec 20, 2016 at 11:16 AM, Khem Raj wrote: > > > >>> On Dec 20, 2016, at 10:50 AM, Tom King wrote: > >>> > >>> Hi All, > >>> > >>> We have been looking for a time when we could do a full stop of the infra > >>> to upgrade some bits and clear out some faults. > >>> > >>> This will involve shutting down the main machine that we use for *most* > >> of > >>> the OE infra. > >>> > >>> Our goal is to put up a backup git master but other services such as: > >> wiki, > >>> patches, etc will be offline for some or all of that period. > >>> > >>> We have delayed doing this much needed maintenance to try to work around > >>> Yocto and OE release schedules and it is necessary that we take this time > >>> to do the work. > >>> > >> I guess, you need to come up with a tentative down-time schedule. > >> > >>> Tom > >>> (for the OE Infra Team) > >>> -- > >>> ___ > >>> Openembedded-devel mailing list > >>> openembedded-de...@lists.openembedded.org > >>> http://lists.openembedded.org/mailman/listinfo/openembedded-devel > >> -- > >> ___ > >> Openembedded-devel mailing list > >> openembedded-de...@lists.openembedded.org > >> http://lists.openembedded.org/mailman/listinfo/openembedded-devel > >> > > -- > Michael Halstead > Linux Foundation / SysAdmin > > > -- > ___ > bitbake-devel mailing list > bitbake-de...@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/bitbake-devel -- Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com signature.asc Description: Digital signature -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH] Provide additional OECORE_EXTRA_SYSROOT variable for CMake Toolchain
Hey, I would like to propose the appended patch for Poky's CMake toolchain to
allow its usage inside a Yocto SDK for building libraries and applications
using an external (meaning as in "different to the native SDK dir") install
directory.
I hope that I use the correct mailing list and patch format. (It's my first
patch to Yocto) Please tell me if this mail is better suited for a different
mailing list.
Cheers,
Andreas>From b09bc09c13d1ec9334bdc8a2c148436f1f363b71 Mon Sep 17 00:00:00 2001
From: Andreas Cord-Landwehr
Date: Mon, 26 Dec 2016 13:43:02 +0100
Subject: [PATCH] Provide additional OECORE_EXTRA_SYSROOT variable
When compiling against a Yocto generated SDK and using an install folder
outside of the SDK's folder, CMake must be configure by using the
respective CMAKE_FIND_ROOT_PATH. This CMake cache variable is set
in the toolchain file and hence can only be configured via environment
variables; unless one wants to modify a project's CMake files.
This patch adds an additional environment variable OECORE_EXTRA_SYSROOT
to specify such an additional sysroot location that can optionally
be used when building against a Yocto SDK using this toolchain file.
Signed-off-by: Andreas Cord-Landwehr
---
meta/recipes-devtools/cmake/cmake/OEToolchainConfig.cmake | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-devtools/cmake/cmake/OEToolchainConfig.cmake b/meta/recipes-devtools/cmake/cmake/OEToolchainConfig.cmake
index 6518408c70..1927e0bdb4 100644
--- a/meta/recipes-devtools/cmake/cmake/OEToolchainConfig.cmake
+++ b/meta/recipes-devtools/cmake/cmake/OEToolchainConfig.cmake
@@ -4,7 +4,10 @@ set( CMAKE_CXX_FLAGS $ENV{CXXFLAGS} CACHE STRING "" FORCE )
set( CMAKE ASM_FLAGS ${CMAKE_C_FLAGS} CACHE STRING "" FORCE )
set( CMAKE_LDFLAGS_FLAGS ${CMAKE_CXX_FLAGS} CACHE STRING "" FORCE )
-set( CMAKE_FIND_ROOT_PATH $ENV{OECORE_TARGET_SYSROOT} $ENV{OECORE_NATIVE_SYSROOT} )
+# Re-root CMake search tree to sysroot locations given by environment variables OECORE_TARGET_SYSROOT and
+# OECORE_NATIVE_SYSROOT. For additional locations, e.g. a cross-building install directory, use
+# the OECORE_EXTRA_SYSROOT variable.
+set( CMAKE_FIND_ROOT_PATH $ENV{OECORE_TARGET_SYSROOT} $ENV{OECORE_NATIVE_SYSROOT} $ENV{OECORE_EXTRA_SYSROOT} )
set( CMAKE_FIND_ROOT_PATH_MODE_PROGRAM NEVER )
set( CMAKE_FIND_ROOT_PATH_MODE_LIBRARY ONLY )
set( CMAKE_FIND_ROOT_PATH_MODE_INCLUDE ONLY )
--
2.11.0
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Toaster fail to clone meta-oe
Hello,
After several successful builds with toaster I got an error
(UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 226:
ordinal not in range(128)).
I cloned a brand new poky directory, set up toaster in a virtualenv, etc.
and am stuck with the same error.
It seems to happen while cloning meta-oe ... but it's not clear where it
comes from.
Do you have any clue that might help ?
2016-12-26 14:52:09,110 DEBUG runbuilds: starting build SonoMKR (Release
krogoth (krogoth), BBV krogoth (Branch: krogoth)) in progress, environment
BuildEnvironment object
2016-12-26 14:52:09,112 DEBUG localhostbecontroller, our git repos are
{(u'/home/valoo/yocto/layers/meta-sonomkr', u'master'): [(u'meta-sonomkr',
u'/')],
(u'git://git.openembedded.org/meta-openembedded', u'krogoth'):
[(u'meta-oe',
u'meta-oe'),
(u'meta-python',
u'meta-python'),
(u'meta-networking',
u'meta-networking')],
(u'git://git.yoctoproject.org/meta-raspberrypi', u'krogoth'):
[(u'meta-raspberrypi',
u'')],
(u'git://git.yoctoproject.org/meta-yocto', u'krogoth'): [(u'meta-poky',
u'meta-poky'),
(u'meta-yocto-bsp',
u'meta-yocto-bsp')],
(u'git://git.yoctoproject.org/poky.git', u'krogoth'): [('bitbake',
u'bitbake'),
(u'openembedded-core',
u'meta')],
(u'git://github.com/meta-qt5/meta-qt5.git', u'krogoth'): [(u'meta-qt5',
u'')]}
2016-12-26 14:52:09,112 DEBUG lbc_shellcmmd: (/home/valoo/yocto/poky21) git
remote -v
2016-12-26 14:52:09,117 DEBUG localhostbecontroller: shellcmd success
2016-12-26 14:52:09,117 INFO Using pre-checked out source for layer {'git://
git.yoctoproject.org/poky.git': u'/home/valoo/yocto/poky21'}
2016-12-26 14:52:09,117 DEBUG localhostbecontroller: giturl git://
github.com/meta-qt5/meta-qt5.git:krogoth checking out in current directory
/home/valoo/yocto/poky21/_toaster_clones/_git___github.com_meta-qt5_meta-qt5.git_krogoth
2016-12-26 14:52:09,117 DEBUG lbc_shellcmmd:
(/home/valoo/yocto/poky21/_toaster_clones/_git___github.com_meta-qt5_meta-qt5.git_krogoth)
git remote -v
2016-12-26 14:52:09,123 DEBUG localhostbecontroller: shellcmd success
2016-12-26 14:52:09,124 DEBUG localhostbecontroller: checking out commit
krogoth to
/home/valoo/yocto/poky21/_toaster_clones/_git___github.com_meta-qt5_meta-qt5.git_krogoth
2016-12-26 14:52:09,124 DEBUG lbc_shellcmmd:
(/home/valoo/yocto/poky21/_toaster_clones/_git___github.com_meta-qt5_meta-qt5.git_krogoth)
git fetch --all && git reset --hard "origin/krogoth"
2016-12-26 14:52:09,373 DEBUG localhostbecontroller: shellcmd success
2016-12-26 14:52:09,373 DEBUG localhostbecontroller: localdirpath expected
'/home/valoo/yocto/poky21/_toaster_clones/_git___github.com_meta-qt5_meta-qt5.git_krogoth/'
2016-12-26 14:52:09,373 DEBUG localhostbecontroller: giturl git://
git.yoctoproject.org/poky.git:krogoth checking out in current directory
/home/valoo/yocto/poky21/_toaster_clones/_git___git.yoctoproject.org_poky.git_krogoth
2016-12-26 14:52:09,373 DEBUG lbc_shellcmmd:
(/home/valoo/yocto/poky21/_toaster_clones/_git___git.yoctoproject.org_poky.git_krogoth)
git remote -v
2016-12-26 14:52:09,377 DEBUG localhostbecontroller: shellcmd success
2016-12-26 14:52:09,378 DEBUG localhostbecontroller: checking out commit
krogoth to
/home/valoo/yocto/poky21/_toaster_clones/_git___git.yoctoproject.org_poky.git_krogoth
2016-12-26 14:52:09,378 DEBUG lbc_shellcmmd:
(/home/valoo/yocto/poky21/_toaster_clones/_git___git.yoctoproject.org_poky.git_krogoth)
git fetch --all && git reset --hard "origin/krogoth"
2016-12-26 14:52:10,137 DEBUG localhostbecontroller: shellcmd success
2016-12-26 14:52:10,137 DEBUG localhostbecontroller: selected poky dir name
/home/valoo/yocto/poky21/_toaster_clones/_git___git.yoctoproject.org_poky.git_krogoth
2016-12-26 14:52:10,137 DEBUG localhostbecontroller: localdirpath expected
'/home/valoo/yocto/poky21/_toaster_clones/_git___git.yoctoproject.org_poky.git_krogoth/bitbake'
2016-12-26 14:52:10,137 DEBUG localhostbecontroller: localdirpath expected
'/home/valoo/yocto/poky21/_toaster_clones/_git___git.yoctoproject.org_poky.git_krogoth/meta'
2016-12-26 14:52:10,138 DEBUG localhostbecontroller: giturl git://
git.yoctoproject.org/meta-raspberrypi:krogoth checking out in current
directory
/home/valoo/yocto/poky21/_toaster_clones/_git___git.yoctoproject.org_meta-raspberrypi_krogoth
2016-12-26 14:52:10,138 DEBUG lbc_shellcmmd:
(/home/valoo/yocto/poky21/_toaster_clones/_git___git.yoctoproject.org_meta-raspberrypi_krogoth)
git remote -v
2016-12-26 14:52:10,142 DEBUG localhostbecontroller: shellcmd success
2016-12-26 14:52:10,142 DEBUG localhostbecontroller: checking out commit
krogoth to
/home/valoo/yocto/poky21/_toaster_clones/_git___git.yoctoproject.org_meta-raspberrypi_krogoth
2016-12-26 14:52
Re: [yocto] [oe] Infra Full Stop 12/26-12/29
On 12/25/2016 11:06 PM, Michael Halstead wrote: > In preparation for the scheduled maintenance I have moved > git.openembedded.org to a new server temporarily. E-mail and Patchwork > hooks may not work correctly. All other git operations as well as > listings at http://git.openembedded.org/ should continue working. > > If you have a git remote pointed directly at openembedded.org it will > fail. Please update your remote to point at git.openembedded.org and try > again. > > Other services that will stay up during the maintenance are: > > Layerindex https://layers.openembedded.org/ > Mailman http://lists.openembedded.org/ > Patchwork https://patchwork.openembedded.org/ > > I'd like the share my appreciation for the OpenEmbedded volunteer > sysadmins who are taking time away from their holiday celebrations to > make this downtime as convenient for the rest of us as possible. I'd like to thank everyone working on this project for their hard work through out the year keeping OpenEmbeded up to date and moving it forward as the premier embedded Linux (and possibly other OS') build system. Here's to a good New Year! Philip > > > On 12/22/2016 09:19 AM, Tom King wrote: >> Schedule is 06:00UTC 27DEC16 for the full stop. Things will start coming >> back (estimated) about 48hrs later. >> >> Tom >> >> On Tue, Dec 20, 2016 at 11:16 AM, Khem Raj wrote: >> On Dec 20, 2016, at 10:50 AM, Tom King wrote: Hi All, We have been looking for a time when we could do a full stop of the infra to upgrade some bits and clear out some faults. This will involve shutting down the main machine that we use for *most* >>> of the OE infra. Our goal is to put up a backup git master but other services such as: >>> wiki, patches, etc will be offline for some or all of that period. We have delayed doing this much needed maintenance to try to work around Yocto and OE release schedules and it is necessary that we take this time to do the work. >>> I guess, you need to come up with a tentative down-time schedule. >>> Tom (for the OE Infra Team) -- ___ Openembedded-devel mailing list openembedded-de...@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel >>> -- >>> ___ >>> Openembedded-devel mailing list >>> openembedded-de...@lists.openembedded.org >>> http://lists.openembedded.org/mailman/listinfo/openembedded-devel >>> > > > signature.asc Description: OpenPGP digital signature -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [bitbake-devel] [oe] Infra Full Stop 12/26-12/29
On 12/25/2016 11:43 PM, Martin Jansa wrote: > On Sun, Dec 25, 2016 at 08:06:50PM -0800, Michael Halstead wrote: >> In preparation for the scheduled maintenance I have moved >> git.openembedded.org to a new server temporarily. E-mail and Patchwork >> hooks may not work correctly. All other git operations as well as >> listings at http://git.openembedded.org/ should continue working. >> >> If you have a git remote pointed directly at openembedded.org it will >> fail. Please update your remote to point at git.openembedded.org and try >> again. > It doesn't seem to be working here: > > error: Could not fetch origin > fatal: unable to connect to git.openembedded.org: > git.openembedded.org[0: 104.236.212.160]: errno=Connection refused > git.openembedded.org[1: 2604:a880:800:10::2127:2001]: errno=Network is > unreachable > > But that's OK for me, I was prepared to do some holiday celebrations > thanks to planned downtime :). And I have some local mirrors in case > I got tired of celebrations before the downtime is over. This is fixed now. I fulled tested push access but not normal anonymous clones. Sorry about that. > >> Other services that will stay up during the maintenance are: >> >> Layerindex https://layers.openembedded.org/ >> Mailman http://lists.openembedded.org/ >> Patchwork https://patchwork.openembedded.org/ >> >> I'd like the share my appreciation for the OpenEmbedded volunteer >> sysadmins who are taking time away from their holiday celebrations to >> make this downtime as convenient for the rest of us as possible. >> >> >> On 12/22/2016 09:19 AM, Tom King wrote: >>> Schedule is 06:00UTC 27DEC16 for the full stop. Things will start coming >>> back (estimated) about 48hrs later. >>> >>> Tom >>> >>> On Tue, Dec 20, 2016 at 11:16 AM, Khem Raj wrote: >>> > On Dec 20, 2016, at 10:50 AM, Tom King wrote: > > Hi All, > > We have been looking for a time when we could do a full stop of the infra > to upgrade some bits and clear out some faults. > > This will involve shutting down the main machine that we use for *most* of > the OE infra. > > Our goal is to put up a backup git master but other services such as: wiki, > patches, etc will be offline for some or all of that period. > > We have delayed doing this much needed maintenance to try to work around > Yocto and OE release schedules and it is necessary that we take this time > to do the work. > I guess, you need to come up with a tentative down-time schedule. > Tom > (for the OE Infra Team) > -- > ___ > Openembedded-devel mailing list > openembedded-de...@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-devel -- ___ Openembedded-devel mailing list openembedded-de...@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel >> -- >> Michael Halstead >> Linux Foundation / SysAdmin >> >> > > > >> -- >> ___ >> bitbake-devel mailing list >> bitbake-de...@lists.openembedded.org >> http://lists.openembedded.org/mailman/listinfo/bitbake-devel > -- Michael Halstead Linux Foundation / SysAdmin -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
