Re: [yocto] build error on raspberrypi3
Are you under proxy ?
If yes set http_proxy/https_proxy variables.
However, with github the protocol variable must be https.
2017-10-26 5:59 GMT+02:00 vishal ashapur :
> hi im buliding linux on rpi3 using yocto pyro branch. after doing
> "bitbake linux-raspberrypi -c menuconfig" it is downloading all
> sources but at the end it is showing the following error.
>
> ERROR: linux-raspberrypi-1_4.9.30+gitAUTOINC+e54215a9bc-r28 do_fetch:
> Fetcher failure for URL:
> 'git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.9.y'.
> Unable to fetch URL from any source.
> ERROR: linux-raspberrypi-1_4.9.30+gitAUTOINC+e54215a9bc-r28 do_fetch:
> Function failed: base_do_fetch
> ERROR: Logfile of failure stored in:
> /u/rpi2/rpi/build/tmp/work/raspberrypi2-poky-linux-
> gnueabi/linux-raspberrypi/1_4.9.30+gitAUTOINC+e54215a9bc-
> r28/temp/log.do_fetch.30856
> ERROR: Task (/u/rpi2/sources/poky-morty/meta-raspberrypi/recipes-
> kernel/linux/linux-raspberrypi_4.9.bb:do_fetch)
> failed with exit code '1'
>
> so can anybody help with this error.
> my detailed procedure for build is below
> git clone -b pyro git://git.yoctoproject.org/poky
> cd poky
> git clone -b pyro git://git.openembedded.org/meta-openembedded
> git clone -b pyro git://git.yoctoproject.org/meta-raspberrypi
>
> source sources/poky/oe-init-build-env rpi-build
>
> changes in local.conf
> MACHINE = "raspberrypi3"
> PREFERRED_VERSION_linux-raspberrypi = "4.9.%"
> DISTRO_FEATURES_remove = "x11 wayland"
> DISTRO_FEATURES_append = " systemd"
> VIRTUAL-RUNTIME_init_manager = "systemd"
> IMAGE_INSTALL += "packagegroup-core-buildessential"
>
> changes in bblayers.conf
> BBLAYERS ?= " \
> ${BSPDIR}/sources/poky/meta \
> ${BSPDIR}/sources/poky/meta-poky \
> ${BSPDIR}/sources/poky/meta-yocto-bsp \
> ${BSPDIR}/sources/meta-openembedded/meta-oe \
> ${BSPDIR}/sources/meta-openembedded/meta-multimedia \
> ${BSPDIR}/sources/meta-raspberrypi \
>
> bitbake linux-raspberrypi -c menuconfig
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [PATCH v2] devtool: add clean command
Add an idiomatic way to devtool to clean a recipe. When using devtool
in the context of an eSDK there is no direct access to bitbake.
This command exposes the bitbake clean facility through devtool,
keeping the idiomatic interface and configurability.
Signed-off-by: Josef Holzmayr
---
scripts/lib/devtool/clean.py | 48
1 file changed, 48 insertions(+)
create mode 100644 scripts/lib/devtool/clean.py
diff --git a/scripts/lib/devtool/clean.py b/scripts/lib/devtool/clean.py
new file mode 100644
index 00..473c30f366
--- /dev/null
+++ b/scripts/lib/devtool/clean.py
@@ -0,0 +1,48 @@
+# Development tool - clean command plugin
+#
+# Copyright (C) 2014-2015 Intel Corporation
+# 2017 R-S-I Elektrotechnik GmbH & Co. KG
+#
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License version 2 as
+# published by the Free Software Foundation.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License along
+# with this program; if not, write to the Free Software Foundation, Inc.,
+# 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
+"""Devtool clean plugin"""
+
+import bb
+from devtool import exec_build_env_command, check_workspace_recipe
+
+def _get_clean_tasks(config):
+tasks = config.get('Clean', 'clean_task', 'clean').split(',')
+return ['do_%s' % task.strip() for task in tasks]
+
+def clean(args, config, basepath, workspace):
+"""Entry point for the devtool 'clean' subcommand"""
+
+build_tasks = _get_clean_tasks(config)
+try:
+bbargs = []
+for task in build_tasks:
+bbargs.append('%s:%s' % (args.recipename, task))
+exec_build_env_command(config.init_path, basepath, 'bitbake %s' % '
'.join(bbargs), watch=True)
+except bb.process.ExecutionError as e:
+# We've already seen the output since watch=True, so just ensure we
return something to the user
+return e.exitcode
+
+return 0
+
+def register_commands(subparsers, context):
+"""Register devtool subcommands from this plugin"""
+parser_build = subparsers.add_parser('clean', help='Clean a recipe',
+ description='Cleans the specified
recipe using bitbake',
+ group='working', order=50)
+parser_build.add_argument('recipename', help='Recipe to clean')
+parser_build.set_defaults(func=clean)
--
2.14.3
--
_
R-S-I Elektrotechnik GmbH & Co. KG
Woelkestrasse 11
D-85301 Schweitenkirchen
Fon: +49 8444 9204-0
Fax: +49 8444 9204-50
www.rsi-elektrotechnik.de
_
Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
USt-IdNr.: DE 128592548
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] build error on raspberrypi3
On Thu, Oct 26, 2017 at 4:59 AM, vishal ashapur wrote:
> hi im buliding linux on rpi3 using yocto pyro branch. after doing
> "bitbake linux-raspberrypi -c menuconfig" it is downloading all
> sources but at the end it is showing the following error.
>
> ERROR: linux-raspberrypi-1_4.9.30+gitAUTOINC+e54215a9bc-r28 do_fetch:
> Fetcher failure for URL:
> 'git://github.com/raspberrypi/linux.git;protocol=git;branch=rpi-4.9.y'.
> Unable to fetch URL from any source.
> ERROR: linux-raspberrypi-1_4.9.30+gitAUTOINC+e54215a9bc-r28 do_fetch:
> Function failed: base_do_fetch
> ERROR: Logfile of failure stored in:
> /u/rpi2/rpi/build/tmp/work/raspberrypi2-poky-linux-gnueabi/linux-raspberrypi/1_4.9.30+gitAUTOINC+e54215a9bc-r28/temp/log.do_fetch.30856
> ERROR: Task
> (/u/rpi2/sources/poky-morty/meta-raspberrypi/recipes-kernel/linux/linux-raspberrypi_4.9.bb:do_fetch)
> failed with exit code '1'
This looks wrong. We went straight from 4.9.27 to 4.9.30 in
meta-raspberrypi so not sure where your recipe is coming from. The
latest kernel version on the pyro branch is 4.9.50.
>
> so can anybody help with this error.
> my detailed procedure for build is below
> git clone -b pyro git://git.yoctoproject.org/poky
> cd poky
> git clone -b pyro git://git.openembedded.org/meta-openembedded
> git clone -b pyro git://git.yoctoproject.org/meta-raspberrypi
>
> source sources/poky/oe-init-build-env rpi-build
>
> changes in local.conf
> MACHINE = "raspberrypi3"
> PREFERRED_VERSION_linux-raspberrypi = "4.9.%"
> DISTRO_FEATURES_remove = "x11 wayland"
> DISTRO_FEATURES_append = " systemd"
> VIRTUAL-RUNTIME_init_manager = "systemd"
> IMAGE_INSTALL += "packagegroup-core-buildessential"
>
> changes in bblayers.conf
> BBLAYERS ?= " \
> ${BSPDIR}/sources/poky/meta \
> ${BSPDIR}/sources/poky/meta-poky \
> ${BSPDIR}/sources/poky/meta-yocto-bsp \
> ${BSPDIR}/sources/meta-openembedded/meta-oe \
> ${BSPDIR}/sources/meta-openembedded/meta-multimedia \
> ${BSPDIR}/sources/meta-raspberrypi \
These paths might be wrong, from your commands above the
meta-openembedded and meta-raspberrypi directories would be placed
under the poky directory.
--
Paul Barker
Togán Labs Ltd
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] How to disable dropbear start on boot
Hello, we have a Yocto 2.2 image with image-feature read-only-rootfs and ssh-server-dropbear. On every boot dropbear starts and generates keys in /var/lib/dropbear/ . We like to enable dropbear on demand. How to disable dropbear start on boot? And what ist the preferred way to change DROPBEAR_RSAKEY_DEFAULT? Are there some example dropbear%.bbappend files available? Thank you very much, Bastian. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] How /etc/shadow packed into my final image?
Hello Chen, Very interesting answer you did give on this email thread... I have learned something useful, indeed. :-) I did try what you have suggested on target, but also, out of curiosity, on the host (Fedora 26). And here is what I have on the host (CLI transcript follows): [user@localhost modules]$ uname -r 4.13.8-200.fc26.x86_64 [user@localhost modules]$ rpm -qa | grep shadow shadow-utils-4.3.1-3.fc26.x86_64 [user@localhost modules]$ rpm -q --scripts shadow package shadow is not installed [user@localhost modules]$ rpm -q --scripts shadow-utils [user@localhost modules]$ I was, after all, surprised (expected the same/similar). Any idea why this is different? Should be the same/similar. I'll investigate further the host problem (seems, something/some package is missing/not installed). Thank you, Zoran On Wed, Oct 25, 2017 at 4:53 AM, ChenQi wrote: > On 10/24/2017 07:58 PM, Bacheh Karaji wrote: > > Hi, > > I wanted to modify the content of /etc/shadow, > but don't know how /etc/shadow files is packed into final image. > > Can anybody how it is packed and way to modify it? > Thanks > > > > > > The file is created in postinst of the shadow package. > > Codes are like below: > root@qemux86-64:~# rpm -q --scripts shadow > postinstall scriptlet (using /bin/sh): > # shadow - postinst > if [ "x$D" != "x" ]; then > rootarg="--root $D" > else > rootarg="" > fi > > pwconv $rootarg || exit 1 > grpconv $rootarg || exit 1 > [snip] > > There are several ways to modify the file, depending on your purpose. > If you just want to modify/add/delete user/group in recipe, please try to > make use of useradd*.bbclass. > http://www.yoctoproject.org/docs/2.3.2/mega-manual/mega- > manual.html#ref-classes-useradd > > If you want to do user/group operation in conf file, please try to make > use of extrausers.bbclass. > http://www.yoctoproject.org/docs/2.3.2/mega-manual/mega- > manual.html#ref-classes-extrausers > > The above should be basically enough. > > Best Regards, > Chen Qi > > > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [PATCH v2] devtool: add clean command
Josef, as Paul mentioned, this is a openembedded-core patch and should
be sent to the proper mailing list.
Great that you included the reason of this patch on the description,
otherwise I saw no real benefit from this change.
Leo
On Thu, Oct 26, 2017 at 2:22 AM, Josef Holzmayr
wrote:
Add an idiomatic way to devtool to clean a recipe. When using devtool
in the context of an eSDK there is no direct access to bitbake.
This command exposes the bitbake clean facility through devtool,
keeping the idiomatic interface and configurability.
Signed-off-by: Josef Holzmayr
---
scripts/lib/devtool/clean.py | 48
1 file changed, 48 insertions(+)
create mode 100644 scripts/lib/devtool/clean.py
diff --git a/scripts/lib/devtool/clean.py
b/scripts/lib/devtool/clean.py
new file mode 100644
index 00..473c30f366
--- /dev/null
+++ b/scripts/lib/devtool/clean.py
@@ -0,0 +1,48 @@
+# Development tool - clean command plugin
+#
+# Copyright (C) 2014-2015 Intel Corporation
+# 2017 R-S-I Elektrotechnik GmbH & Co. KG
+#
+# This program is free software; you can redistribute it and/or
modify
+# it under the terms of the GNU General Public License version 2 as
+# published by the Free Software Foundation.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
along
+# with this program; if not, write to the Free Software Foundation,
Inc.,
+# 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
+"""Devtool clean plugin"""
+
+import bb
+from devtool import exec_build_env_command, check_workspace_recipe
+
+def _get_clean_tasks(config):
+tasks = config.get('Clean', 'clean_task', 'clean').split(',')
+return ['do_%s' % task.strip() for task in tasks]
+
+def clean(args, config, basepath, workspace):
+"""Entry point for the devtool 'clean' subcommand"""
+
+build_tasks = _get_clean_tasks(config)
+try:
+bbargs = []
+for task in build_tasks:
+bbargs.append('%s:%s' % (args.recipename, task))
+exec_build_env_command(config.init_path, basepath, 'bitbake
%s' % ' '.join(bbargs), watch=True)
+except bb.process.ExecutionError as e:
+# We've already seen the output since watch=True, so just
ensure we return something to the user
+return e.exitcode
+
+return 0
+
+def register_commands(subparsers, context):
+"""Register devtool subcommands from this plugin"""
+parser_build = subparsers.add_parser('clean', help='Clean a
recipe',
+ description='Cleans the
specified recipe using bitbake',
+ group='working', order=50)
+parser_build.add_argument('recipename', help='Recipe to clean')
+parser_build.set_defaults(func=clean)
--
2.14.3
--
_
R-S-I Elektrotechnik GmbH & Co. KG
Woelkestrasse 11
D-85301 Schweitenkirchen
Fon: +49 8444 9204-0
Fax: +49 8444 9204-50
www.rsi-elektrotechnik.de
_
Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363
Geschftsfhrer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
USt-IdNr.: DE 128592548
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [ANNOUNCEMENT] Yocto Project 2.4 (rocko 18.0.0) Released
Hello, The latest release of the Yocto Project 2.4 (rocko-18.0.0) is now available for download at: http://downloads.yoctoproject.org/releases/yocto/yocto-2.4/poky-rocko-18.0.0.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.4/poky-rocko-18.0.0.tar.bz2 A gpg signed version of these release notes is available at: http://downloads.yoctoproject.org/releases/yocto/yocto-2.4/RELEASENOTES Full pass test report is available at: https://wiki.yoctoproject.org/wiki/WW43_-_2017-10-23_-_Full_Test_Cycle_2.4_RC3 Thank you to everyone for all your hard work on this release! Sincerely, Tracy Graydon Yocto Project Build and Release tracy.gray...@intel.com --- yocto-2.4 Errata --- Release Name: eclipse-poky-mars-rocko-18.0.0 Branch: mars/rocko Tag: mars/rocko-18.0.0 Hash: 92aa0e79e8b01c56f0670af3cd8296ec68b43350 md5: a948420534a1e1eb6c1eb3b5858eb599 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-2.4/eclipse-poky-mars-rocko-18.0.0.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.4/eclipse-poky-mars-rocko-18.0.0.tar.bz2 Release Name: eclipse-poky-neon-rocko-18.0.0 Branch: neon/rocko Tag: neon/rocko-18.0.0 Hash: 83e0083ef3a71e10039ace7d18057dddc154408b md5: 7a47832683c63cd1dd1c82078f886220 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-2.4/eclipse-poky-neon-rocko-18.0.0.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.4/eclipse-poky-neon-rocko-18.0.0.tar.bz2 Release Name: eclipse-poky-oxygen-rocko-18.0.0 Branch: oxygen/rocko Tag: oxygen/rocko-18.0.0 Hash: 126e707a6de212feeaaf093edc170aaa74192ce7 md5: 50c5d209e11d0ae84de6046be8d50d2c Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-2.4/eclipse-poky-oxygen-rocko-18.0.0.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.4/eclipse-poky-oxygen-rocko-18.0.0.tar.bz2 Release Name: meta-qt3-rocko-18.0.0 Branch: rocko Tag: rocko-18.0.0 Hash: f33b73a9563f2dfdfd0ee37b61d65d90197a456f md5: 3755300f0f46b519735bf8be1e022515 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-2.4/meta-qt3-rocko-18.0.0.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.4/meta-qt3-rocko-18.0.0.tar.bz2 Release Name: meta-qt4-rocko-18.0.0 Branch: rocko Tag: rocko-18.0.0 Hash: f313dbee2ac3d5fcc9801407947d3cb6cfb90b5d md5: 5af43b99008f9e33469b98621545cb0d Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-2.4/meta-qt4-rocko-18.0.0.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.4/meta-qt4-rocko-18.0.0.tar.bz2 Release Name: poky-rocko-18.0.0 Branch: rocko Tag: rocko-18.0.0 Hash: 65d23bd7986615fdfb0f1717b615534a2a14ab80 md5: 69f9f9ffcb2a7b7002d625c79eb93763 Download Locations: http://downloads.yoctoproject.org/releases/yocto/yocto-2.4/poky-rocko-18.0.0.tar.bz2 http://mirrors.kernel.org/yocto/yocto/yocto-2.4/poky-rocko-18.0.0.tar.bz2 -- New Features / Enhancements -- * Linux kernel 4.12, 4.10, 4.9 (LTS/LTSI), 4.4 (LTS) * gcc 7.2 * glibc 2.26 * Significant work on binary reproducibility - >98% of packages generated when building core-image-sato are now reproducible. * Support for Vulkan 3D graphics/compute API, enabled by default in poky distro configuration * New "distrooverrides" class to selectively turn DISTRO_FEATURES into overrides (enabling bbappends with functionality conditional upon DISTRO_FEATURES) * New VOLATILE_LOG_DIR variable to allow making /var/log persistent * Support for merged / and /usr with "usrmerge" DISTRO_FEATURES item * Parallelised rpm/ipk/deb package creation for improved performance * Go improvements: - Added Go toolchain support - Added support for ARMv5 targets - Enhancements to go.bbclass for go-based recipes: - Added do_unpack function to handle common cases - Added GO_INSTALL_FILTEROUT variable - Separate source and build directories - Enable parallel build - Use global Go build flags - Split out the Go runtime into a separate go-runtime recipe - Build the Go runtime as a shared library * Python improvements: - python 2 -> 3 migration for bmap-tools, libxml2, opkg-utils, parted. - The main "python3" package now brings in all of the standard Python 3 distribution rather than just a subset, matching the typical expected behaviour based on traditional Linux distributions. * wic image creator enhancements: - New 'wic cp' command to copy files into an ext/vfat partition - New 'wic ls' command to list files in an ext/vfat partition - New 'wic rm' command to delete files in an ext/vfat partition - New 'wic write' command to write an image to a device (e.g. SD card) - New wks option --mkfs-extraopts - Added option to skip changing fstab - Allow multiple /boot partitions with different content - Switch to using --use-uuid by default * devtool/recipetool enhancements: - devtool add now has explicit options to specify source revision and branch when fetching from a repository - devtool deploy-target
