[yocto] FireFox
Hi everyone,
I am trying to add firefox to my yocto project. I am now at this so I need a
few hints.
*1. I am using yocto kirkstone*
*2. Image I am building is core-image-minimal-dev*
*3. My local.conf file looks like this:*
#
# 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.sample.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-yocto"
#MACHINE ?= "genericx86"
#MACHINE ?= "genericx86-64"
#MACHINE ?= "edgerouter"
#
# This sets the default machine to be qemux86-64 if no other machine is
selected:
MACHINE ??= "qemux86-64"
#
# 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 ?= "poky"
# 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_deb"
#
# 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, x86_64, aarch64
#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
# va
Re: [yocto] FireFox
Thank you for your help! Is there any other option instead of core-image-sato? -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#58854): https://lists.yoctoproject.org/g/yocto/message/58854 Mute This Topic: https://lists.yoctoproject.org/mt/95802925/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[yocto] Run browser immediately after booting up device #yocto
Hi everyone, I have a task to add browser to my yocto project and start it immediately after it is booted. Also I have to open specific web page. Any suggestions how to do it? Any advice would be helpful. Thanks in advance! -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#58873): https://lists.yoctoproject.org/g/yocto/message/58873 Mute This Topic: https://lists.yoctoproject.org/mt/95900014/21656 Mute #yocto:https://lists.yoctoproject.org/g/yocto/mutehashtag/yocto Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[yocto] How to make root file system writable?
After bitbaking core-image-full-cmdline, my root file system is readable only. How to make it writable? Is there something I have to change in local.conf? -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#58937): https://lists.yoctoproject.org/g/yocto/message/58937 Mute This Topic: https://lists.yoctoproject.org/mt/96148248/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[yocto] gn native do compile fails
Can someone help me to solve this issue? I am not sure what can be the problem since me and my colleague did the exact same steps, and on his machine everything is done without any error and I am receiving constantly this one: ERROR: gn-native-106.0.5249.119-r0 do_compile: Execution of '/home/jovanbosic/Yocto/build/tmp/work/x86_64-linux/gn-native/106.0.5249.119-r0/temp/run.do_compile.2197284' failed with exit code 1 ERROR: Logfile of failure stored in: /home/jovanbosic/Yocto/build/tmp/work/x86_64-linux/gn-native/106.0.5249.119-r0/temp/log.do_compile.2197284 Log data follows: | DEBUG: Executing shell function do_compile | ninja: Entering directory `/home/jovanbosic/Yocto/build/tmp/work/x86_64-linux/gn-native/106.0.5249.119-r0/chromium-106.0.5249.119/out/Release/gn_build' | [1/195] CXX src/base/files/file_path_constants.o | FAILED: src/base/files/file_path_constants.o | clang++ -target x86_64-linux -MMD -MF src/base/files/file_path_constants.o.d -I../../../tools/gn/src -I. -isystem/home/jovanbosic/Yocto/build/tmp/work/x86_64-linux/gn-native/106.0.5249.119-r0/recipe-sysroot-native/usr/include -O2 -pipe -isystem/home/jovanbosic/Yocto/build/tmp/work/x86_64-linux/gn-native/106.0.5249.119-r0/recipe-sysroot-native/usr/include -O2 -pipe -D_LIBCPP_HAS_NO_VENDOR_AVAILABILITY_ANNOTATIONS -DNDEBUG -O3 -fdata-sections -ffunction-sections -Werror -D_FILE_OFFSET_BITS=64 -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -pthread -pipe -fno-exceptions -fno-rtti -fdiagnostics-color -Wall -Wextra -Wno-unused-parameter -Wextra-semi -Wundef -std=c++17 -c ../../../tools/gn/src/base/files/file_path_constants.cc -o src/base/files/file_path_constants.o | ../../../tools/gn/src/base/files/file_path_constants.cc:7:10: fatal error: 'iterator' file not found | #include | ^~ | 1 error generated. | [2/195] CXX src/base/command_line.o | FAILED: src/base/command_line.o | clang++ -target x86_64-linux -MMD -MF src/base/command_line.o.d -I../../../tools/gn/src -I. -isystem/home/jovanbosic/Yocto/build/tmp/work/x86_64-linux/gn-native/106.0.5249.119-r0/recipe-sysroot-native/usr/include -O2 -pipe -isystem/home/jovanbosic/Yocto/build/tmp/work/x86_64-linux/gn-native/106.0.5249.119-r0/recipe-sysroot-native/usr/include -O2 -pipe -D_LIBCPP_HAS_NO_VENDOR_AVAILABILITY_ANNOTATIONS -DNDEBUG -O3 -fdata-sections -ffunction-sections -Werror -D_FILE_OFFSET_BITS=64 -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -pthread -pipe -fno-exceptions -fno-rtti -fdiagnostics-color -Wall -Wextra -Wno-unused-parameter -Wextra-semi -Wundef -std=c++17 -c ../../../tools/gn/src/base/command_line.cc -o src/base/command_line.o | In file included from ../../../tools/gn/src/base/command_line.cc:5: | ../../../tools/gn/src/base/command_line.h:19:10: fatal error: 'map' file not found | #include | ^ | 1 error generated. | [3/195] CXX src/base/environment.o | FAILED: src/base/environment.o | clang++ -target x86_64-linux -MMD -MF src/base/environment.o.d -I../../../tools/gn/src -I. -isystem/home/jovanbosic/Yocto/build/tmp/work/x86_64-linux/gn-native/106.0.5249.119-r0/recipe-sysroot-native/usr/include -O2 -pipe -isystem/home/jovanbosic/Yocto/build/tmp/work/x86_64-linux/gn-native/106.0.5249.119-r0/recipe-sysroot-native/usr/include -O2 -pipe -D_LIBCPP_HAS_NO_VENDOR_AVAILABILITY_ANNOTATIONS -DNDEBUG -O3 -fdata-sections -ffunction-sections -Werror -D_FILE_OFFSET_BITS=64 -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -pthread -pipe -fno-exceptions -fno-rtti -fdiagnostics-color -Wall -Wextra -Wno-unused-parameter -Wextra-semi -Wundef -std=c++17 -c ../../../tools/gn/src/base/environment.cc -o src/base/environment.o | In file included from ../../../tools/gn/src/base/environment.cc:5: | ../../../tools/gn/src/base/environment.h:8:10: fatal error: 'map' file not found | #include | ^ | 1 error generated. | [4/195] CXX src/base/files/file_path.o | FAILED: src/base/files/file_path.o | clang++ -target x86_64-linux -MMD -MF src/base/files/file_path.o.d -I../../../tools/gn/src -I. -isystem/home/jovanbosic/Yocto/build/tmp/work/x86_64-linux/gn-native/106.0.5249.119-r0/recipe-sysroot-native/usr/include -O2 -pipe -isystem/home/jovanbosic/Yocto/build/tmp/work/x86_64-linux/gn-native/106.0.5249.119-r0/recipe-sysroot-native/usr/include -O2 -pipe -D_LIBCPP_HAS_NO_VENDOR_AVAILABILITY_ANNOTATIONS -DNDEBUG -O3 -fdata-sections -ffunction-sections -Werror -D_FILE_OFFSET_BITS=64 -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -pthread -pipe -fno-exceptions -fno-rtti -fdiagnostics-color -Wall -Wextra -Wno-unused-parameter -Wextra-semi -Wundef -std=c++17 -c ../../../tools/gn/src/base/files/file_path.cc -o src/base/files/file_path.o | In file included from ../../../tools/gn/src/base/files/file_path.cc:5: | ../../../tools/gn/src/base/files/file_path.h:107:10: fatal error: 'iosfwd' file not found | #include | ^~~~ | 1 error generated. | [5/195] CXX src/base/files/file.o | FAILED: src/base/files/file.o | clang++
Re: [yocto] gn native do compile fails
This is my gn-native_106.0.5.249.119.bb:
# gn-native contains the GN binary used to configure Chromium.
# It is not released separately, and each Chromium release is only expected to
# work with the GN version provided with it.
require chromium.inc
inherit native
S = "${WORKDIR}/chromium-${PV}"
# bootstrap.py --no_clean hardcodes the build location to out_bootstrap.
# Omitting --no_clean causes the script to create a temporary directory with a
# random name outside the build directory, so we choose the lesser of the two
# evils.
B = "${S}/out_bootstrap"
SRC_URI += " \
file://0001-Pass-no-static-libstdc-to-gen.py.patch \
"
# The build system expects the linker to be invoked via the compiler. If we use
# the default value for BUILD_LD, it will fail because it does not recognize
# some of the arguments passed to it.
BUILD_LD = "${CXX}"
# Use LLVM's ar rather than binutils'. Depending on the optimizations enabled
# in the build ar(1) may not be enough.
BUILD_AR = "llvm-ar"
DEPENDS = "clang-native ninja-native libcxx-native"
DEPENDS:append:runtime-llvm = " compiler-rt-native libcxx-native"
# Use libcxx headers for native parts
CXXFLAGS:append:runtime-llvm = " -isysroot=${STAGING_DIR_NATIVE} -stdlib=libc++"
# Use libgcc for native parts
LDFLAGS:append:runtime-llvm = " -rtlib=libgcc -unwindlib=libgcc -stdlib=libc++
-lc++abi -rpath ${STAGING_LIBDIR_NATIVE}"
do_configure[noexec] = "1"
do_compile() {
python3 ${S}/tools/gn/bootstrap/bootstrap.py --skip-generate-buildfiles
}
do_install() {
install -d ${D}${bindir}
install -m 0755 ${S}/out/Release/gn ${D}${bindir}/gn
}
INSANE_SKIP:${PN} += "already-stripped"
I have libcxx-native in dependencies and I have installed C++ runtime but I am
seeing the same error.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#58973): https://lists.yoctoproject.org/g/yocto/message/58973
Mute This Topic: https://lists.yoctoproject.org/mt/96241718/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[yocto] gn-native_106.0.5249.119.bb:do_compile failed with exit code '1'
Can someone help me with this problem? I want to install chromium on dunfell, and I am receiving this problem. jovanbosic@administrator-ThinkPad-L470:~/Yocto/build$ bitbake core-image-full-cmdline WARNING: Host distribution "ubuntu-22.04" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution. Loading cache: 100% || Time: 0:00:00 Loaded 3726 entries from dependency cache. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION = "1.46.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS = "x86_64-poky-linux" MACHINE = "qemux86-64" DISTRO = "poky" DISTRO_VERSION = "3.1.22" TUNE_FEATURES = "m64 core2" TARGET_FPU = "" meta meta-poky meta-yocto-bsp meta-selftest meta-skeleton = "dunfell:6b8a307b7843af23d189d7ffcecf32c05afac850" meta-chromium = "master:068b693ffcf0273ec23d0ab1eeb8f4b97eb143a1" meta-clang = "dunfell-clang12:8a6558fe1cedb3eb81769a3cc2512364f1a6" meta-filesystems meta-gnome meta-initramfs meta-multimedia meta-networking meta-oe meta-perl meta-python meta-webserver meta-xfce = "dunfell:7952135f650b4a754e2255f5aa03973a32344123" Initialising tasks: 100% |###| Time: 0:00:05 Sstate summary: Wanted 21 Found 0 Missed 21 Current 2963 (0% match, 99% complete) NOTE: Executing Tasks ERROR: gn-native-106.0.5249.119-r0 do_compile: Execution of '/home/jovanbosic/Yocto/build/tmp/work/x86_64-linux/gn-native/106.0.5249.119-r0/temp/run.do_compile.4042233' failed with exit code 1 ERROR: Logfile of failure stored in: /home/jovanbosic/Yocto/build/tmp/work/x86_64-linux/gn-native/106.0.5249.119-r0/temp/log.do_compile.4042233 Log data follows: | DEBUG: Executing shell function do_compile | ninja: Entering directory `/home/jovanbosic/Yocto/build/tmp/work/x86_64-linux/gn-native/106.0.5249.119-r0/chromium-106.0.5249.119/out/Release/gn_build' | [1/195] CXX src/base/files/file_path_constants.o | FAILED: src/base/files/file_path_constants.o | clang++ -target x86_64-linux -MMD -MF src/base/files/file_path_constants.o.d -I../../../tools/gn/src -I. -isystem/home/jovanbosic/Yocto/build/tmp/work/x86_64-linux/gn-native/106.0.5249.119-r0/recipe-sysroot-native/usr/include -O2 -pipe -isystem/home/jovanbosic/Yocto/build/tmp/work/x86_64-linux/gn-native/106.0.5249.119-r0/recipe-sysroot-native/usr/include -O2 -pipe -D_LIBCPP_HAS_NO_VENDOR_AVAILABILITY_ANNOTATIONS -DNDEBUG -O3 -fdata-sections -ffunction-sections -Werror -D_FILE_OFFSET_BITS=64 -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -pthread -pipe -fno-exceptions -fno-rtti -fdiagnostics-color -Wall -Wextra -Wno-unused-parameter -Wextra-semi -Wundef -std=c++17 -c ../../../tools/gn/src/base/files/file_path_constants.cc -o src/base/files/file_path_constants.o | ../../../tools/gn/src/base/files/file_path_constants.cc:7:10: fatal error: 'iterator' file not found | #include | ^~ | 1 error generated. | [2/195] CXX src/base/files/file_path.o | FAILED: src/base/files/file_path.o | clang++ -target x86_64-linux -MMD -MF src/base/files/file_path.o.d -I../../../tools/gn/src -I. -isystem/home/jovanbosic/Yocto/build/tmp/work/x86_64-linux/gn-native/106.0.5249.119-r0/recipe-sysroot-native/usr/include -O2 -pipe -isystem/home/jovanbosic/Yocto/build/tmp/work/x86_64-linux/gn-native/106.0.5249.119-r0/recipe-sysroot-native/usr/include -O2 -pipe -D_LIBCPP_HAS_NO_VENDOR_AVAILABILITY_ANNOTATIONS -DNDEBUG -O3 -fdata-sections -ffunction-sections -Werror -D_FILE_OFFSET_BITS=64 -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -pthread -pipe -fno-exceptions -fno-rtti -fdiagnostics-color -Wall -Wextra -Wno-unused-parameter -Wextra-semi -Wundef -std=c++17 -c ../../../tools/gn/src/base/files/file_path.cc -o src/base/files/file_path.o | In file included from ../../../tools/gn/src/base/files/file_path.cc:5: | ../../../tools/gn/src/base/files/file_path.h:107:10: fatal error: 'iosfwd' file not found | #include | ^~~~ | 1 error generated. | [3/195] CXX src/base/files/file.o | FAILED: src/base/files/file.o | clang++ -target x86_64-linux -MMD -MF src/base/files/file.o.d -I../../../tools/gn/src -I. -isystem/home/jovanbosic/Yocto/build/tmp/work/x86_64-linux/gn-native/106.0.5249.119-r0/recipe-sysroot-native/usr/include -O2 -pipe -isystem/home/jovanbosic/Yocto/build/tmp/work/x86_64-linux/gn-native/106.0.5249.119-r0/recipe-sysroot-native/usr/include -O2 -pipe -D_LIBCPP_HAS_NO_VENDOR_AVAILABILITY_ANNOTATIONS -DNDEBUG -O3 -fdata-sections -ffunction-sections -Werror -D_FILE_OFFSET_BITS=64 -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -pthread -pipe -fno-exceptions -fno-rtti -fdiagnostics-color -Wall -Wextra -Wno-unused-parameter -Wextra-semi -Wundef -std=c++17 -c ../../../tools/gn/src/base/files/file
Re: [yocto] gn-native_106.0.5249.119.bb:do_compile failed with exit code '1'
Is it something about compiler? -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#59004): https://lists.yoctoproject.org/g/yocto/message/59004 Mute This Topic: https://lists.yoctoproject.org/mt/96325807/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
