* Regarding build Yocto offline
@ 2018-07-13 8:58 S, Karthikeyan
2018-07-16 8:55 ` Gunnar Andersson
2018-07-16 9:27 ` Burton, Ross
0 siblings, 2 replies; 14+ messages in thread
From: S, Karthikeyan @ 2018-07-13 8:58 UTC (permalink / raw)
To: yocto
[-- Attachment #1: Type: text/plain, Size: 1426 bytes --]
Greetings,
Initially I was able to built with github access, but our requirement is to build offline(without Internet), I followed the steps given in https://wiki.yoctoproject.org/wiki/How_do_I#Q:_How_do_I_create_my_own_source_download_mirror_.3F
I added following lines in conf/local.conf (Git enabled machine)
SOURCE_MIRROR_URL ?= "file:///source_mirror/sources/<file:///\\source_mirror\sources\>"
INHERIT += "own-mirrors"
BB_GENERATE_MIRROR_TARBALLS = "1"
and copied download directory to network disabled system and added following in conf/local.conf(network disabled system).
SOURCE_MIRROR_URL ?= "file:///source_mirror/sources/<file:///\\source_mirror\sources\>"
INHERIT += "own-mirrors"
BB_GENERATE_MIRROR_TARBALLS = "1"
BB_NO_NETWORK = "1"
It was throwing error, saying that "Network is disabled through BB_NO_NETWORK=1" and build was failed. Please share me the exact procedure to build yocto offline.
Thanks & Regards,
Karthik S
________________________________
The information contained in this message is privileged and intended only for the recipients named. If the reader is not a representative of the intended recipient, any review, dissemination or copying of this message or the information it contains is prohibited. If you have received this message in error, please immediately notify the sender, and delete the original message and attachments.
[-- Attachment #2: Type: text/html, Size: 4984 bytes --]
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Regarding build Yocto offline
2018-07-13 8:58 Regarding build Yocto offline S, Karthikeyan
@ 2018-07-16 8:55 ` Gunnar Andersson
2018-07-16 9:01 ` Gunnar GMail
2018-07-16 9:27 ` Burton, Ross
1 sibling, 1 reply; 14+ messages in thread
From: Gunnar Andersson @ 2018-07-16 8:55 UTC (permalink / raw)
To: S, Karthikeyan, yocto
On Fri, 2018-07-13 at 08:58 +0000, S, Karthikeyan wrote:
> Greetings,
> Initially I was able to built with github access, but our
> requirement is to build offline(without Internet), I followed the steps
> given in https://wiki.yoctoproject.org/wiki/How_do_I#Q:_How_do_I_create_my
> _own_source_download_mirror_.3F
> I added following lines in conf/local.conf (Git enabled machine)
> SOURCE_MIRROR_URL ?= "file:///source_mirror/sources/"
> INHERIT += "own-mirrors"
> BB_GENERATE_MIRROR_TARBALLS = "1"
> and copied download directory to network disabled system and added
> following in conf/local.conf(network disabled system).
> SOURCE_MIRROR_URL ?= "file:///source_mirror/sources/"
> INHERIT += "own-mirrors"
> BB_GENERATE_MIRROR_TARBALLS = "1"
> BB_NO_NETWORK = "1"
> It was throwing error, saying that "Network is disabled through
> BB_NO_NETWORK=1" and build was failed. Please share me the exact procedure
> to build yocto offline.
I used to run into this also. Please check, and reply to list, if you are
using a tag in any of the recipes, and if changing to SRCREV=<hash> in all
recipes solves the problem.
Here is a reference to an earlier discussion - I think it is commonly
recurring question. (Maybe you can propose a change to the docs, to
indicate this near the description of the BB_NO_NETWORK variable?)
https://lists.yoctoproject.org/pipermail/yocto/2012-September/009586.html
Hope this helps,
- Gunnar
--
Gunnar Andersson <gandersson@genivi.org>
Development Lead
GENIVI Alliance
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Regarding build Yocto offline
2018-07-16 8:55 ` Gunnar Andersson
@ 2018-07-16 9:01 ` Gunnar GMail
0 siblings, 0 replies; 14+ messages in thread
From: Gunnar GMail @ 2018-07-16 9:01 UTC (permalink / raw)
To: S, Karthikeyan, yocto
On Mon, 2018-07-16 at 10:55 +0200, Gunnar Andersson wrote:
> [trimmed]
> Here is a reference to an earlier discussion - I think it is commonly
> recurring question. (Maybe you can propose a change to the docs, to
> indicate this near the description of the BB_NO_NETWORK variable?)
It seems to already be written in the Wiki you referred to [1]. But I think
it might help to put it also in the official manual.
- Gunnar
[1] https://wiki.yoctoproject.org/wiki/How_do_I#Q:_How_do_I_create_my_own_source_download_mirror_.3F
--
Gunnar Andersson <gandersson@genivi.org>
Development Lead
GENIVI Alliance
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Regarding build Yocto offline
2018-07-13 8:58 Regarding build Yocto offline S, Karthikeyan
2018-07-16 8:55 ` Gunnar Andersson
@ 2018-07-16 9:27 ` Burton, Ross
2018-07-16 9:45 ` S, Karthikeyan
1 sibling, 1 reply; 14+ messages in thread
From: Burton, Ross @ 2018-07-16 9:27 UTC (permalink / raw)
To: S, Karthikeyan; +Cc: yocto
What recipe is failing? It's most likely to be a recipe which is
using a git tag instead of a git hash in the SRCREV.
Ross
On 13 July 2018 at 09:58, S, Karthikeyan <Karthikeyan.S@trane.com> wrote:
> Greetings,
>
> Initially I was able to built with github access, but our
> requirement is to build offline(without Internet), I followed the steps
> given in
> https://wiki.yoctoproject.org/wiki/How_do_I#Q:_How_do_I_create_my_own_source_download_mirror_.3F
>
> I added following lines in conf/local.conf (Git enabled machine)
>
> SOURCE_MIRROR_URL ?= "file:///source_mirror/sources/"
>
> INHERIT += "own-mirrors"
>
> BB_GENERATE_MIRROR_TARBALLS = "1"
>
> and copied download directory to network disabled system and added following
> in conf/local.conf(network disabled system).
>
> SOURCE_MIRROR_URL ?= "file:///source_mirror/sources/"
>
> INHERIT += "own-mirrors"
>
> BB_GENERATE_MIRROR_TARBALLS = "1"
>
> BB_NO_NETWORK = "1"
>
> It was throwing error, saying that "Network is disabled through
> BB_NO_NETWORK=1" and build was failed. Please share me the exact procedure
> to build yocto offline.
>
>
>
>
>
> Thanks & Regards,
>
> Karthik S
>
>
>
>
> ________________________________
>
> The information contained in this message is privileged and intended only
> for the recipients named. If the reader is not a representative of the
> intended recipient, any review, dissemination or copying of this message or
> the information it contains is prohibited. If you have received this message
> in error, please immediately notify the sender, and delete the original
> message and attachments.
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Regarding build Yocto offline
2018-07-16 9:27 ` Burton, Ross
@ 2018-07-16 9:45 ` S, Karthikeyan
2018-07-16 11:13 ` Burton, Ross
0 siblings, 1 reply; 14+ messages in thread
From: S, Karthikeyan @ 2018-07-16 9:45 UTC (permalink / raw)
To: Burton, Ross; +Cc: yocto
[-- Attachment #1: Type: text/plain, Size: 3320 bytes --]
Hi,
Thanks a lot for responding my message even in your busy schedule. As for recipe, it was linux. When I was trying to build entire image "core-image-base", it was failed with "linux kernel recipe". Please find attached linux kernel bb files, all other remaining packages were built successfully.
Thanks,
Karthik
-----Original Message-----
From: Burton, Ross [mailto:ross.burton@intel.com]
Sent: Monday, July 16, 2018 2:57 PM
To: S, Karthikeyan <Karthikeyan.S@trane.com>
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Regarding build Yocto offline
What recipe is failing? It's most likely to be a recipe which is using a git tag instead of a git hash in the SRCREV.
Ross
On 13 July 2018 at 09:58, S, Karthikeyan <Karthikeyan.S@trane.com> wrote:
> Greetings,
>
> Initially I was able to built with github access, but our
> requirement is to build offline(without Internet), I followed the
> steps given in
> https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.yoctoproject
> .org_wiki_How-5Fdo-5FI-23Q-3A-5FHow-5Fdo-5FI-5Fcreate-5Fmy-5Fown-5Fsou
> rce-5Fdownload-5Fmirror-5F.3F&d=DwIBaQ&c=RqOSY-j6o2m72bl3g1aM9A&r=YbS5
> yltng6sM94fh7KTh4S4VmOewJypeQHV1NtdqqQc&m=P2cndFe0OX2zyu8XR1B5rdwBTlbc
> jdT4XVot9clBO6Y&s=25mwi0Mp0X78CdeZtKoVzQ0BeTqLR-q4tn1K0xZcpaU&e=
>
> I added following lines in conf/local.conf (Git enabled machine)
>
> SOURCE_MIRROR_URL ?= "file:///source_mirror/sources/"
>
> INHERIT += "own-mirrors"
>
> BB_GENERATE_MIRROR_TARBALLS = "1"
>
> and copied download directory to network disabled system and added
> following in conf/local.conf(network disabled system).
>
> SOURCE_MIRROR_URL ?= "file:///source_mirror/sources/"
>
> INHERIT += "own-mirrors"
>
> BB_GENERATE_MIRROR_TARBALLS = "1"
>
> BB_NO_NETWORK = "1"
>
> It was throwing error, saying that "Network is disabled through
> BB_NO_NETWORK=1" and build was failed. Please share me the exact
> procedure to build yocto offline.
>
>
>
>
>
> Thanks & Regards,
>
> Karthik S
>
>
>
>
> ________________________________
>
> The information contained in this message is privileged and intended
> only for the recipients named. If the reader is not a representative
> of the intended recipient, any review, dissemination or copying of
> this message or the information it contains is prohibited. If you have
> received this message in error, please immediately notify the sender,
> and delete the original message and attachments.
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.yoctoprojec
> t.org_listinfo_yocto&d=DwIBaQ&c=RqOSY-j6o2m72bl3g1aM9A&r=YbS5yltng6sM94fh7KTh4S4VmOewJypeQHV1NtdqqQc&m=P2cndFe0OX2zyu8XR1B5rdwBTlbcjdT4XVot9clBO6Y&s=u-a0sJKO7HiDC_SADTXL06S-qN7DPan-UYMsYULz_T0&e=
>
________________________________
The information contained in this message is privileged and intended only for the recipients named. If the reader is not a representative of the intended recipient, any review, dissemination or copying of this message or the information it contains is prohibited. If you have received this message in error, please immediately notify the sender, and delete the original message and attachments.
[-- Attachment #2: linux-dey.inc --]
[-- Type: application/octet-stream, Size: 2604 bytes --]
# Copyright (C) 2013-2018 Digi International
SUMMARY = "Linux kernel for Digi boards"
LICENSE = "GPLv2"
LIC_FILES_CHKSUM = "file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7"
DEPENDS += "lzop-native bc-native"
DEPENDS += "${@base_conditional('TRUSTFENCE_SIGN', '1', 'trustfence-sign-tools-native', '', d)}"
inherit kernel fsl-kernel-localversion
LOCALVERSION = "-dey"
# Select internal or Github Linux repo
#LINUX_GIT_URI ?= "${@base_conditional('DIGI_INTERNAL_GIT', '1' , '${DIGI_GIT}linux-2.6.git', '${DIGI_GITHUB_GIT}/linux.git', d)}"
SRC_URI = " \
file:///home/irhpoq/p2project/yocto/downloads/linux-4.9.tar.gz \
file://defconfig \
"
#SRC_URI[md5sum] = "3c15e49e36e1466615ac3511bf9c4a93"
S = "${WORKDIR}/git"
do_deploy[postfuncs] += "${@base_conditional('TRUSTFENCE_SIGN', '1', 'trustfence_sign', '', d)}"
trustfence_sign() {
# Set environment variables for trustfence configuration
export CONFIG_SIGN_KEYS_PATH="${TRUSTFENCE_SIGN_KEYS_PATH}"
[ -n "${TRUSTFENCE_KEY_INDEX}" ] && export CONFIG_KEY_INDEX="${TRUSTFENCE_KEY_INDEX}"
[ -n "${TRUSTFENCE_DEK_PATH}" ] && [ "${TRUSTFENCE_DEK_PATH}" != "0" ] && export CONFIG_DEK_PATH="${TRUSTFENCE_DEK_PATH}"
# Sign/encrypt the kernel images
for type in ${KERNEL_IMAGETYPES}; do
KERNEL_IMAGE="${type}-${KERNEL_IMAGE_BASE_NAME}.bin"
TMP_KERNEL_IMAGE_SIGNED="$(mktemp ${KERNEL_IMAGE}-signed.XXXXXX)"
trustfence-sign-kernel.sh -p "${DIGI_FAMILY}" -l "${KERNEL_IMAGE}" "${TMP_KERNEL_IMAGE_SIGNED}"
mv "${TMP_KERNEL_IMAGE_SIGNED}" "${KERNEL_IMAGE}"
done
# Sign/encrypt the device tree blobs
for DTB in ${KERNEL_DEVICETREE}; do
DTB=`normalize_dtb "${DTB}"`
DTB_EXT=${DTB##*.}
DTB_BASE_NAME=`basename ${DTB} ."${DTB_EXT}"`
for type in ${KERNEL_IMAGETYPES}; do
DTB_IMAGE="$(echo ${type}-${KERNEL_IMAGE_BASE_NAME} | sed "s/${MACHINE}/${DTB_BASE_NAME}/g").${DTB_EXT}"
TMP_DTB_IMAGE_SIGNED="$(mktemp ${DTB_IMAGE}-signed.XXXXXX)"
trustfence-sign-kernel.sh -p "${DIGI_FAMILY}" -d "${DTB_IMAGE}" "${TMP_DTB_IMAGE_SIGNED}"
mv "${TMP_DTB_IMAGE_SIGNED}" "${DTB_IMAGE}"
done
done
}
trustfence_sign[dirs] = "${DEPLOYDIR}"
do_deploy[vardeps] += "TRUSTFENCE_SIGN_KEYS_PATH TRUSTFENCE_KEY_INDEX TRUSTFENCE_DEK_PATH"
FILES_kernel-image += "/boot/config-${KERNEL_VERSION}"
# Don't include kernels in standard images
RDEPENDS_kernel-base = ""
[-- Attachment #3: linux-dey_4.9.bb --]
[-- Type: application/octet-stream, Size: 242 bytes --]
# Copyright (C) 2017, 2018 Digi International
require recipes-kernel/linux/linux-dey.inc
#SRCBRANCH = "v4.9/dey-2.4/maint"
#SRCREV = "${AUTOREV}"
#SRCREV = "8885ced062131214448fae056ef453f094303805"
COMPATIBLE_MACHINE = "(ccimx6|ccimx6ul)"
[-- Attachment #4: local.conf --]
[-- Type: application/octet-stream, Size: 10653 bytes --]
#
# This file is your local configuration file and is where all local user settings
# are placed. The comments in this file give some guide to the options a new user
# to the system might want to change but pretty much any configuration option can
# be set in this file. More adventurous users can look at local.conf.extended
# which contains other examples of configuration which can be placed in this file
# but new users likely won't need any of them initially.
#
# Lines starting with the '#' character are commented out and in some cases the
# default values are provided as comments to show people example syntax. Enabling
# the option is a question of removing the # character and making any change to the
# variable as required.
#
# Machine Selection
#
# You need to select a specific machine to target the build with. There are a selection
# of emulated machines available which can boot and run in the QEMU emulator:
#
#MACHINE ?= "qemuarm"
#MACHINE ?= "qemuarm64"
#MACHINE ?= "qemumips"
#MACHINE ?= "qemumips64"
#MACHINE ?= "qemuppc"
#MACHINE ?= "qemux86"
#MACHINE ?= "qemux86-64"
#
# There are also the following hardware board target machines included for
# demonstration purposes:
#
#MACHINE ?= "beaglebone"
#MACHINE ?= "genericx86"
#MACHINE ?= "genericx86-64"
#MACHINE ?= "mpc8315e-rdb"
#MACHINE ?= "edgerouter"
#
# This sets the default machine to be qemux86 if no other machine is selected:
#MACHINE ??= "qemux86"
MACHINE = "ccimx6ulsbc"
#
# Use Digi's internal git repositories
#
#DIGI_INTERNAL_GIT ?= "1"
#
# Where to place downloads
#
# During a first build the system will download many different source code tarballs
# from various upstream projects. This can take a while, particularly if your network
# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you
# can preserve this directory to speed up this part of subsequent builds. This directory
# is safe to share between multiple builds on the same machine too.
#
# The default is a downloads directory under TOPDIR which is the build directory.
#
DL_DIR ?= "${TOPDIR}/downloads"
#
# Where to place shared-state files
#
# BitBake has the capability to accelerate builds based on previously built output.
# This is done using "shared state" files which can be thought of as cache objects
# and this option determines where those files are placed.
#
# You can wipe out TMPDIR leaving this directory intact and the build would regenerate
# from these files if no changes were made to the configuration. If changes were made
# to the configuration, only shared state files where the state was still valid would
# be used (done using checksums).
#
# The default is a sstate-cache directory under TOPDIR.
#
SSTATE_DIR ?= "${TOPDIR}/sstate-cache"
#
# Where to place the build output
#
# This option specifies where the bulk of the building work should be done and
# where BitBake should place its temporary files and output. Keep in mind that
# this includes the extraction and compilation of many applications and the toolchain
# which can use Gigabytes of hard disk space.
#
# The default is a tmp directory under TOPDIR.
#
TMPDIR = "${TOPDIR}/tmp"
#
# Default policy config
#
# The distribution setting controls which policy settings are used as defaults.
# The default value is fine for general Yocto project use, at least initially.
# Ultimately when creating custom policy, people will likely end up subclassing
# these defaults.
#
DISTRO ?= "dey"
# As an example of a subclass there is a "bleeding" edge policy configuration
# where many versions are set to the absolute latest code from the upstream
# source control systems. This is just mentioned here as an example, its not
# useful to most new users.
# DISTRO ?= "poky-bleeding"
#
# Package Management configuration
#
# This variable lists which packaging formats to enable. Multiple package backends
# can be enabled at once and the first item listed in the variable will be used
# to generate the root filesystems.
# Options are:
# - 'package_deb' for debian style deb files
# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager)
# - 'package_rpm' for rpm style packages
# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk"
# We default to rpm:
PACKAGE_CLASSES ?= "package_rpm"
#
# SDK target architecture
#
# This variable specifies the architecture to build SDK items for and means
# you can build the SDK packages for architectures other than the machine you are
# running the build on (i.e. building i686 packages on an x86_64 host).
# Supported values are i686 and x86_64
#SDKMACHINE ?= "i686"
#
# Extra image configuration defaults
#
# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated
# images. Some of these options are added to certain image types automatically. The
# variable can contain the following options:
# "dbg-pkgs" - add -dbg packages for all installed packages
# (adds symbol information for debugging/profiling)
# "dev-pkgs" - add -dev packages for all installed packages
# (useful if you want to develop against libs in the image)
# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages
# (useful if you want to run the package test suites)
# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.)
# "tools-debug" - add debugging tools (gdb, strace)
# "eclipse-debug" - add Eclipse remote debugging support
# "tools-profile" - add profiling tools (oprofile, lttng, valgrind)
# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.)
# "debug-tweaks" - make an image suitable for development
# e.g. ssh root access has a blank password
# There are other application targets that can be used here too, see
# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details.
# We default to enabling the debugging tweaks.
EXTRA_IMAGE_FEATURES ?= "debug-tweaks"
#
# Additional image features
#
# The following is a list of additional classes to use when building images which
# enable extra features. Some available options which can be included in this variable
# are:
# - 'buildstats' collect build statistics
# - 'image-mklibs' to reduce shared library files size for an image
# - 'image-prelink' in order to prelink the filesystem image
# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink
# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended
USER_CLASSES ?= "buildstats image-mklibs image-prelink"
#
# Runtime testing of images
#
# The build system can test booting virtual machine images under qemu (an emulator)
# after any root filesystems are created and run tests against those images. To
# enable this uncomment this line. See classes/testimage(-auto).bbclass for
# further details.
#TEST_IMAGE = "1"
#
# Interactive shell configuration
#
# Under certain circumstances the system may need input from you and to do this it
# can launch an interactive shell. It needs to do this since the build is
# multithreaded and needs to be able to handle the case where more than one parallel
# process may require the user's attention. The default is iterate over the available
# terminal types to find one that works.
#
# Examples of the occasions this may happen are when resolving patches which cannot
# be applied, to use the devshell or the kernel menuconfig
#
# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none
# Note: currently, Konsole support only works for KDE 3.x due to the way
# newer Konsole versions behave
#OE_TERMINAL = "auto"
# By default disable interactive patch resolution (tasks will just fail instead):
PATCHRESOLVE = "noop"
#
# Disk Space Monitoring during the build
#
# Monitor the disk space during the build. If there is less that 1GB of space or less
# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully
# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort
# of the build. The reason for this is that running completely out of space can corrupt
# files and damages the build in ways which may not be easily recoverable.
# It's necesary to monitor /tmp, if there is no space left the build will fail
# with very exotic errors.
BB_DISKMON_DIRS = "\
STOPTASKS,${TMPDIR},1G,100K \
STOPTASKS,${DL_DIR},1G,100K \
STOPTASKS,${SSTATE_DIR},1G,100K \
STOPTASKS,/tmp,100M,100K \
ABORT,${TMPDIR},100M,1K \
ABORT,${DL_DIR},100M,1K \
ABORT,${SSTATE_DIR},100M,1K \
ABORT,/tmp,10M,1K"
#
# Shared-state files from other locations
#
# As mentioned above, shared state files are prebuilt cache data objects which can
# used to accelerate build time. This variable can be used to configure the system
# to search other mirror locations for these objects before it builds the data itself.
#
# This can be a filesystem directory, or a remote url such as http or ftp. These
# would contain the sstate-cache results from previous builds (possibly from other
# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the
# cache locations to check for the shared objects.
# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH
# at the end as shown in the examples below. This will be substituted with the
# correct path within the directory structure.
#SSTATE_MIRRORS ?= "\
#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \
#file://.* file:///some/local/dir/sstate/PATH"
#
# Qemu configuration
#
# By default qemu will build with a builtin VNC server where graphical output can be
# seen. The two lines below enable the SDL backend too. By default libsdl-native will
# be built, if you want to use your host's libSDL instead of the minimal libsdl built
# by libsdl-native then uncomment the ASSUME_PROVIDED line below.
PACKAGECONFIG_append_pn-qemu-native = " sdl"
PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl"
#ASSUME_PROVIDED += "libsdl-native"
# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to
# track the version of this file when it was generated. This can safely be ignored if
# this doesn't mean anything to you.
CONF_VERSION = "1"
SOURCE_MIRROR_URL = "file:///home/irhpoq/yocto_build/downloads/"
INHERIT += "own-mirrors"
BB_GENERATE_MIRROR_TARBALLS = "1"
BB_NUMBER_THREADS ?= "12"
PARALLEL_MAKE ?= "-j 8"
BB_NO_NETWORK = "1"
#
# Enable local PR server
#
PRSERV_HOST = "localhost:0"
#
# Some libraries and packages are covered by NXP EULA
#
ACCEPT_FSL_EULA = "1"
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Regarding build Yocto offline
2018-07-16 9:45 ` S, Karthikeyan
@ 2018-07-16 11:13 ` Burton, Ross
2018-07-16 11:17 ` S, Karthikeyan
0 siblings, 1 reply; 14+ messages in thread
From: Burton, Ross @ 2018-07-16 11:13 UTC (permalink / raw)
To: S, Karthikeyan; +Cc: yocto
Logs, please.
Ross
On 16 July 2018 at 10:45, S, Karthikeyan <Karthikeyan.S@trane.com> wrote:
> Hi,
> Thanks a lot for responding my message even in your busy schedule. As for recipe, it was linux. When I was trying to build entire image "core-image-base", it was failed with "linux kernel recipe". Please find attached linux kernel bb files, all other remaining packages were built successfully.
>
> Thanks,
> Karthik
>
> -----Original Message-----
> From: Burton, Ross [mailto:ross.burton@intel.com]
> Sent: Monday, July 16, 2018 2:57 PM
> To: S, Karthikeyan <Karthikeyan.S@trane.com>
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] Regarding build Yocto offline
>
> What recipe is failing? It's most likely to be a recipe which is using a git tag instead of a git hash in the SRCREV.
>
> Ross
>
> On 13 July 2018 at 09:58, S, Karthikeyan <Karthikeyan.S@trane.com> wrote:
>> Greetings,
>>
>> Initially I was able to built with github access, but our
>> requirement is to build offline(without Internet), I followed the
>> steps given in
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.yoctoproject
>> .org_wiki_How-5Fdo-5FI-23Q-3A-5FHow-5Fdo-5FI-5Fcreate-5Fmy-5Fown-5Fsou
>> rce-5Fdownload-5Fmirror-5F.3F&d=DwIBaQ&c=RqOSY-j6o2m72bl3g1aM9A&r=YbS5
>> yltng6sM94fh7KTh4S4VmOewJypeQHV1NtdqqQc&m=P2cndFe0OX2zyu8XR1B5rdwBTlbc
>> jdT4XVot9clBO6Y&s=25mwi0Mp0X78CdeZtKoVzQ0BeTqLR-q4tn1K0xZcpaU&e=
>>
>> I added following lines in conf/local.conf (Git enabled machine)
>>
>> SOURCE_MIRROR_URL ?= "file:///source_mirror/sources/"
>>
>> INHERIT += "own-mirrors"
>>
>> BB_GENERATE_MIRROR_TARBALLS = "1"
>>
>> and copied download directory to network disabled system and added
>> following in conf/local.conf(network disabled system).
>>
>> SOURCE_MIRROR_URL ?= "file:///source_mirror/sources/"
>>
>> INHERIT += "own-mirrors"
>>
>> BB_GENERATE_MIRROR_TARBALLS = "1"
>>
>> BB_NO_NETWORK = "1"
>>
>> It was throwing error, saying that "Network is disabled through
>> BB_NO_NETWORK=1" and build was failed. Please share me the exact
>> procedure to build yocto offline.
>>
>>
>>
>>
>>
>> Thanks & Regards,
>>
>> Karthik S
>>
>>
>>
>>
>> ________________________________
>>
>> The information contained in this message is privileged and intended
>> only for the recipients named. If the reader is not a representative
>> of the intended recipient, any review, dissemination or copying of
>> this message or the information it contains is prohibited. If you have
>> received this message in error, please immediately notify the sender,
>> and delete the original message and attachments.
>>
>> --
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.yoctoprojec
>> t.org_listinfo_yocto&d=DwIBaQ&c=RqOSY-j6o2m72bl3g1aM9A&r=YbS5yltng6sM94fh7KTh4S4VmOewJypeQHV1NtdqqQc&m=P2cndFe0OX2zyu8XR1B5rdwBTlbcjdT4XVot9clBO6Y&s=u-a0sJKO7HiDC_SADTXL06S-qN7DPan-UYMsYULz_T0&e=
>>
>
> ________________________________
>
> The information contained in this message is privileged and intended only for the recipients named. If the reader is not a representative of the intended recipient, any review, dissemination or copying of this message or the information it contains is prohibited. If you have received this message in error, please immediately notify the sender, and delete the original message and attachments.
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Regarding build Yocto offline
2018-07-16 11:13 ` Burton, Ross
@ 2018-07-16 11:17 ` S, Karthikeyan
2018-07-16 11:25 ` Burton, Ross
0 siblings, 1 reply; 14+ messages in thread
From: S, Karthikeyan @ 2018-07-16 11:17 UTC (permalink / raw)
To: Burton, Ross; +Cc: yocto
[-- Attachment #1: Type: text/plain, Size: 4389 bytes --]
Hi Ross,
Sorry, I don’t have log file, I am attaching screenshot here and please let me know how to get log files
Thanks & Regards,
Karthik S
-----Original Message-----
From: Burton, Ross [mailto:ross.burton@intel.com]
Sent: Monday, July 16, 2018 4:44 PM
To: S, Karthikeyan <Karthikeyan.S@trane.com>
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Regarding build Yocto offline
Logs, please.
Ross
On 16 July 2018 at 10:45, S, Karthikeyan <Karthikeyan.S@trane.com> wrote:
> Hi,
> Thanks a lot for responding my message even in your busy schedule. As for recipe, it was linux. When I was trying to build entire image "core-image-base", it was failed with "linux kernel recipe". Please find attached linux kernel bb files, all other remaining packages were built successfully.
>
> Thanks,
> Karthik
>
> -----Original Message-----
> From: Burton, Ross [mailto:ross.burton@intel.com]
> Sent: Monday, July 16, 2018 2:57 PM
> To: S, Karthikeyan <Karthikeyan.S@trane.com>
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] Regarding build Yocto offline
>
> What recipe is failing? It's most likely to be a recipe which is using a git tag instead of a git hash in the SRCREV.
>
> Ross
>
> On 13 July 2018 at 09:58, S, Karthikeyan <Karthikeyan.S@trane.com> wrote:
>> Greetings,
>>
>> Initially I was able to built with github access, but
>> our requirement is to build offline(without Internet), I followed the
>> steps given in
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.yoctoprojec
>> t
>> .org_wiki_How-5Fdo-5FI-23Q-3A-5FHow-5Fdo-5FI-5Fcreate-5Fmy-5Fown-5Fso
>> u
>> rce-5Fdownload-5Fmirror-5F.3F&d=DwIBaQ&c=RqOSY-j6o2m72bl3g1aM9A&r=YbS
>> 5
>> yltng6sM94fh7KTh4S4VmOewJypeQHV1NtdqqQc&m=P2cndFe0OX2zyu8XR1B5rdwBTlb
>> c jdT4XVot9clBO6Y&s=25mwi0Mp0X78CdeZtKoVzQ0BeTqLR-q4tn1K0xZcpaU&e=
>>
>> I added following lines in conf/local.conf (Git enabled machine)
>>
>> SOURCE_MIRROR_URL ?= "file:///source_mirror/sources/"
>>
>> INHERIT += "own-mirrors"
>>
>> BB_GENERATE_MIRROR_TARBALLS = "1"
>>
>> and copied download directory to network disabled system and added
>> following in conf/local.conf(network disabled system).
>>
>> SOURCE_MIRROR_URL ?= "file:///source_mirror/sources/"
>>
>> INHERIT += "own-mirrors"
>>
>> BB_GENERATE_MIRROR_TARBALLS = "1"
>>
>> BB_NO_NETWORK = "1"
>>
>> It was throwing error, saying that "Network is disabled through
>> BB_NO_NETWORK=1" and build was failed. Please share me the exact
>> procedure to build yocto offline.
>>
>>
>>
>>
>>
>> Thanks & Regards,
>>
>> Karthik S
>>
>>
>>
>>
>> ________________________________
>>
>> The information contained in this message is privileged and intended
>> only for the recipients named. If the reader is not a representative
>> of the intended recipient, any review, dissemination or copying of
>> this message or the information it contains is prohibited. If you
>> have received this message in error, please immediately notify the
>> sender, and delete the original message and attachments.
>>
>> --
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.yoctoproje
>> c
>> t.org_listinfo_yocto&d=DwIBaQ&c=RqOSY-j6o2m72bl3g1aM9A&r=YbS5yltng6sM
>> 94fh7KTh4S4VmOewJypeQHV1NtdqqQc&m=P2cndFe0OX2zyu8XR1B5rdwBTlbcjdT4XVo
>> t9clBO6Y&s=u-a0sJKO7HiDC_SADTXL06S-qN7DPan-UYMsYULz_T0&e=
>>
>
> ________________________________
>
> The information contained in this message is privileged and intended only for the recipients named. If the reader is not a representative of the intended recipient, any review, dissemination or copying of this message or the information it contains is prohibited. If you have received this message in error, please immediately notify the sender, and delete the original message and attachments.
________________________________
The information contained in this message is privileged and intended only for the recipients named. If the reader is not a representative of the intended recipient, any review, dissemination or copying of this message or the information it contains is prohibited. If you have received this message in error, please immediately notify the sender, and delete the original message and attachments.
[-- Attachment #2: Bitbake error.JPG --]
[-- Type: image/jpeg, Size: 128664 bytes --]
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Regarding build Yocto offline
2018-07-16 11:17 ` S, Karthikeyan
@ 2018-07-16 11:25 ` Burton, Ross
2018-07-16 12:00 ` S, Karthikeyan
2018-07-16 12:04 ` S, Karthikeyan
0 siblings, 2 replies; 14+ messages in thread
From: Burton, Ross @ 2018-07-16 11:25 UTC (permalink / raw)
To: S, Karthikeyan; +Cc: yocto
That build is not building that recipe, because the recipe you've
attached has SRC_URI=a local file, but the log clearly shows it going
to github.
Assuming you're actually using the original version of the recipe and
not the edited version you sent, then the problem is that the recipe
has SRCREV=${AUTOREV}, which means "always go and get the latest
revision". This is obviously incompatible with offline builds, so
you'll want to replace that with a specific SHA to build (as this is
an old kernel, the SHA of the branch will be sufficient).
Ross
On 16 July 2018 at 12:17, S, Karthikeyan <Karthikeyan.S@trane.com> wrote:
> Hi Ross,
> Sorry, I don’t have log file, I am attaching screenshot here and please let me know how to get log files
>
>
> Thanks & Regards,
> Karthik S
>
>
>
> -----Original Message-----
> From: Burton, Ross [mailto:ross.burton@intel.com]
> Sent: Monday, July 16, 2018 4:44 PM
> To: S, Karthikeyan <Karthikeyan.S@trane.com>
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] Regarding build Yocto offline
>
> Logs, please.
>
> Ross
>
> On 16 July 2018 at 10:45, S, Karthikeyan <Karthikeyan.S@trane.com> wrote:
>> Hi,
>> Thanks a lot for responding my message even in your busy schedule. As for recipe, it was linux. When I was trying to build entire image "core-image-base", it was failed with "linux kernel recipe". Please find attached linux kernel bb files, all other remaining packages were built successfully.
>>
>> Thanks,
>> Karthik
>>
>> -----Original Message-----
>> From: Burton, Ross [mailto:ross.burton@intel.com]
>> Sent: Monday, July 16, 2018 2:57 PM
>> To: S, Karthikeyan <Karthikeyan.S@trane.com>
>> Cc: yocto@yoctoproject.org
>> Subject: Re: [yocto] Regarding build Yocto offline
>>
>> What recipe is failing? It's most likely to be a recipe which is using a git tag instead of a git hash in the SRCREV.
>>
>> Ross
>>
>> On 13 July 2018 at 09:58, S, Karthikeyan <Karthikeyan.S@trane.com> wrote:
>>> Greetings,
>>>
>>> Initially I was able to built with github access, but
>>> our requirement is to build offline(without Internet), I followed the
>>> steps given in
>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.yoctoprojec
>>> t
>>> .org_wiki_How-5Fdo-5FI-23Q-3A-5FHow-5Fdo-5FI-5Fcreate-5Fmy-5Fown-5Fso
>>> u
>>> rce-5Fdownload-5Fmirror-5F.3F&d=DwIBaQ&c=RqOSY-j6o2m72bl3g1aM9A&r=YbS
>>> 5
>>> yltng6sM94fh7KTh4S4VmOewJypeQHV1NtdqqQc&m=P2cndFe0OX2zyu8XR1B5rdwBTlb
>>> c jdT4XVot9clBO6Y&s=25mwi0Mp0X78CdeZtKoVzQ0BeTqLR-q4tn1K0xZcpaU&e=
>>>
>>> I added following lines in conf/local.conf (Git enabled machine)
>>>
>>> SOURCE_MIRROR_URL ?= "file:///source_mirror/sources/"
>>>
>>> INHERIT += "own-mirrors"
>>>
>>> BB_GENERATE_MIRROR_TARBALLS = "1"
>>>
>>> and copied download directory to network disabled system and added
>>> following in conf/local.conf(network disabled system).
>>>
>>> SOURCE_MIRROR_URL ?= "file:///source_mirror/sources/"
>>>
>>> INHERIT += "own-mirrors"
>>>
>>> BB_GENERATE_MIRROR_TARBALLS = "1"
>>>
>>> BB_NO_NETWORK = "1"
>>>
>>> It was throwing error, saying that "Network is disabled through
>>> BB_NO_NETWORK=1" and build was failed. Please share me the exact
>>> procedure to build yocto offline.
>>>
>>>
>>>
>>>
>>>
>>> Thanks & Regards,
>>>
>>> Karthik S
>>>
>>>
>>>
>>>
>>> ________________________________
>>>
>>> The information contained in this message is privileged and intended
>>> only for the recipients named. If the reader is not a representative
>>> of the intended recipient, any review, dissemination or copying of
>>> this message or the information it contains is prohibited. If you
>>> have received this message in error, please immediately notify the
>>> sender, and delete the original message and attachments.
>>>
>>> --
>>> _______________________________________________
>>> yocto mailing list
>>> yocto@yoctoproject.org
>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.yoctoproje
>>> c
>>> t.org_listinfo_yocto&d=DwIBaQ&c=RqOSY-j6o2m72bl3g1aM9A&r=YbS5yltng6sM
>>> 94fh7KTh4S4VmOewJypeQHV1NtdqqQc&m=P2cndFe0OX2zyu8XR1B5rdwBTlbcjdT4XVo
>>> t9clBO6Y&s=u-a0sJKO7HiDC_SADTXL06S-qN7DPan-UYMsYULz_T0&e=
>>>
>>
>> ________________________________
>>
>> The information contained in this message is privileged and intended only for the recipients named. If the reader is not a representative of the intended recipient, any review, dissemination or copying of this message or the information it contains is prohibited. If you have received this message in error, please immediately notify the sender, and delete the original message and attachments.
>
> ________________________________
>
> The information contained in this message is privileged and intended only for the recipients named. If the reader is not a representative of the intended recipient, any review, dissemination or copying of this message or the information it contains is prohibited. If you have received this message in error, please immediately notify the sender, and delete the original message and attachments.
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Regarding build Yocto offline
2018-07-16 11:25 ` Burton, Ross
@ 2018-07-16 12:00 ` S, Karthikeyan
2018-07-16 12:04 ` S, Karthikeyan
1 sibling, 0 replies; 14+ messages in thread
From: S, Karthikeyan @ 2018-07-16 12:00 UTC (permalink / raw)
To: Burton, Ross; +Cc: yocto
[-- Attachment #1: Type: text/plain, Size: 7837 bytes --]
Hi Ross,
Actual our requirement is, we should be able to build yocto without internet connection, So what we did was, Initially we made the setup in internet enabled system and it fetches the all the required source to build, So we copied "download", "source", "conf/local.conf" file to internet disabled system to build offline, So, I just had gone through below link to build offline.
https://wiki.yoctoproject.org/wiki/How_do_I#Non-networked_Builds_and_Cached_Git_Respositories
then, "linux-dey-4.9" package was failed due to "BB_NO_NETWORK" was enabled, only this package trying to access the git hub, then I looked in to download directory, there was no such source tar file("linux-dey-4.9.tar") in the download directory, even it was not there in internet enabled system but there it was compiling successfully, the phrase I was looking might be wrong because download directory has most of the file starts with "git.***", So I removed whatever I added recently in conf/local.conf file in internet-disabled system, basically the following lines,
SOURCE_MIRROR_URL = "file:///home/irhpoq/yocto_build/downloads/"
INHERIT += "own-mirrors"
BB_GENERATE_MIRROR_TARBALLS = "1"
BB_NO_NETWORK = "1"
And then build is compiling successfully in internet-disabled system and I would feel that this is not the correct way to build offline, So, Please let me know how to build "linux-dey-4.9" with above lines are added in conf/local.conf file or our build should not check/validate the newer version of any package, it supposed to build whatever files available in download directory. Once we get download the directory, we will make it has our base source file and even if we connect to Internet our build should not download any files from Internet, basically our source files should not get changed by any means, even if it is connected to internet. I am attaching original linux-4.9 bb files as well. Please let me know if you need any additional details.
-----Original Message-----
From: Burton, Ross [mailto:ross.burton@intel.com]
Sent: Monday, July 16, 2018 4:55 PM
To: S, Karthikeyan <Karthikeyan.S@trane.com>
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Regarding build Yocto offline
That build is not building that recipe, because the recipe you've attached has SRC_URI=a local file, but the log clearly shows it going to github.
Assuming you're actually using the original version of the recipe and not the edited version you sent, then the problem is that the recipe has SRCREV=${AUTOREV}, which means "always go and get the latest revision". This is obviously incompatible with offline builds, so you'll want to replace that with a specific SHA to build (as this is an old kernel, the SHA of the branch will be sufficient).
Ross
On 16 July 2018 at 12:17, S, Karthikeyan <Karthikeyan.S@trane.com> wrote:
> Hi Ross,
> Sorry, I don’t have log file, I am attaching screenshot here and
> please let me know how to get log files
>
>
> Thanks & Regards,
> Karthik S
>
>
>
> -----Original Message-----
> From: Burton, Ross [mailto:ross.burton@intel.com]
> Sent: Monday, July 16, 2018 4:44 PM
> To: S, Karthikeyan <Karthikeyan.S@trane.com>
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] Regarding build Yocto offline
>
> Logs, please.
>
> Ross
>
> On 16 July 2018 at 10:45, S, Karthikeyan <Karthikeyan.S@trane.com> wrote:
>> Hi,
>> Thanks a lot for responding my message even in your busy schedule. As for recipe, it was linux. When I was trying to build entire image "core-image-base", it was failed with "linux kernel recipe". Please find attached linux kernel bb files, all other remaining packages were built successfully.
>>
>> Thanks,
>> Karthik
>>
>> -----Original Message-----
>> From: Burton, Ross [mailto:ross.burton@intel.com]
>> Sent: Monday, July 16, 2018 2:57 PM
>> To: S, Karthikeyan <Karthikeyan.S@trane.com>
>> Cc: yocto@yoctoproject.org
>> Subject: Re: [yocto] Regarding build Yocto offline
>>
>> What recipe is failing? It's most likely to be a recipe which is using a git tag instead of a git hash in the SRCREV.
>>
>> Ross
>>
>> On 13 July 2018 at 09:58, S, Karthikeyan <Karthikeyan.S@trane.com> wrote:
>>> Greetings,
>>>
>>> Initially I was able to built with github access, but
>>> our requirement is to build offline(without Internet), I followed
>>> the steps given in
>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.yoctoproje
>>> c
>>> t
>>> .org_wiki_How-5Fdo-5FI-23Q-3A-5FHow-5Fdo-5FI-5Fcreate-5Fmy-5Fown-5Fs
>>> o
>>> u
>>> rce-5Fdownload-5Fmirror-5F.3F&d=DwIBaQ&c=RqOSY-j6o2m72bl3g1aM9A&r=Yb
>>> S
>>> 5
>>> yltng6sM94fh7KTh4S4VmOewJypeQHV1NtdqqQc&m=P2cndFe0OX2zyu8XR1B5rdwBTl
>>> b c jdT4XVot9clBO6Y&s=25mwi0Mp0X78CdeZtKoVzQ0BeTqLR-q4tn1K0xZcpaU&e=
>>>
>>> I added following lines in conf/local.conf (Git enabled machine)
>>>
>>> SOURCE_MIRROR_URL ?= "file:///source_mirror/sources/"
>>>
>>> INHERIT += "own-mirrors"
>>>
>>> BB_GENERATE_MIRROR_TARBALLS = "1"
>>>
>>> and copied download directory to network disabled system and added
>>> following in conf/local.conf(network disabled system).
>>>
>>> SOURCE_MIRROR_URL ?= "file:///source_mirror/sources/"
>>>
>>> INHERIT += "own-mirrors"
>>>
>>> BB_GENERATE_MIRROR_TARBALLS = "1"
>>>
>>> BB_NO_NETWORK = "1"
>>>
>>> It was throwing error, saying that "Network is disabled through
>>> BB_NO_NETWORK=1" and build was failed. Please share me the exact
>>> procedure to build yocto offline.
>>>
>>>
>>>
>>>
>>>
>>> Thanks & Regards,
>>>
>>> Karthik S
>>>
>>>
>>>
>>>
>>> ________________________________
>>>
>>> The information contained in this message is privileged and intended
>>> only for the recipients named. If the reader is not a representative
>>> of the intended recipient, any review, dissemination or copying of
>>> this message or the information it contains is prohibited. If you
>>> have received this message in error, please immediately notify the
>>> sender, and delete the original message and attachments.
>>>
>>> --
>>> _______________________________________________
>>> yocto mailing list
>>> yocto@yoctoproject.org
>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.yoctoproj
>>> e
>>> c
>>> t.org_listinfo_yocto&d=DwIBaQ&c=RqOSY-j6o2m72bl3g1aM9A&r=YbS5yltng6s
>>> M
>>> 94fh7KTh4S4VmOewJypeQHV1NtdqqQc&m=P2cndFe0OX2zyu8XR1B5rdwBTlbcjdT4XV
>>> o t9clBO6Y&s=u-a0sJKO7HiDC_SADTXL06S-qN7DPan-UYMsYULz_T0&e=
>>>
>>
>> ________________________________
>>
>> The information contained in this message is privileged and intended only for the recipients named. If the reader is not a representative of the intended recipient, any review, dissemination or copying of this message or the information it contains is prohibited. If you have received this message in error, please immediately notify the sender, and delete the original message and attachments.
>
> ________________________________
>
> The information contained in this message is privileged and intended only for the recipients named. If the reader is not a representative of the intended recipient, any review, dissemination or copying of this message or the information it contains is prohibited. If you have received this message in error, please immediately notify the sender, and delete the original message and attachments.
________________________________
The information contained in this message is privileged and intended only for the recipients named. If the reader is not a representative of the intended recipient, any review, dissemination or copying of this message or the information it contains is prohibited. If you have received this message in error, please immediately notify the sender, and delete the original message and attachments.
[-- Attachment #2: Bitbake error.JPG --]
[-- Type: image/jpeg, Size: 128664 bytes --]
[-- Attachment #3: linux-dey.inc --]
[-- Type: application/octet-stream, Size: 2604 bytes --]
# Copyright (C) 2013-2018 Digi International
SUMMARY = "Linux kernel for Digi boards"
LICENSE = "GPLv2"
LIC_FILES_CHKSUM = "file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7"
DEPENDS += "lzop-native bc-native"
DEPENDS += "${@base_conditional('TRUSTFENCE_SIGN', '1', 'trustfence-sign-tools-native', '', d)}"
inherit kernel fsl-kernel-localversion
LOCALVERSION = "-dey"
# Select internal or Github Linux repo
#LINUX_GIT_URI ?= "${@base_conditional('DIGI_INTERNAL_GIT', '1' , '${DIGI_GIT}linux-2.6.git', '${DIGI_GITHUB_GIT}/linux.git', d)}"
SRC_URI = " \
file:///home/irhpoq/p2project/yocto/downloads/linux-4.9.tar.gz \
file://defconfig \
"
#SRC_URI[md5sum] = "3c15e49e36e1466615ac3511bf9c4a93"
S = "${WORKDIR}/git"
do_deploy[postfuncs] += "${@base_conditional('TRUSTFENCE_SIGN', '1', 'trustfence_sign', '', d)}"
trustfence_sign() {
# Set environment variables for trustfence configuration
export CONFIG_SIGN_KEYS_PATH="${TRUSTFENCE_SIGN_KEYS_PATH}"
[ -n "${TRUSTFENCE_KEY_INDEX}" ] && export CONFIG_KEY_INDEX="${TRUSTFENCE_KEY_INDEX}"
[ -n "${TRUSTFENCE_DEK_PATH}" ] && [ "${TRUSTFENCE_DEK_PATH}" != "0" ] && export CONFIG_DEK_PATH="${TRUSTFENCE_DEK_PATH}"
# Sign/encrypt the kernel images
for type in ${KERNEL_IMAGETYPES}; do
KERNEL_IMAGE="${type}-${KERNEL_IMAGE_BASE_NAME}.bin"
TMP_KERNEL_IMAGE_SIGNED="$(mktemp ${KERNEL_IMAGE}-signed.XXXXXX)"
trustfence-sign-kernel.sh -p "${DIGI_FAMILY}" -l "${KERNEL_IMAGE}" "${TMP_KERNEL_IMAGE_SIGNED}"
mv "${TMP_KERNEL_IMAGE_SIGNED}" "${KERNEL_IMAGE}"
done
# Sign/encrypt the device tree blobs
for DTB in ${KERNEL_DEVICETREE}; do
DTB=`normalize_dtb "${DTB}"`
DTB_EXT=${DTB##*.}
DTB_BASE_NAME=`basename ${DTB} ."${DTB_EXT}"`
for type in ${KERNEL_IMAGETYPES}; do
DTB_IMAGE="$(echo ${type}-${KERNEL_IMAGE_BASE_NAME} | sed "s/${MACHINE}/${DTB_BASE_NAME}/g").${DTB_EXT}"
TMP_DTB_IMAGE_SIGNED="$(mktemp ${DTB_IMAGE}-signed.XXXXXX)"
trustfence-sign-kernel.sh -p "${DIGI_FAMILY}" -d "${DTB_IMAGE}" "${TMP_DTB_IMAGE_SIGNED}"
mv "${TMP_DTB_IMAGE_SIGNED}" "${DTB_IMAGE}"
done
done
}
trustfence_sign[dirs] = "${DEPLOYDIR}"
do_deploy[vardeps] += "TRUSTFENCE_SIGN_KEYS_PATH TRUSTFENCE_KEY_INDEX TRUSTFENCE_DEK_PATH"
FILES_kernel-image += "/boot/config-${KERNEL_VERSION}"
# Don't include kernels in standard images
RDEPENDS_kernel-base = ""
[-- Attachment #4: linux-dey_4.9.bb --]
[-- Type: application/octet-stream, Size: 242 bytes --]
# Copyright (C) 2017, 2018 Digi International
require recipes-kernel/linux/linux-dey.inc
#SRCBRANCH = "v4.9/dey-2.4/maint"
#SRCREV = "${AUTOREV}"
#SRCREV = "8885ced062131214448fae056ef453f094303805"
COMPATIBLE_MACHINE = "(ccimx6|ccimx6ul)"
[-- Attachment #5: linux-dey.inc.orig --]
[-- Type: application/octet-stream, Size: 2247 bytes --]
# Copyright (C) 2013-2018 Digi International
SUMMARY = "Linux kernel for Digi boards"
LICENSE = "GPLv2"
LIC_FILES_CHKSUM = "file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7"
DEPENDS += "lzop-native bc-native"
DEPENDS += "${@base_conditional('TRUSTFENCE_SIGN', '1', 'trustfence-sign-tools-native', '', d)}"
inherit kernel fsl-kernel-localversion
LOCALVERSION = "-dey"
# Select internal or Github Linux repo
LINUX_GIT_URI ?= "${@base_conditional('DIGI_INTERNAL_GIT', '1' , '${DIGI_GIT}linux-2.6.git', '${DIGI_GITHUB_GIT}/linux.git', d)}"
SRC_URI = " \
${LINUX_GIT_URI};branch=${SRCBRANCH} \
file://defconfig \
"
S = "${WORKDIR}/git"
do_deploy[postfuncs] += "${@base_conditional('TRUSTFENCE_SIGN', '1', 'trustfence_sign', '', d)}"
trustfence_sign() {
# Set environment variables for trustfence configuration
export CONFIG_SIGN_KEYS_PATH="${TRUSTFENCE_SIGN_KEYS_PATH}"
[ -n "${TRUSTFENCE_KEY_INDEX}" ] && export CONFIG_KEY_INDEX="${TRUSTFENCE_KEY_INDEX}"
[ -n "${TRUSTFENCE_DEK_PATH}" ] && [ "${TRUSTFENCE_DEK_PATH}" != "0" ] && export CONFIG_DEK_PATH="${TRUSTFENCE_DEK_PATH}"
# Sign/encrypt the kernel images
for type in ${KERNEL_IMAGETYPES}; do
KERNEL_IMAGE="${type}-${KERNEL_IMAGE_BASE_NAME}.bin"
TMP_KERNEL_IMAGE_SIGNED="$(mktemp ${KERNEL_IMAGE}-signed.XXXXXX)"
trustfence-sign-kernel.sh -p "${DIGI_FAMILY}" -l "${KERNEL_IMAGE}" "${TMP_KERNEL_IMAGE_SIGNED}"
mv "${TMP_KERNEL_IMAGE_SIGNED}" "${KERNEL_IMAGE}"
done
# Sign/encrypt the device tree blobs
for DTB in ${KERNEL_DEVICETREE}; do
DTB=`normalize_dtb "${DTB}"`
DTB_EXT=${DTB##*.}
DTB_BASE_NAME=`basename ${DTB} ."${DTB_EXT}"`
for type in ${KERNEL_IMAGETYPES}; do
DTB_IMAGE="$(echo ${type}-${KERNEL_IMAGE_BASE_NAME} | sed "s/${MACHINE}/${DTB_BASE_NAME}/g").${DTB_EXT}"
TMP_DTB_IMAGE_SIGNED="$(mktemp ${DTB_IMAGE}-signed.XXXXXX)"
trustfence-sign-kernel.sh -p "${DIGI_FAMILY}" -d "${DTB_IMAGE}" "${TMP_DTB_IMAGE_SIGNED}"
mv "${TMP_DTB_IMAGE_SIGNED}" "${DTB_IMAGE}"
done
done
}
trustfence_sign[dirs] = "${DEPLOYDIR}"
do_deploy[vardeps] += "TRUSTFENCE_SIGN_KEYS_PATH TRUSTFENCE_KEY_INDEX TRUSTFENCE_DEK_PATH"
FILES_kernel-image += "/boot/config-${KERNEL_VERSION}"
# Don't include kernels in standard images
RDEPENDS_kernel-base = ""
[-- Attachment #6: linux-dey_4.9.bb.orig --]
[-- Type: application/octet-stream, Size: 188 bytes --]
# Copyright (C) 2017, 2018 Digi International
require recipes-kernel/linux/linux-dey.inc
SRCBRANCH = "v4.9/dey-2.4/maint"
SRCREV = "${AUTOREV}"
COMPATIBLE_MACHINE = "(ccimx6|ccimx6ul)"
[-- Attachment #7: local.conf.orig --]
[-- Type: application/octet-stream, Size: 10509 bytes --]
#
# This file is your local configuration file and is where all local user settings
# are placed. The comments in this file give some guide to the options a new user
# to the system might want to change but pretty much any configuration option can
# be set in this file. More adventurous users can look at local.conf.extended
# which contains other examples of configuration which can be placed in this file
# but new users likely won't need any of them initially.
#
# Lines starting with the '#' character are commented out and in some cases the
# default values are provided as comments to show people example syntax. Enabling
# the option is a question of removing the # character and making any change to the
# variable as required.
#
# Machine Selection
#
# You need to select a specific machine to target the build with. There are a selection
# of emulated machines available which can boot and run in the QEMU emulator:
#
#MACHINE ?= "qemuarm"
#MACHINE ?= "qemuarm64"
#MACHINE ?= "qemumips"
#MACHINE ?= "qemumips64"
#MACHINE ?= "qemuppc"
#MACHINE ?= "qemux86"
#MACHINE ?= "qemux86-64"
#
# There are also the following hardware board target machines included for
# demonstration purposes:
#
#MACHINE ?= "beaglebone"
#MACHINE ?= "genericx86"
#MACHINE ?= "genericx86-64"
#MACHINE ?= "mpc8315e-rdb"
#MACHINE ?= "edgerouter"
#
# This sets the default machine to be qemux86 if no other machine is selected:
#MACHINE ??= "qemux86"
MACHINE = "ccimx6ulsbc"
#
# Use Digi's internal git repositories
#
#DIGI_INTERNAL_GIT ?= "1"
#
# Where to place downloads
#
# During a first build the system will download many different source code tarballs
# from various upstream projects. This can take a while, particularly if your network
# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you
# can preserve this directory to speed up this part of subsequent builds. This directory
# is safe to share between multiple builds on the same machine too.
#
# The default is a downloads directory under TOPDIR which is the build directory.
#
DL_DIR ?= "${TOPDIR}/downloads"
#
# Where to place shared-state files
#
# BitBake has the capability to accelerate builds based on previously built output.
# This is done using "shared state" files which can be thought of as cache objects
# and this option determines where those files are placed.
#
# You can wipe out TMPDIR leaving this directory intact and the build would regenerate
# from these files if no changes were made to the configuration. If changes were made
# to the configuration, only shared state files where the state was still valid would
# be used (done using checksums).
#
# The default is a sstate-cache directory under TOPDIR.
#
SSTATE_DIR ?= "${TOPDIR}/sstate-cache"
#
# Where to place the build output
#
# This option specifies where the bulk of the building work should be done and
# where BitBake should place its temporary files and output. Keep in mind that
# this includes the extraction and compilation of many applications and the toolchain
# which can use Gigabytes of hard disk space.
#
# The default is a tmp directory under TOPDIR.
#
TMPDIR = "${TOPDIR}/tmp"
#
# Default policy config
#
# The distribution setting controls which policy settings are used as defaults.
# The default value is fine for general Yocto project use, at least initially.
# Ultimately when creating custom policy, people will likely end up subclassing
# these defaults.
#
DISTRO ?= "dey"
# As an example of a subclass there is a "bleeding" edge policy configuration
# where many versions are set to the absolute latest code from the upstream
# source control systems. This is just mentioned here as an example, its not
# useful to most new users.
# DISTRO ?= "poky-bleeding"
#
# Package Management configuration
#
# This variable lists which packaging formats to enable. Multiple package backends
# can be enabled at once and the first item listed in the variable will be used
# to generate the root filesystems.
# Options are:
# - 'package_deb' for debian style deb files
# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager)
# - 'package_rpm' for rpm style packages
# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk"
# We default to rpm:
PACKAGE_CLASSES ?= "package_rpm"
#
# SDK target architecture
#
# This variable specifies the architecture to build SDK items for and means
# you can build the SDK packages for architectures other than the machine you are
# running the build on (i.e. building i686 packages on an x86_64 host).
# Supported values are i686 and x86_64
#SDKMACHINE ?= "i686"
#
# Extra image configuration defaults
#
# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated
# images. Some of these options are added to certain image types automatically. The
# variable can contain the following options:
# "dbg-pkgs" - add -dbg packages for all installed packages
# (adds symbol information for debugging/profiling)
# "dev-pkgs" - add -dev packages for all installed packages
# (useful if you want to develop against libs in the image)
# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages
# (useful if you want to run the package test suites)
# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.)
# "tools-debug" - add debugging tools (gdb, strace)
# "eclipse-debug" - add Eclipse remote debugging support
# "tools-profile" - add profiling tools (oprofile, lttng, valgrind)
# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.)
# "debug-tweaks" - make an image suitable for development
# e.g. ssh root access has a blank password
# There are other application targets that can be used here too, see
# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details.
# We default to enabling the debugging tweaks.
EXTRA_IMAGE_FEATURES ?= "debug-tweaks"
#
# Additional image features
#
# The following is a list of additional classes to use when building images which
# enable extra features. Some available options which can be included in this variable
# are:
# - 'buildstats' collect build statistics
# - 'image-mklibs' to reduce shared library files size for an image
# - 'image-prelink' in order to prelink the filesystem image
# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink
# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended
USER_CLASSES ?= "buildstats image-mklibs image-prelink"
#
# Runtime testing of images
#
# The build system can test booting virtual machine images under qemu (an emulator)
# after any root filesystems are created and run tests against those images. To
# enable this uncomment this line. See classes/testimage(-auto).bbclass for
# further details.
#TEST_IMAGE = "1"
#
# Interactive shell configuration
#
# Under certain circumstances the system may need input from you and to do this it
# can launch an interactive shell. It needs to do this since the build is
# multithreaded and needs to be able to handle the case where more than one parallel
# process may require the user's attention. The default is iterate over the available
# terminal types to find one that works.
#
# Examples of the occasions this may happen are when resolving patches which cannot
# be applied, to use the devshell or the kernel menuconfig
#
# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none
# Note: currently, Konsole support only works for KDE 3.x due to the way
# newer Konsole versions behave
#OE_TERMINAL = "auto"
# By default disable interactive patch resolution (tasks will just fail instead):
PATCHRESOLVE = "noop"
#
# Disk Space Monitoring during the build
#
# Monitor the disk space during the build. If there is less that 1GB of space or less
# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully
# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort
# of the build. The reason for this is that running completely out of space can corrupt
# files and damages the build in ways which may not be easily recoverable.
# It's necesary to monitor /tmp, if there is no space left the build will fail
# with very exotic errors.
BB_DISKMON_DIRS = "\
STOPTASKS,${TMPDIR},1G,100K \
STOPTASKS,${DL_DIR},1G,100K \
STOPTASKS,${SSTATE_DIR},1G,100K \
STOPTASKS,/tmp,100M,100K \
ABORT,${TMPDIR},100M,1K \
ABORT,${DL_DIR},100M,1K \
ABORT,${SSTATE_DIR},100M,1K \
ABORT,/tmp,10M,1K"
#
# Shared-state files from other locations
#
# As mentioned above, shared state files are prebuilt cache data objects which can
# used to accelerate build time. This variable can be used to configure the system
# to search other mirror locations for these objects before it builds the data itself.
#
# This can be a filesystem directory, or a remote url such as http or ftp. These
# would contain the sstate-cache results from previous builds (possibly from other
# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the
# cache locations to check for the shared objects.
# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH
# at the end as shown in the examples below. This will be substituted with the
# correct path within the directory structure.
#SSTATE_MIRRORS ?= "\
#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \
#file://.* file:///some/local/dir/sstate/PATH"
#
# Qemu configuration
#
# By default qemu will build with a builtin VNC server where graphical output can be
# seen. The two lines below enable the SDL backend too. By default libsdl-native will
# be built, if you want to use your host's libSDL instead of the minimal libsdl built
# by libsdl-native then uncomment the ASSUME_PROVIDED line below.
PACKAGECONFIG_append_pn-qemu-native = " sdl"
PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl"
#ASSUME_PROVIDED += "libsdl-native"
# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to
# track the version of this file when it was generated. This can safely be ignored if
# this doesn't mean anything to you.
CONF_VERSION = "1"
BB_NUMBER_THREADS ?= "12"
PARALLEL_MAKE ?= "-j 8"
#
# Enable local PR server
#
PRSERV_HOST = "localhost:0"
#
# Some libraries and packages are covered by NXP EULA
#
ACCEPT_FSL_EULA = "1"
[-- Attachment #8: local.conf --]
[-- Type: application/octet-stream, Size: 10653 bytes --]
#
# This file is your local configuration file and is where all local user settings
# are placed. The comments in this file give some guide to the options a new user
# to the system might want to change but pretty much any configuration option can
# be set in this file. More adventurous users can look at local.conf.extended
# which contains other examples of configuration which can be placed in this file
# but new users likely won't need any of them initially.
#
# Lines starting with the '#' character are commented out and in some cases the
# default values are provided as comments to show people example syntax. Enabling
# the option is a question of removing the # character and making any change to the
# variable as required.
#
# Machine Selection
#
# You need to select a specific machine to target the build with. There are a selection
# of emulated machines available which can boot and run in the QEMU emulator:
#
#MACHINE ?= "qemuarm"
#MACHINE ?= "qemuarm64"
#MACHINE ?= "qemumips"
#MACHINE ?= "qemumips64"
#MACHINE ?= "qemuppc"
#MACHINE ?= "qemux86"
#MACHINE ?= "qemux86-64"
#
# There are also the following hardware board target machines included for
# demonstration purposes:
#
#MACHINE ?= "beaglebone"
#MACHINE ?= "genericx86"
#MACHINE ?= "genericx86-64"
#MACHINE ?= "mpc8315e-rdb"
#MACHINE ?= "edgerouter"
#
# This sets the default machine to be qemux86 if no other machine is selected:
#MACHINE ??= "qemux86"
MACHINE = "ccimx6ulsbc"
#
# Use Digi's internal git repositories
#
#DIGI_INTERNAL_GIT ?= "1"
#
# Where to place downloads
#
# During a first build the system will download many different source code tarballs
# from various upstream projects. This can take a while, particularly if your network
# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you
# can preserve this directory to speed up this part of subsequent builds. This directory
# is safe to share between multiple builds on the same machine too.
#
# The default is a downloads directory under TOPDIR which is the build directory.
#
DL_DIR ?= "${TOPDIR}/downloads"
#
# Where to place shared-state files
#
# BitBake has the capability to accelerate builds based on previously built output.
# This is done using "shared state" files which can be thought of as cache objects
# and this option determines where those files are placed.
#
# You can wipe out TMPDIR leaving this directory intact and the build would regenerate
# from these files if no changes were made to the configuration. If changes were made
# to the configuration, only shared state files where the state was still valid would
# be used (done using checksums).
#
# The default is a sstate-cache directory under TOPDIR.
#
SSTATE_DIR ?= "${TOPDIR}/sstate-cache"
#
# Where to place the build output
#
# This option specifies where the bulk of the building work should be done and
# where BitBake should place its temporary files and output. Keep in mind that
# this includes the extraction and compilation of many applications and the toolchain
# which can use Gigabytes of hard disk space.
#
# The default is a tmp directory under TOPDIR.
#
TMPDIR = "${TOPDIR}/tmp"
#
# Default policy config
#
# The distribution setting controls which policy settings are used as defaults.
# The default value is fine for general Yocto project use, at least initially.
# Ultimately when creating custom policy, people will likely end up subclassing
# these defaults.
#
DISTRO ?= "dey"
# As an example of a subclass there is a "bleeding" edge policy configuration
# where many versions are set to the absolute latest code from the upstream
# source control systems. This is just mentioned here as an example, its not
# useful to most new users.
# DISTRO ?= "poky-bleeding"
#
# Package Management configuration
#
# This variable lists which packaging formats to enable. Multiple package backends
# can be enabled at once and the first item listed in the variable will be used
# to generate the root filesystems.
# Options are:
# - 'package_deb' for debian style deb files
# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager)
# - 'package_rpm' for rpm style packages
# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk"
# We default to rpm:
PACKAGE_CLASSES ?= "package_rpm"
#
# SDK target architecture
#
# This variable specifies the architecture to build SDK items for and means
# you can build the SDK packages for architectures other than the machine you are
# running the build on (i.e. building i686 packages on an x86_64 host).
# Supported values are i686 and x86_64
#SDKMACHINE ?= "i686"
#
# Extra image configuration defaults
#
# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated
# images. Some of these options are added to certain image types automatically. The
# variable can contain the following options:
# "dbg-pkgs" - add -dbg packages for all installed packages
# (adds symbol information for debugging/profiling)
# "dev-pkgs" - add -dev packages for all installed packages
# (useful if you want to develop against libs in the image)
# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages
# (useful if you want to run the package test suites)
# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.)
# "tools-debug" - add debugging tools (gdb, strace)
# "eclipse-debug" - add Eclipse remote debugging support
# "tools-profile" - add profiling tools (oprofile, lttng, valgrind)
# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.)
# "debug-tweaks" - make an image suitable for development
# e.g. ssh root access has a blank password
# There are other application targets that can be used here too, see
# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details.
# We default to enabling the debugging tweaks.
EXTRA_IMAGE_FEATURES ?= "debug-tweaks"
#
# Additional image features
#
# The following is a list of additional classes to use when building images which
# enable extra features. Some available options which can be included in this variable
# are:
# - 'buildstats' collect build statistics
# - 'image-mklibs' to reduce shared library files size for an image
# - 'image-prelink' in order to prelink the filesystem image
# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink
# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended
USER_CLASSES ?= "buildstats image-mklibs image-prelink"
#
# Runtime testing of images
#
# The build system can test booting virtual machine images under qemu (an emulator)
# after any root filesystems are created and run tests against those images. To
# enable this uncomment this line. See classes/testimage(-auto).bbclass for
# further details.
#TEST_IMAGE = "1"
#
# Interactive shell configuration
#
# Under certain circumstances the system may need input from you and to do this it
# can launch an interactive shell. It needs to do this since the build is
# multithreaded and needs to be able to handle the case where more than one parallel
# process may require the user's attention. The default is iterate over the available
# terminal types to find one that works.
#
# Examples of the occasions this may happen are when resolving patches which cannot
# be applied, to use the devshell or the kernel menuconfig
#
# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none
# Note: currently, Konsole support only works for KDE 3.x due to the way
# newer Konsole versions behave
#OE_TERMINAL = "auto"
# By default disable interactive patch resolution (tasks will just fail instead):
PATCHRESOLVE = "noop"
#
# Disk Space Monitoring during the build
#
# Monitor the disk space during the build. If there is less that 1GB of space or less
# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully
# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort
# of the build. The reason for this is that running completely out of space can corrupt
# files and damages the build in ways which may not be easily recoverable.
# It's necesary to monitor /tmp, if there is no space left the build will fail
# with very exotic errors.
BB_DISKMON_DIRS = "\
STOPTASKS,${TMPDIR},1G,100K \
STOPTASKS,${DL_DIR},1G,100K \
STOPTASKS,${SSTATE_DIR},1G,100K \
STOPTASKS,/tmp,100M,100K \
ABORT,${TMPDIR},100M,1K \
ABORT,${DL_DIR},100M,1K \
ABORT,${SSTATE_DIR},100M,1K \
ABORT,/tmp,10M,1K"
#
# Shared-state files from other locations
#
# As mentioned above, shared state files are prebuilt cache data objects which can
# used to accelerate build time. This variable can be used to configure the system
# to search other mirror locations for these objects before it builds the data itself.
#
# This can be a filesystem directory, or a remote url such as http or ftp. These
# would contain the sstate-cache results from previous builds (possibly from other
# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the
# cache locations to check for the shared objects.
# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH
# at the end as shown in the examples below. This will be substituted with the
# correct path within the directory structure.
#SSTATE_MIRRORS ?= "\
#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \
#file://.* file:///some/local/dir/sstate/PATH"
#
# Qemu configuration
#
# By default qemu will build with a builtin VNC server where graphical output can be
# seen. The two lines below enable the SDL backend too. By default libsdl-native will
# be built, if you want to use your host's libSDL instead of the minimal libsdl built
# by libsdl-native then uncomment the ASSUME_PROVIDED line below.
PACKAGECONFIG_append_pn-qemu-native = " sdl"
PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl"
#ASSUME_PROVIDED += "libsdl-native"
# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to
# track the version of this file when it was generated. This can safely be ignored if
# this doesn't mean anything to you.
CONF_VERSION = "1"
SOURCE_MIRROR_URL = "file:///home/irhpoq/yocto_build/downloads/"
INHERIT += "own-mirrors"
BB_GENERATE_MIRROR_TARBALLS = "1"
BB_NUMBER_THREADS ?= "12"
PARALLEL_MAKE ?= "-j 8"
BB_NO_NETWORK = "1"
#
# Enable local PR server
#
PRSERV_HOST = "localhost:0"
#
# Some libraries and packages are covered by NXP EULA
#
ACCEPT_FSL_EULA = "1"
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Regarding build Yocto offline
2018-07-16 11:25 ` Burton, Ross
2018-07-16 12:00 ` S, Karthikeyan
@ 2018-07-16 12:04 ` S, Karthikeyan
2018-07-16 12:06 ` Burton, Ross
1 sibling, 1 reply; 14+ messages in thread
From: S, Karthikeyan @ 2018-07-16 12:04 UTC (permalink / raw)
To: Burton, Ross; +Cc: yocto
Hi Ross,
From your reply and from the below link " https://wiki.yoctoproject.org/wiki/How_do_I#Non-networked_Builds_and_Cached_Git_Respositories"
I may have to change something in SRC_URI and SRC_REV variable and this will work I guess, Please let me know what exactly I have to do. Thanks for supporting this issue.
Thanks,
Karthik
-----Original Message-----
From: Burton, Ross [mailto:ross.burton@intel.com]
Sent: Monday, July 16, 2018 4:55 PM
To: S, Karthikeyan <Karthikeyan.S@trane.com>
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Regarding build Yocto offline
That build is not building that recipe, because the recipe you've attached has SRC_URI=a local file, but the log clearly shows it going to github.
Assuming you're actually using the original version of the recipe and not the edited version you sent, then the problem is that the recipe has SRCREV=${AUTOREV}, which means "always go and get the latest revision". This is obviously incompatible with offline builds, so you'll want to replace that with a specific SHA to build (as this is an old kernel, the SHA of the branch will be sufficient).
Ross
On 16 July 2018 at 12:17, S, Karthikeyan <Karthikeyan.S@trane.com> wrote:
> Hi Ross,
> Sorry, I don’t have log file, I am attaching screenshot here and
> please let me know how to get log files
>
>
> Thanks & Regards,
> Karthik S
>
>
>
> -----Original Message-----
> From: Burton, Ross [mailto:ross.burton@intel.com]
> Sent: Monday, July 16, 2018 4:44 PM
> To: S, Karthikeyan <Karthikeyan.S@trane.com>
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] Regarding build Yocto offline
>
> Logs, please.
>
> Ross
>
> On 16 July 2018 at 10:45, S, Karthikeyan <Karthikeyan.S@trane.com> wrote:
>> Hi,
>> Thanks a lot for responding my message even in your busy schedule. As for recipe, it was linux. When I was trying to build entire image "core-image-base", it was failed with "linux kernel recipe". Please find attached linux kernel bb files, all other remaining packages were built successfully.
>>
>> Thanks,
>> Karthik
>>
>> -----Original Message-----
>> From: Burton, Ross [mailto:ross.burton@intel.com]
>> Sent: Monday, July 16, 2018 2:57 PM
>> To: S, Karthikeyan <Karthikeyan.S@trane.com>
>> Cc: yocto@yoctoproject.org
>> Subject: Re: [yocto] Regarding build Yocto offline
>>
>> What recipe is failing? It's most likely to be a recipe which is using a git tag instead of a git hash in the SRCREV.
>>
>> Ross
>>
>> On 13 July 2018 at 09:58, S, Karthikeyan <Karthikeyan.S@trane.com> wrote:
>>> Greetings,
>>>
>>> Initially I was able to built with github access, but
>>> our requirement is to build offline(without Internet), I followed
>>> the steps given in
>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.yoctoproje
>>> c
>>> t
>>> .org_wiki_How-5Fdo-5FI-23Q-3A-5FHow-5Fdo-5FI-5Fcreate-5Fmy-5Fown-5Fs
>>> o
>>> u
>>> rce-5Fdownload-5Fmirror-5F.3F&d=DwIBaQ&c=RqOSY-j6o2m72bl3g1aM9A&r=Yb
>>> S
>>> 5
>>> yltng6sM94fh7KTh4S4VmOewJypeQHV1NtdqqQc&m=P2cndFe0OX2zyu8XR1B5rdwBTl
>>> b c jdT4XVot9clBO6Y&s=25mwi0Mp0X78CdeZtKoVzQ0BeTqLR-q4tn1K0xZcpaU&e=
>>>
>>> I added following lines in conf/local.conf (Git enabled machine)
>>>
>>> SOURCE_MIRROR_URL ?= "file:///source_mirror/sources/"
>>>
>>> INHERIT += "own-mirrors"
>>>
>>> BB_GENERATE_MIRROR_TARBALLS = "1"
>>>
>>> and copied download directory to network disabled system and added
>>> following in conf/local.conf(network disabled system).
>>>
>>> SOURCE_MIRROR_URL ?= "file:///source_mirror/sources/"
>>>
>>> INHERIT += "own-mirrors"
>>>
>>> BB_GENERATE_MIRROR_TARBALLS = "1"
>>>
>>> BB_NO_NETWORK = "1"
>>>
>>> It was throwing error, saying that "Network is disabled through
>>> BB_NO_NETWORK=1" and build was failed. Please share me the exact
>>> procedure to build yocto offline.
>>>
>>>
>>>
>>>
>>>
>>> Thanks & Regards,
>>>
>>> Karthik S
>>>
>>>
>>>
>>>
>>> ________________________________
>>>
>>> The information contained in this message is privileged and intended
>>> only for the recipients named. If the reader is not a representative
>>> of the intended recipient, any review, dissemination or copying of
>>> this message or the information it contains is prohibited. If you
>>> have received this message in error, please immediately notify the
>>> sender, and delete the original message and attachments.
>>>
>>> --
>>> _______________________________________________
>>> yocto mailing list
>>> yocto@yoctoproject.org
>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.yoctoproj
>>> e
>>> c
>>> t.org_listinfo_yocto&d=DwIBaQ&c=RqOSY-j6o2m72bl3g1aM9A&r=YbS5yltng6s
>>> M
>>> 94fh7KTh4S4VmOewJypeQHV1NtdqqQc&m=P2cndFe0OX2zyu8XR1B5rdwBTlbcjdT4XV
>>> o t9clBO6Y&s=u-a0sJKO7HiDC_SADTXL06S-qN7DPan-UYMsYULz_T0&e=
>>>
>>
>> ________________________________
>>
>> The information contained in this message is privileged and intended only for the recipients named. If the reader is not a representative of the intended recipient, any review, dissemination or copying of this message or the information it contains is prohibited. If you have received this message in error, please immediately notify the sender, and delete the original message and attachments.
>
> ________________________________
>
> The information contained in this message is privileged and intended only for the recipients named. If the reader is not a representative of the intended recipient, any review, dissemination or copying of this message or the information it contains is prohibited. If you have received this message in error, please immediately notify the sender, and delete the original message and attachments.
________________________________
The information contained in this message is privileged and intended only for the recipients named. If the reader is not a representative of the intended recipient, any review, dissemination or copying of this message or the information it contains is prohibited. If you have received this message in error, please immediately notify the sender, and delete the original message and attachments.
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Regarding build Yocto offline
2018-07-16 12:04 ` S, Karthikeyan
@ 2018-07-16 12:06 ` Burton, Ross
2018-07-16 12:12 ` S, Karthikeyan
` (2 more replies)
0 siblings, 3 replies; 14+ messages in thread
From: Burton, Ross @ 2018-07-16 12:06 UTC (permalink / raw)
To: S, Karthikeyan; +Cc: yocto
Change SRCREV to a real SHA, not AUTOREV. That's all you need to do.
Ross
On 16 July 2018 at 13:04, S, Karthikeyan <Karthikeyan.S@trane.com> wrote:
> Hi Ross,
> From your reply and from the below link " https://wiki.yoctoproject.org/wiki/How_do_I#Non-networked_Builds_and_Cached_Git_Respositories"
> I may have to change something in SRC_URI and SRC_REV variable and this will work I guess, Please let me know what exactly I have to do. Thanks for supporting this issue.
>
> Thanks,
> Karthik
>
> -----Original Message-----
> From: Burton, Ross [mailto:ross.burton@intel.com]
> Sent: Monday, July 16, 2018 4:55 PM
> To: S, Karthikeyan <Karthikeyan.S@trane.com>
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] Regarding build Yocto offline
>
> That build is not building that recipe, because the recipe you've attached has SRC_URI=a local file, but the log clearly shows it going to github.
>
> Assuming you're actually using the original version of the recipe and not the edited version you sent, then the problem is that the recipe has SRCREV=${AUTOREV}, which means "always go and get the latest revision". This is obviously incompatible with offline builds, so you'll want to replace that with a specific SHA to build (as this is an old kernel, the SHA of the branch will be sufficient).
>
> Ross
>
> On 16 July 2018 at 12:17, S, Karthikeyan <Karthikeyan.S@trane.com> wrote:
>> Hi Ross,
>> Sorry, I don’t have log file, I am attaching screenshot here and
>> please let me know how to get log files
>>
>>
>> Thanks & Regards,
>> Karthik S
>>
>>
>>
>> -----Original Message-----
>> From: Burton, Ross [mailto:ross.burton@intel.com]
>> Sent: Monday, July 16, 2018 4:44 PM
>> To: S, Karthikeyan <Karthikeyan.S@trane.com>
>> Cc: yocto@yoctoproject.org
>> Subject: Re: [yocto] Regarding build Yocto offline
>>
>> Logs, please.
>>
>> Ross
>>
>> On 16 July 2018 at 10:45, S, Karthikeyan <Karthikeyan.S@trane.com> wrote:
>>> Hi,
>>> Thanks a lot for responding my message even in your busy schedule. As for recipe, it was linux. When I was trying to build entire image "core-image-base", it was failed with "linux kernel recipe". Please find attached linux kernel bb files, all other remaining packages were built successfully.
>>>
>>> Thanks,
>>> Karthik
>>>
>>> -----Original Message-----
>>> From: Burton, Ross [mailto:ross.burton@intel.com]
>>> Sent: Monday, July 16, 2018 2:57 PM
>>> To: S, Karthikeyan <Karthikeyan.S@trane.com>
>>> Cc: yocto@yoctoproject.org
>>> Subject: Re: [yocto] Regarding build Yocto offline
>>>
>>> What recipe is failing? It's most likely to be a recipe which is using a git tag instead of a git hash in the SRCREV.
>>>
>>> Ross
>>>
>>> On 13 July 2018 at 09:58, S, Karthikeyan <Karthikeyan.S@trane.com> wrote:
>>>> Greetings,
>>>>
>>>> Initially I was able to built with github access, but
>>>> our requirement is to build offline(without Internet), I followed
>>>> the steps given in
>>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.yoctoproje
>>>> c
>>>> t
>>>> .org_wiki_How-5Fdo-5FI-23Q-3A-5FHow-5Fdo-5FI-5Fcreate-5Fmy-5Fown-5Fs
>>>> o
>>>> u
>>>> rce-5Fdownload-5Fmirror-5F.3F&d=DwIBaQ&c=RqOSY-j6o2m72bl3g1aM9A&r=Yb
>>>> S
>>>> 5
>>>> yltng6sM94fh7KTh4S4VmOewJypeQHV1NtdqqQc&m=P2cndFe0OX2zyu8XR1B5rdwBTl
>>>> b c jdT4XVot9clBO6Y&s=25mwi0Mp0X78CdeZtKoVzQ0BeTqLR-q4tn1K0xZcpaU&e=
>>>>
>>>> I added following lines in conf/local.conf (Git enabled machine)
>>>>
>>>> SOURCE_MIRROR_URL ?= "file:///source_mirror/sources/"
>>>>
>>>> INHERIT += "own-mirrors"
>>>>
>>>> BB_GENERATE_MIRROR_TARBALLS = "1"
>>>>
>>>> and copied download directory to network disabled system and added
>>>> following in conf/local.conf(network disabled system).
>>>>
>>>> SOURCE_MIRROR_URL ?= "file:///source_mirror/sources/"
>>>>
>>>> INHERIT += "own-mirrors"
>>>>
>>>> BB_GENERATE_MIRROR_TARBALLS = "1"
>>>>
>>>> BB_NO_NETWORK = "1"
>>>>
>>>> It was throwing error, saying that "Network is disabled through
>>>> BB_NO_NETWORK=1" and build was failed. Please share me the exact
>>>> procedure to build yocto offline.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Thanks & Regards,
>>>>
>>>> Karthik S
>>>>
>>>>
>>>>
>>>>
>>>> ________________________________
>>>>
>>>> The information contained in this message is privileged and intended
>>>> only for the recipients named. If the reader is not a representative
>>>> of the intended recipient, any review, dissemination or copying of
>>>> this message or the information it contains is prohibited. If you
>>>> have received this message in error, please immediately notify the
>>>> sender, and delete the original message and attachments.
>>>>
>>>> --
>>>> _______________________________________________
>>>> yocto mailing list
>>>> yocto@yoctoproject.org
>>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.yoctoproj
>>>> e
>>>> c
>>>> t.org_listinfo_yocto&d=DwIBaQ&c=RqOSY-j6o2m72bl3g1aM9A&r=YbS5yltng6s
>>>> M
>>>> 94fh7KTh4S4VmOewJypeQHV1NtdqqQc&m=P2cndFe0OX2zyu8XR1B5rdwBTlbcjdT4XV
>>>> o t9clBO6Y&s=u-a0sJKO7HiDC_SADTXL06S-qN7DPan-UYMsYULz_T0&e=
>>>>
>>>
>>> ________________________________
>>>
>>> The information contained in this message is privileged and intended only for the recipients named. If the reader is not a representative of the intended recipient, any review, dissemination or copying of this message or the information it contains is prohibited. If you have received this message in error, please immediately notify the sender, and delete the original message and attachments.
>>
>> ________________________________
>>
>> The information contained in this message is privileged and intended only for the recipients named. If the reader is not a representative of the intended recipient, any review, dissemination or copying of this message or the information it contains is prohibited. If you have received this message in error, please immediately notify the sender, and delete the original message and attachments.
>
> ________________________________
>
> The information contained in this message is privileged and intended only for the recipients named. If the reader is not a representative of the intended recipient, any review, dissemination or copying of this message or the information it contains is prohibited. If you have received this message in error, please immediately notify the sender, and delete the original message and attachments.
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Regarding build Yocto offline
2018-07-16 12:06 ` Burton, Ross
@ 2018-07-16 12:12 ` S, Karthikeyan
2018-07-16 12:16 ` S, Karthikeyan
2018-07-16 12:36 ` S, Karthikeyan
2 siblings, 0 replies; 14+ messages in thread
From: S, Karthikeyan @ 2018-07-16 12:12 UTC (permalink / raw)
To: Burton, Ross; +Cc: yocto
Hi Ross,
Really Thanks a lot for replying quickly. As for SHA, from where will I get this SHA value, below is the one we are using
https://github.com/digi-embedded/linux
Thanks,
Karthik
-----Original Message-----
From: Burton, Ross [mailto:ross.burton@intel.com]
Sent: Monday, July 16, 2018 5:36 PM
To: S, Karthikeyan <Karthikeyan.S@trane.com>
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Regarding build Yocto offline
Change SRCREV to a real SHA, not AUTOREV. That's all you need to do.
Ross
On 16 July 2018 at 13:04, S, Karthikeyan <Karthikeyan.S@trane.com> wrote:
> Hi Ross,
> From your reply and from the below link " https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.yoctoproject.org_wiki_How-5Fdo-5FI-23Non-2Dnetworked-5FBuilds-5Fand-5FCached-5FGit-5FRespositories&d=DwIFaQ&c=RqOSY-j6o2m72bl3g1aM9A&r=YbS5yltng6sM94fh7KTh4S4VmOewJypeQHV1NtdqqQc&m=fsLklzl3TzPsNWr7GG3EUIvPxdcodjk_HEm7tYMKooI&s=4bvR9CC7vDMaZj66VBYTOY8upLV3AEN5ftdkhF4O090&e="
> I may have to change something in SRC_URI and SRC_REV variable and this will work I guess, Please let me know what exactly I have to do. Thanks for supporting this issue.
>
> Thanks,
> Karthik
>
> -----Original Message-----
> From: Burton, Ross [mailto:ross.burton@intel.com]
> Sent: Monday, July 16, 2018 4:55 PM
> To: S, Karthikeyan <Karthikeyan.S@trane.com>
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] Regarding build Yocto offline
>
> That build is not building that recipe, because the recipe you've attached has SRC_URI=a local file, but the log clearly shows it going to github.
>
> Assuming you're actually using the original version of the recipe and not the edited version you sent, then the problem is that the recipe has SRCREV=${AUTOREV}, which means "always go and get the latest revision". This is obviously incompatible with offline builds, so you'll want to replace that with a specific SHA to build (as this is an old kernel, the SHA of the branch will be sufficient).
>
> Ross
>
> On 16 July 2018 at 12:17, S, Karthikeyan <Karthikeyan.S@trane.com> wrote:
>> Hi Ross,
>> Sorry, I don’t have log file, I am attaching screenshot here and
>> please let me know how to get log files
>>
>>
>> Thanks & Regards,
>> Karthik S
>>
>>
>>
>> -----Original Message-----
>> From: Burton, Ross [mailto:ross.burton@intel.com]
>> Sent: Monday, July 16, 2018 4:44 PM
>> To: S, Karthikeyan <Karthikeyan.S@trane.com>
>> Cc: yocto@yoctoproject.org
>> Subject: Re: [yocto] Regarding build Yocto offline
>>
>> Logs, please.
>>
>> Ross
>>
>> On 16 July 2018 at 10:45, S, Karthikeyan <Karthikeyan.S@trane.com> wrote:
>>> Hi,
>>> Thanks a lot for responding my message even in your busy schedule. As for recipe, it was linux. When I was trying to build entire image "core-image-base", it was failed with "linux kernel recipe". Please find attached linux kernel bb files, all other remaining packages were built successfully.
>>>
>>> Thanks,
>>> Karthik
>>>
>>> -----Original Message-----
>>> From: Burton, Ross [mailto:ross.burton@intel.com]
>>> Sent: Monday, July 16, 2018 2:57 PM
>>> To: S, Karthikeyan <Karthikeyan.S@trane.com>
>>> Cc: yocto@yoctoproject.org
>>> Subject: Re: [yocto] Regarding build Yocto offline
>>>
>>> What recipe is failing? It's most likely to be a recipe which is using a git tag instead of a git hash in the SRCREV.
>>>
>>> Ross
>>>
>>> On 13 July 2018 at 09:58, S, Karthikeyan <Karthikeyan.S@trane.com> wrote:
>>>> Greetings,
>>>>
>>>> Initially I was able to built with github access, but
>>>> our requirement is to build offline(without Internet), I followed
>>>> the steps given in
>>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.yoctoproj
>>>> e
>>>> c
>>>> t
>>>> .org_wiki_How-5Fdo-5FI-23Q-3A-5FHow-5Fdo-5FI-5Fcreate-5Fmy-5Fown-5F
>>>> s
>>>> o
>>>> u
>>>> rce-5Fdownload-5Fmirror-5F.3F&d=DwIBaQ&c=RqOSY-j6o2m72bl3g1aM9A&r=Y
>>>> b
>>>> S
>>>> 5
>>>> yltng6sM94fh7KTh4S4VmOewJypeQHV1NtdqqQc&m=P2cndFe0OX2zyu8XR1B5rdwBT
>>>> l b c
>>>> jdT4XVot9clBO6Y&s=25mwi0Mp0X78CdeZtKoVzQ0BeTqLR-q4tn1K0xZcpaU&e=
>>>>
>>>> I added following lines in conf/local.conf (Git enabled machine)
>>>>
>>>> SOURCE_MIRROR_URL ?= "file:///source_mirror/sources/"
>>>>
>>>> INHERIT += "own-mirrors"
>>>>
>>>> BB_GENERATE_MIRROR_TARBALLS = "1"
>>>>
>>>> and copied download directory to network disabled system and added
>>>> following in conf/local.conf(network disabled system).
>>>>
>>>> SOURCE_MIRROR_URL ?= "file:///source_mirror/sources/"
>>>>
>>>> INHERIT += "own-mirrors"
>>>>
>>>> BB_GENERATE_MIRROR_TARBALLS = "1"
>>>>
>>>> BB_NO_NETWORK = "1"
>>>>
>>>> It was throwing error, saying that "Network is disabled through
>>>> BB_NO_NETWORK=1" and build was failed. Please share me the exact
>>>> procedure to build yocto offline.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Thanks & Regards,
>>>>
>>>> Karthik S
>>>>
>>>>
>>>>
>>>>
>>>> ________________________________
>>>>
>>>> The information contained in this message is privileged and
>>>> intended only for the recipients named. If the reader is not a
>>>> representative of the intended recipient, any review, dissemination
>>>> or copying of this message or the information it contains is
>>>> prohibited. If you have received this message in error, please
>>>> immediately notify the sender, and delete the original message and attachments.
>>>>
>>>> --
>>>> _______________________________________________
>>>> yocto mailing list
>>>> yocto@yoctoproject.org
>>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.yoctopro
>>>> j
>>>> e
>>>> c
>>>> t.org_listinfo_yocto&d=DwIBaQ&c=RqOSY-j6o2m72bl3g1aM9A&r=YbS5yltng6
>>>> s
>>>> M
>>>> 94fh7KTh4S4VmOewJypeQHV1NtdqqQc&m=P2cndFe0OX2zyu8XR1B5rdwBTlbcjdT4X
>>>> V o t9clBO6Y&s=u-a0sJKO7HiDC_SADTXL06S-qN7DPan-UYMsYULz_T0&e=
>>>>
>>>
>>> ________________________________
>>>
>>> The information contained in this message is privileged and intended only for the recipients named. If the reader is not a representative of the intended recipient, any review, dissemination or copying of this message or the information it contains is prohibited. If you have received this message in error, please immediately notify the sender, and delete the original message and attachments.
>>
>> ________________________________
>>
>> The information contained in this message is privileged and intended only for the recipients named. If the reader is not a representative of the intended recipient, any review, dissemination or copying of this message or the information it contains is prohibited. If you have received this message in error, please immediately notify the sender, and delete the original message and attachments.
>
> ________________________________
>
> The information contained in this message is privileged and intended only for the recipients named. If the reader is not a representative of the intended recipient, any review, dissemination or copying of this message or the information it contains is prohibited. If you have received this message in error, please immediately notify the sender, and delete the original message and attachments.
________________________________
The information contained in this message is privileged and intended only for the recipients named. If the reader is not a representative of the intended recipient, any review, dissemination or copying of this message or the information it contains is prohibited. If you have received this message in error, please immediately notify the sender, and delete the original message and attachments.
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Regarding build Yocto offline
2018-07-16 12:06 ` Burton, Ross
2018-07-16 12:12 ` S, Karthikeyan
@ 2018-07-16 12:16 ` S, Karthikeyan
2018-07-16 12:36 ` S, Karthikeyan
2 siblings, 0 replies; 14+ messages in thread
From: S, Karthikeyan @ 2018-07-16 12:16 UTC (permalink / raw)
To: Burton, Ross; +Cc: yocto
Hi Ross,
SHA mean "shasum" command in linux which gives some value when we type along with tar file,
Thanks,
Karthik
-----Original Message-----
From: Burton, Ross [mailto:ross.burton@intel.com]
Sent: Monday, July 16, 2018 5:36 PM
To: S, Karthikeyan <Karthikeyan.S@trane.com>
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Regarding build Yocto offline
Change SRCREV to a real SHA, not AUTOREV. That's all you need to do.
Ross
On 16 July 2018 at 13:04, S, Karthikeyan <Karthikeyan.S@trane.com> wrote:
> Hi Ross,
> From your reply and from the below link " https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.yoctoproject.org_wiki_How-5Fdo-5FI-23Non-2Dnetworked-5FBuilds-5Fand-5FCached-5FGit-5FRespositories&d=DwIFaQ&c=RqOSY-j6o2m72bl3g1aM9A&r=YbS5yltng6sM94fh7KTh4S4VmOewJypeQHV1NtdqqQc&m=fsLklzl3TzPsNWr7GG3EUIvPxdcodjk_HEm7tYMKooI&s=4bvR9CC7vDMaZj66VBYTOY8upLV3AEN5ftdkhF4O090&e="
> I may have to change something in SRC_URI and SRC_REV variable and this will work I guess, Please let me know what exactly I have to do. Thanks for supporting this issue.
>
> Thanks,
> Karthik
>
> -----Original Message-----
> From: Burton, Ross [mailto:ross.burton@intel.com]
> Sent: Monday, July 16, 2018 4:55 PM
> To: S, Karthikeyan <Karthikeyan.S@trane.com>
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] Regarding build Yocto offline
>
> That build is not building that recipe, because the recipe you've attached has SRC_URI=a local file, but the log clearly shows it going to github.
>
> Assuming you're actually using the original version of the recipe and not the edited version you sent, then the problem is that the recipe has SRCREV=${AUTOREV}, which means "always go and get the latest revision". This is obviously incompatible with offline builds, so you'll want to replace that with a specific SHA to build (as this is an old kernel, the SHA of the branch will be sufficient).
>
> Ross
>
> On 16 July 2018 at 12:17, S, Karthikeyan <Karthikeyan.S@trane.com> wrote:
>> Hi Ross,
>> Sorry, I don’t have log file, I am attaching screenshot here and
>> please let me know how to get log files
>>
>>
>> Thanks & Regards,
>> Karthik S
>>
>>
>>
>> -----Original Message-----
>> From: Burton, Ross [mailto:ross.burton@intel.com]
>> Sent: Monday, July 16, 2018 4:44 PM
>> To: S, Karthikeyan <Karthikeyan.S@trane.com>
>> Cc: yocto@yoctoproject.org
>> Subject: Re: [yocto] Regarding build Yocto offline
>>
>> Logs, please.
>>
>> Ross
>>
>> On 16 July 2018 at 10:45, S, Karthikeyan <Karthikeyan.S@trane.com> wrote:
>>> Hi,
>>> Thanks a lot for responding my message even in your busy schedule. As for recipe, it was linux. When I was trying to build entire image "core-image-base", it was failed with "linux kernel recipe". Please find attached linux kernel bb files, all other remaining packages were built successfully.
>>>
>>> Thanks,
>>> Karthik
>>>
>>> -----Original Message-----
>>> From: Burton, Ross [mailto:ross.burton@intel.com]
>>> Sent: Monday, July 16, 2018 2:57 PM
>>> To: S, Karthikeyan <Karthikeyan.S@trane.com>
>>> Cc: yocto@yoctoproject.org
>>> Subject: Re: [yocto] Regarding build Yocto offline
>>>
>>> What recipe is failing? It's most likely to be a recipe which is using a git tag instead of a git hash in the SRCREV.
>>>
>>> Ross
>>>
>>> On 13 July 2018 at 09:58, S, Karthikeyan <Karthikeyan.S@trane.com> wrote:
>>>> Greetings,
>>>>
>>>> Initially I was able to built with github access, but
>>>> our requirement is to build offline(without Internet), I followed
>>>> the steps given in
>>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.yoctoproj
>>>> e
>>>> c
>>>> t
>>>> .org_wiki_How-5Fdo-5FI-23Q-3A-5FHow-5Fdo-5FI-5Fcreate-5Fmy-5Fown-5F
>>>> s
>>>> o
>>>> u
>>>> rce-5Fdownload-5Fmirror-5F.3F&d=DwIBaQ&c=RqOSY-j6o2m72bl3g1aM9A&r=Y
>>>> b
>>>> S
>>>> 5
>>>> yltng6sM94fh7KTh4S4VmOewJypeQHV1NtdqqQc&m=P2cndFe0OX2zyu8XR1B5rdwBT
>>>> l b c
>>>> jdT4XVot9clBO6Y&s=25mwi0Mp0X78CdeZtKoVzQ0BeTqLR-q4tn1K0xZcpaU&e=
>>>>
>>>> I added following lines in conf/local.conf (Git enabled machine)
>>>>
>>>> SOURCE_MIRROR_URL ?= "file:///source_mirror/sources/"
>>>>
>>>> INHERIT += "own-mirrors"
>>>>
>>>> BB_GENERATE_MIRROR_TARBALLS = "1"
>>>>
>>>> and copied download directory to network disabled system and added
>>>> following in conf/local.conf(network disabled system).
>>>>
>>>> SOURCE_MIRROR_URL ?= "file:///source_mirror/sources/"
>>>>
>>>> INHERIT += "own-mirrors"
>>>>
>>>> BB_GENERATE_MIRROR_TARBALLS = "1"
>>>>
>>>> BB_NO_NETWORK = "1"
>>>>
>>>> It was throwing error, saying that "Network is disabled through
>>>> BB_NO_NETWORK=1" and build was failed. Please share me the exact
>>>> procedure to build yocto offline.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Thanks & Regards,
>>>>
>>>> Karthik S
>>>>
>>>>
>>>>
>>>>
>>>> ________________________________
>>>>
>>>> The information contained in this message is privileged and
>>>> intended only for the recipients named. If the reader is not a
>>>> representative of the intended recipient, any review, dissemination
>>>> or copying of this message or the information it contains is
>>>> prohibited. If you have received this message in error, please
>>>> immediately notify the sender, and delete the original message and attachments.
>>>>
>>>> --
>>>> _______________________________________________
>>>> yocto mailing list
>>>> yocto@yoctoproject.org
>>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.yoctopro
>>>> j
>>>> e
>>>> c
>>>> t.org_listinfo_yocto&d=DwIBaQ&c=RqOSY-j6o2m72bl3g1aM9A&r=YbS5yltng6
>>>> s
>>>> M
>>>> 94fh7KTh4S4VmOewJypeQHV1NtdqqQc&m=P2cndFe0OX2zyu8XR1B5rdwBTlbcjdT4X
>>>> V o t9clBO6Y&s=u-a0sJKO7HiDC_SADTXL06S-qN7DPan-UYMsYULz_T0&e=
>>>>
>>>
>>> ________________________________
>>>
>>> The information contained in this message is privileged and intended only for the recipients named. If the reader is not a representative of the intended recipient, any review, dissemination or copying of this message or the information it contains is prohibited. If you have received this message in error, please immediately notify the sender, and delete the original message and attachments.
>>
>> ________________________________
>>
>> The information contained in this message is privileged and intended only for the recipients named. If the reader is not a representative of the intended recipient, any review, dissemination or copying of this message or the information it contains is prohibited. If you have received this message in error, please immediately notify the sender, and delete the original message and attachments.
>
> ________________________________
>
> The information contained in this message is privileged and intended only for the recipients named. If the reader is not a representative of the intended recipient, any review, dissemination or copying of this message or the information it contains is prohibited. If you have received this message in error, please immediately notify the sender, and delete the original message and attachments.
________________________________
The information contained in this message is privileged and intended only for the recipients named. If the reader is not a representative of the intended recipient, any review, dissemination or copying of this message or the information it contains is prohibited. If you have received this message in error, please immediately notify the sender, and delete the original message and attachments.
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: Regarding build Yocto offline
2018-07-16 12:06 ` Burton, Ross
2018-07-16 12:12 ` S, Karthikeyan
2018-07-16 12:16 ` S, Karthikeyan
@ 2018-07-16 12:36 ` S, Karthikeyan
2 siblings, 0 replies; 14+ messages in thread
From: S, Karthikeyan @ 2018-07-16 12:36 UTC (permalink / raw)
To: Burton, Ross; +Cc: yocto
[-- Attachment #1: Type: text/plain, Size: 7792 bytes --]
Hi Ross,
As you said, I tried but was throwing same error. Do I need to change anything in SRC_URI as well?. From the link, it looks like something I need to change I guess.
https://wiki.yoctoproject.org/wiki/How_do_I#Non-networked_Builds_and_Cached_Git_Respositories
Thanks,
Karthik.
-----Original Message-----
From: Burton, Ross [mailto:ross.burton@intel.com]
Sent: Monday, July 16, 2018 5:36 PM
To: S, Karthikeyan <Karthikeyan.S@trane.com>
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Regarding build Yocto offline
Change SRCREV to a real SHA, not AUTOREV. That's all you need to do.
Ross
On 16 July 2018 at 13:04, S, Karthikeyan <Karthikeyan.S@trane.com> wrote:
> Hi Ross,
> From your reply and from the below link " https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.yoctoproject.org_wiki_How-5Fdo-5FI-23Non-2Dnetworked-5FBuilds-5Fand-5FCached-5FGit-5FRespositories&d=DwIFaQ&c=RqOSY-j6o2m72bl3g1aM9A&r=YbS5yltng6sM94fh7KTh4S4VmOewJypeQHV1NtdqqQc&m=fsLklzl3TzPsNWr7GG3EUIvPxdcodjk_HEm7tYMKooI&s=4bvR9CC7vDMaZj66VBYTOY8upLV3AEN5ftdkhF4O090&e="
> I may have to change something in SRC_URI and SRC_REV variable and this will work I guess, Please let me know what exactly I have to do. Thanks for supporting this issue.
>
> Thanks,
> Karthik
>
> -----Original Message-----
> From: Burton, Ross [mailto:ross.burton@intel.com]
> Sent: Monday, July 16, 2018 4:55 PM
> To: S, Karthikeyan <Karthikeyan.S@trane.com>
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] Regarding build Yocto offline
>
> That build is not building that recipe, because the recipe you've attached has SRC_URI=a local file, but the log clearly shows it going to github.
>
> Assuming you're actually using the original version of the recipe and not the edited version you sent, then the problem is that the recipe has SRCREV=${AUTOREV}, which means "always go and get the latest revision". This is obviously incompatible with offline builds, so you'll want to replace that with a specific SHA to build (as this is an old kernel, the SHA of the branch will be sufficient).
>
> Ross
>
> On 16 July 2018 at 12:17, S, Karthikeyan <Karthikeyan.S@trane.com> wrote:
>> Hi Ross,
>> Sorry, I don’t have log file, I am attaching screenshot here and
>> please let me know how to get log files
>>
>>
>> Thanks & Regards,
>> Karthik S
>>
>>
>>
>> -----Original Message-----
>> From: Burton, Ross [mailto:ross.burton@intel.com]
>> Sent: Monday, July 16, 2018 4:44 PM
>> To: S, Karthikeyan <Karthikeyan.S@trane.com>
>> Cc: yocto@yoctoproject.org
>> Subject: Re: [yocto] Regarding build Yocto offline
>>
>> Logs, please.
>>
>> Ross
>>
>> On 16 July 2018 at 10:45, S, Karthikeyan <Karthikeyan.S@trane.com> wrote:
>>> Hi,
>>> Thanks a lot for responding my message even in your busy schedule. As for recipe, it was linux. When I was trying to build entire image "core-image-base", it was failed with "linux kernel recipe". Please find attached linux kernel bb files, all other remaining packages were built successfully.
>>>
>>> Thanks,
>>> Karthik
>>>
>>> -----Original Message-----
>>> From: Burton, Ross [mailto:ross.burton@intel.com]
>>> Sent: Monday, July 16, 2018 2:57 PM
>>> To: S, Karthikeyan <Karthikeyan.S@trane.com>
>>> Cc: yocto@yoctoproject.org
>>> Subject: Re: [yocto] Regarding build Yocto offline
>>>
>>> What recipe is failing? It's most likely to be a recipe which is using a git tag instead of a git hash in the SRCREV.
>>>
>>> Ross
>>>
>>> On 13 July 2018 at 09:58, S, Karthikeyan <Karthikeyan.S@trane.com> wrote:
>>>> Greetings,
>>>>
>>>> Initially I was able to built with github access, but
>>>> our requirement is to build offline(without Internet), I followed
>>>> the steps given in
>>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.yoctoproj
>>>> e
>>>> c
>>>> t
>>>> .org_wiki_How-5Fdo-5FI-23Q-3A-5FHow-5Fdo-5FI-5Fcreate-5Fmy-5Fown-5F
>>>> s
>>>> o
>>>> u
>>>> rce-5Fdownload-5Fmirror-5F.3F&d=DwIBaQ&c=RqOSY-j6o2m72bl3g1aM9A&r=Y
>>>> b
>>>> S
>>>> 5
>>>> yltng6sM94fh7KTh4S4VmOewJypeQHV1NtdqqQc&m=P2cndFe0OX2zyu8XR1B5rdwBT
>>>> l b c
>>>> jdT4XVot9clBO6Y&s=25mwi0Mp0X78CdeZtKoVzQ0BeTqLR-q4tn1K0xZcpaU&e=
>>>>
>>>> I added following lines in conf/local.conf (Git enabled machine)
>>>>
>>>> SOURCE_MIRROR_URL ?= "file:///source_mirror/sources/"
>>>>
>>>> INHERIT += "own-mirrors"
>>>>
>>>> BB_GENERATE_MIRROR_TARBALLS = "1"
>>>>
>>>> and copied download directory to network disabled system and added
>>>> following in conf/local.conf(network disabled system).
>>>>
>>>> SOURCE_MIRROR_URL ?= "file:///source_mirror/sources/"
>>>>
>>>> INHERIT += "own-mirrors"
>>>>
>>>> BB_GENERATE_MIRROR_TARBALLS = "1"
>>>>
>>>> BB_NO_NETWORK = "1"
>>>>
>>>> It was throwing error, saying that "Network is disabled through
>>>> BB_NO_NETWORK=1" and build was failed. Please share me the exact
>>>> procedure to build yocto offline.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Thanks & Regards,
>>>>
>>>> Karthik S
>>>>
>>>>
>>>>
>>>>
>>>> ________________________________
>>>>
>>>> The information contained in this message is privileged and
>>>> intended only for the recipients named. If the reader is not a
>>>> representative of the intended recipient, any review, dissemination
>>>> or copying of this message or the information it contains is
>>>> prohibited. If you have received this message in error, please
>>>> immediately notify the sender, and delete the original message and attachments.
>>>>
>>>> --
>>>> _______________________________________________
>>>> yocto mailing list
>>>> yocto@yoctoproject.org
>>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.yoctopro
>>>> j
>>>> e
>>>> c
>>>> t.org_listinfo_yocto&d=DwIBaQ&c=RqOSY-j6o2m72bl3g1aM9A&r=YbS5yltng6
>>>> s
>>>> M
>>>> 94fh7KTh4S4VmOewJypeQHV1NtdqqQc&m=P2cndFe0OX2zyu8XR1B5rdwBTlbcjdT4X
>>>> V o t9clBO6Y&s=u-a0sJKO7HiDC_SADTXL06S-qN7DPan-UYMsYULz_T0&e=
>>>>
>>>
>>> ________________________________
>>>
>>> The information contained in this message is privileged and intended only for the recipients named. If the reader is not a representative of the intended recipient, any review, dissemination or copying of this message or the information it contains is prohibited. If you have received this message in error, please immediately notify the sender, and delete the original message and attachments.
>>
>> ________________________________
>>
>> The information contained in this message is privileged and intended only for the recipients named. If the reader is not a representative of the intended recipient, any review, dissemination or copying of this message or the information it contains is prohibited. If you have received this message in error, please immediately notify the sender, and delete the original message and attachments.
>
> ________________________________
>
> The information contained in this message is privileged and intended only for the recipients named. If the reader is not a representative of the intended recipient, any review, dissemination or copying of this message or the information it contains is prohibited. If you have received this message in error, please immediately notify the sender, and delete the original message and attachments.
________________________________
The information contained in this message is privileged and intended only for the recipients named. If the reader is not a representative of the intended recipient, any review, dissemination or copying of this message or the information it contains is prohibited. If you have received this message in error, please immediately notify the sender, and delete the original message and attachments.
[-- Attachment #2: linux-dey_4.9.bb --]
[-- Type: application/octet-stream, Size: 241 bytes --]
# Copyright (C) 2017, 2018 Digi International
require recipes-kernel/linux/linux-dey.inc
SRCBRANCH = "v4.9/dey-2.4/maint"
#SRCREV = "${AUTOREV}"
SRCREV = "b4b8eaa7bd6d16433c2de5afee958d027a2df148"
COMPATIBLE_MACHINE = "(ccimx6|ccimx6ul)"
[-- Attachment #3: shavalue.JPG --]
[-- Type: image/jpeg, Size: 69098 bytes --]
[-- Attachment #4: BB_NO_Network error.JPG --]
[-- Type: image/jpeg, Size: 142902 bytes --]
[-- Attachment #5: local.conf --]
[-- Type: application/octet-stream, Size: 10653 bytes --]
#
# This file is your local configuration file and is where all local user settings
# are placed. The comments in this file give some guide to the options a new user
# to the system might want to change but pretty much any configuration option can
# be set in this file. More adventurous users can look at local.conf.extended
# which contains other examples of configuration which can be placed in this file
# but new users likely won't need any of them initially.
#
# Lines starting with the '#' character are commented out and in some cases the
# default values are provided as comments to show people example syntax. Enabling
# the option is a question of removing the # character and making any change to the
# variable as required.
#
# Machine Selection
#
# You need to select a specific machine to target the build with. There are a selection
# of emulated machines available which can boot and run in the QEMU emulator:
#
#MACHINE ?= "qemuarm"
#MACHINE ?= "qemuarm64"
#MACHINE ?= "qemumips"
#MACHINE ?= "qemumips64"
#MACHINE ?= "qemuppc"
#MACHINE ?= "qemux86"
#MACHINE ?= "qemux86-64"
#
# There are also the following hardware board target machines included for
# demonstration purposes:
#
#MACHINE ?= "beaglebone"
#MACHINE ?= "genericx86"
#MACHINE ?= "genericx86-64"
#MACHINE ?= "mpc8315e-rdb"
#MACHINE ?= "edgerouter"
#
# This sets the default machine to be qemux86 if no other machine is selected:
#MACHINE ??= "qemux86"
MACHINE = "ccimx6ulsbc"
#
# Use Digi's internal git repositories
#
#DIGI_INTERNAL_GIT ?= "1"
#
# Where to place downloads
#
# During a first build the system will download many different source code tarballs
# from various upstream projects. This can take a while, particularly if your network
# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you
# can preserve this directory to speed up this part of subsequent builds. This directory
# is safe to share between multiple builds on the same machine too.
#
# The default is a downloads directory under TOPDIR which is the build directory.
#
DL_DIR ?= "${TOPDIR}/downloads"
#
# Where to place shared-state files
#
# BitBake has the capability to accelerate builds based on previously built output.
# This is done using "shared state" files which can be thought of as cache objects
# and this option determines where those files are placed.
#
# You can wipe out TMPDIR leaving this directory intact and the build would regenerate
# from these files if no changes were made to the configuration. If changes were made
# to the configuration, only shared state files where the state was still valid would
# be used (done using checksums).
#
# The default is a sstate-cache directory under TOPDIR.
#
SSTATE_DIR ?= "${TOPDIR}/sstate-cache"
#
# Where to place the build output
#
# This option specifies where the bulk of the building work should be done and
# where BitBake should place its temporary files and output. Keep in mind that
# this includes the extraction and compilation of many applications and the toolchain
# which can use Gigabytes of hard disk space.
#
# The default is a tmp directory under TOPDIR.
#
TMPDIR = "${TOPDIR}/tmp"
#
# Default policy config
#
# The distribution setting controls which policy settings are used as defaults.
# The default value is fine for general Yocto project use, at least initially.
# Ultimately when creating custom policy, people will likely end up subclassing
# these defaults.
#
DISTRO ?= "dey"
# As an example of a subclass there is a "bleeding" edge policy configuration
# where many versions are set to the absolute latest code from the upstream
# source control systems. This is just mentioned here as an example, its not
# useful to most new users.
# DISTRO ?= "poky-bleeding"
#
# Package Management configuration
#
# This variable lists which packaging formats to enable. Multiple package backends
# can be enabled at once and the first item listed in the variable will be used
# to generate the root filesystems.
# Options are:
# - 'package_deb' for debian style deb files
# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager)
# - 'package_rpm' for rpm style packages
# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk"
# We default to rpm:
PACKAGE_CLASSES ?= "package_rpm"
#
# SDK target architecture
#
# This variable specifies the architecture to build SDK items for and means
# you can build the SDK packages for architectures other than the machine you are
# running the build on (i.e. building i686 packages on an x86_64 host).
# Supported values are i686 and x86_64
#SDKMACHINE ?= "i686"
#
# Extra image configuration defaults
#
# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated
# images. Some of these options are added to certain image types automatically. The
# variable can contain the following options:
# "dbg-pkgs" - add -dbg packages for all installed packages
# (adds symbol information for debugging/profiling)
# "dev-pkgs" - add -dev packages for all installed packages
# (useful if you want to develop against libs in the image)
# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages
# (useful if you want to run the package test suites)
# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.)
# "tools-debug" - add debugging tools (gdb, strace)
# "eclipse-debug" - add Eclipse remote debugging support
# "tools-profile" - add profiling tools (oprofile, lttng, valgrind)
# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.)
# "debug-tweaks" - make an image suitable for development
# e.g. ssh root access has a blank password
# There are other application targets that can be used here too, see
# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details.
# We default to enabling the debugging tweaks.
EXTRA_IMAGE_FEATURES ?= "debug-tweaks"
#
# Additional image features
#
# The following is a list of additional classes to use when building images which
# enable extra features. Some available options which can be included in this variable
# are:
# - 'buildstats' collect build statistics
# - 'image-mklibs' to reduce shared library files size for an image
# - 'image-prelink' in order to prelink the filesystem image
# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink
# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended
USER_CLASSES ?= "buildstats image-mklibs image-prelink"
#
# Runtime testing of images
#
# The build system can test booting virtual machine images under qemu (an emulator)
# after any root filesystems are created and run tests against those images. To
# enable this uncomment this line. See classes/testimage(-auto).bbclass for
# further details.
#TEST_IMAGE = "1"
#
# Interactive shell configuration
#
# Under certain circumstances the system may need input from you and to do this it
# can launch an interactive shell. It needs to do this since the build is
# multithreaded and needs to be able to handle the case where more than one parallel
# process may require the user's attention. The default is iterate over the available
# terminal types to find one that works.
#
# Examples of the occasions this may happen are when resolving patches which cannot
# be applied, to use the devshell or the kernel menuconfig
#
# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none
# Note: currently, Konsole support only works for KDE 3.x due to the way
# newer Konsole versions behave
#OE_TERMINAL = "auto"
# By default disable interactive patch resolution (tasks will just fail instead):
PATCHRESOLVE = "noop"
#
# Disk Space Monitoring during the build
#
# Monitor the disk space during the build. If there is less that 1GB of space or less
# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully
# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort
# of the build. The reason for this is that running completely out of space can corrupt
# files and damages the build in ways which may not be easily recoverable.
# It's necesary to monitor /tmp, if there is no space left the build will fail
# with very exotic errors.
BB_DISKMON_DIRS = "\
STOPTASKS,${TMPDIR},1G,100K \
STOPTASKS,${DL_DIR},1G,100K \
STOPTASKS,${SSTATE_DIR},1G,100K \
STOPTASKS,/tmp,100M,100K \
ABORT,${TMPDIR},100M,1K \
ABORT,${DL_DIR},100M,1K \
ABORT,${SSTATE_DIR},100M,1K \
ABORT,/tmp,10M,1K"
#
# Shared-state files from other locations
#
# As mentioned above, shared state files are prebuilt cache data objects which can
# used to accelerate build time. This variable can be used to configure the system
# to search other mirror locations for these objects before it builds the data itself.
#
# This can be a filesystem directory, or a remote url such as http or ftp. These
# would contain the sstate-cache results from previous builds (possibly from other
# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the
# cache locations to check for the shared objects.
# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH
# at the end as shown in the examples below. This will be substituted with the
# correct path within the directory structure.
#SSTATE_MIRRORS ?= "\
#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \
#file://.* file:///some/local/dir/sstate/PATH"
#
# Qemu configuration
#
# By default qemu will build with a builtin VNC server where graphical output can be
# seen. The two lines below enable the SDL backend too. By default libsdl-native will
# be built, if you want to use your host's libSDL instead of the minimal libsdl built
# by libsdl-native then uncomment the ASSUME_PROVIDED line below.
PACKAGECONFIG_append_pn-qemu-native = " sdl"
PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl"
#ASSUME_PROVIDED += "libsdl-native"
# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to
# track the version of this file when it was generated. This can safely be ignored if
# this doesn't mean anything to you.
CONF_VERSION = "1"
SOURCE_MIRROR_URL = "file:///home/irhpoq/yocto_build/downloads/"
INHERIT += "own-mirrors"
BB_GENERATE_MIRROR_TARBALLS = "1"
BB_NUMBER_THREADS ?= "12"
PARALLEL_MAKE ?= "-j 8"
BB_NO_NETWORK = "1"
#
# Enable local PR server
#
PRSERV_HOST = "localhost:0"
#
# Some libraries and packages are covered by NXP EULA
#
ACCEPT_FSL_EULA = "1"
[-- Attachment #6: linux-dey.inc.orig --]
[-- Type: application/octet-stream, Size: 2247 bytes --]
# Copyright (C) 2013-2018 Digi International
SUMMARY = "Linux kernel for Digi boards"
LICENSE = "GPLv2"
LIC_FILES_CHKSUM = "file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7"
DEPENDS += "lzop-native bc-native"
DEPENDS += "${@base_conditional('TRUSTFENCE_SIGN', '1', 'trustfence-sign-tools-native', '', d)}"
inherit kernel fsl-kernel-localversion
LOCALVERSION = "-dey"
# Select internal or Github Linux repo
LINUX_GIT_URI ?= "${@base_conditional('DIGI_INTERNAL_GIT', '1' , '${DIGI_GIT}linux-2.6.git', '${DIGI_GITHUB_GIT}/linux.git', d)}"
SRC_URI = " \
${LINUX_GIT_URI};branch=${SRCBRANCH} \
file://defconfig \
"
S = "${WORKDIR}/git"
do_deploy[postfuncs] += "${@base_conditional('TRUSTFENCE_SIGN', '1', 'trustfence_sign', '', d)}"
trustfence_sign() {
# Set environment variables for trustfence configuration
export CONFIG_SIGN_KEYS_PATH="${TRUSTFENCE_SIGN_KEYS_PATH}"
[ -n "${TRUSTFENCE_KEY_INDEX}" ] && export CONFIG_KEY_INDEX="${TRUSTFENCE_KEY_INDEX}"
[ -n "${TRUSTFENCE_DEK_PATH}" ] && [ "${TRUSTFENCE_DEK_PATH}" != "0" ] && export CONFIG_DEK_PATH="${TRUSTFENCE_DEK_PATH}"
# Sign/encrypt the kernel images
for type in ${KERNEL_IMAGETYPES}; do
KERNEL_IMAGE="${type}-${KERNEL_IMAGE_BASE_NAME}.bin"
TMP_KERNEL_IMAGE_SIGNED="$(mktemp ${KERNEL_IMAGE}-signed.XXXXXX)"
trustfence-sign-kernel.sh -p "${DIGI_FAMILY}" -l "${KERNEL_IMAGE}" "${TMP_KERNEL_IMAGE_SIGNED}"
mv "${TMP_KERNEL_IMAGE_SIGNED}" "${KERNEL_IMAGE}"
done
# Sign/encrypt the device tree blobs
for DTB in ${KERNEL_DEVICETREE}; do
DTB=`normalize_dtb "${DTB}"`
DTB_EXT=${DTB##*.}
DTB_BASE_NAME=`basename ${DTB} ."${DTB_EXT}"`
for type in ${KERNEL_IMAGETYPES}; do
DTB_IMAGE="$(echo ${type}-${KERNEL_IMAGE_BASE_NAME} | sed "s/${MACHINE}/${DTB_BASE_NAME}/g").${DTB_EXT}"
TMP_DTB_IMAGE_SIGNED="$(mktemp ${DTB_IMAGE}-signed.XXXXXX)"
trustfence-sign-kernel.sh -p "${DIGI_FAMILY}" -d "${DTB_IMAGE}" "${TMP_DTB_IMAGE_SIGNED}"
mv "${TMP_DTB_IMAGE_SIGNED}" "${DTB_IMAGE}"
done
done
}
trustfence_sign[dirs] = "${DEPLOYDIR}"
do_deploy[vardeps] += "TRUSTFENCE_SIGN_KEYS_PATH TRUSTFENCE_KEY_INDEX TRUSTFENCE_DEK_PATH"
FILES_kernel-image += "/boot/config-${KERNEL_VERSION}"
# Don't include kernels in standard images
RDEPENDS_kernel-base = ""
^ permalink raw reply [flat|nested] 14+ messages in thread
end of thread, other threads:[~2018-07-16 17:41 UTC | newest]
Thread overview: 14+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-07-13 8:58 Regarding build Yocto offline S, Karthikeyan
2018-07-16 8:55 ` Gunnar Andersson
2018-07-16 9:01 ` Gunnar GMail
2018-07-16 9:27 ` Burton, Ross
2018-07-16 9:45 ` S, Karthikeyan
2018-07-16 11:13 ` Burton, Ross
2018-07-16 11:17 ` S, Karthikeyan
2018-07-16 11:25 ` Burton, Ross
2018-07-16 12:00 ` S, Karthikeyan
2018-07-16 12:04 ` S, Karthikeyan
2018-07-16 12:06 ` Burton, Ross
2018-07-16 12:12 ` S, Karthikeyan
2018-07-16 12:16 ` S, Karthikeyan
2018-07-16 12:36 ` S, Karthikeyan
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.