Re: [yocto] qemu segmentation fault on gobject-introspection
On Wed, Feb 20, 2019 at 3:51 PM João Gonçalves
wrote:
> Hello,
> when trying to migrate my build to master branch of oe layers I got this
> qemu segmentation fault during gobject-introspection.
> Does anyone have any clue on this?
>
This error means qemu is crashing while running some user mode application.
I am also seeing these errors on qemuarm but since qemuarm is moving away
from armv5te to armv7 I did not pay much attention to it
>
> Thank you,
> João Gonçalves
>
> | qemu: uncaught target signal 11 (Segmentation fault) - core dumped
> | Segmentation fault (core dumped)
> | If the above error message is about missing .so libraries, then setting
> up GIR_EXTRA_LIBS_PATH in the recipe should help.
> | (typically like this: GIR_EXTRA_LIBS_PATH="${B}/something/.libs" )
> | Command
> '['/home/joao/poky_imx6/build/tmp-glibc/work/cortexa9t2hf-neon-angstrom-linux-gnueabi/gobject-introspection/1.58.3-r0/build/g-ir-scanner-qemuwrapper',
> '/home/joao/poky_imx6/build/tmp-glibc/work/cortexa9t2hf-neon-angstrom-linux-gnueabi/gobject-introspection/1.58.3-r0/build/tmp-introspect5euoldbk/GLib-2.0',
> '--introspect-dump=/home/joao/poky_imx6/build/tmp-glibc/work/cortexa9t2hf-neon-angstrom-linux-gnueabi/gobject-introspection/1.58.3-r0/build/tmp-introspect5euoldbk/functions.txt,/home/joao/poky_imx6/build/tmp-glibc/work/cortexa9t2hf-neon-angstrom-linux-gnueabi/gobject-introspection/1.58.3-r0/build/tmp-introspect5euoldbk/dump.xml']'
> returned non-zero exit status 1.
> | ninja: build stopped: subcommand failed.
> | WARNING: exit code 1 from a shell command.
> | ERROR: Function failed: do_compile (log file is located at
> /home/joao/poky_imx6/build/tmp-glibc/work/cortexa9t2hf-neon-angstrom-linux-gnueabi/gobject-introspection/1.58.3-r0/temp/log.do_compile.20894)
> ERROR: Task
> (/home/joao/poky_imx6/poky/meta/recipes-gnome/gobject-introspection/gobject-introspection_1.58.3.bb:do_compile)
> failed with exit code '1'
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] qemu segmentation fault on gobject-introspection
Hello,
when trying to migrate my build to master branch of oe layers I got this
qemu segmentation fault during gobject-introspection.
Does anyone have any clue on this?
Thank you,
João Gonçalves
| qemu: uncaught target signal 11 (Segmentation fault) - core dumped
| Segmentation fault (core dumped)
| If the above error message is about missing .so libraries, then setting
up GIR_EXTRA_LIBS_PATH in the recipe should help.
| (typically like this: GIR_EXTRA_LIBS_PATH="${B}/something/.libs" )
| Command
'['/home/joao/poky_imx6/build/tmp-glibc/work/cortexa9t2hf-neon-angstrom-linux-gnueabi/gobject-introspection/1.58.3-r0/build/g-ir-scanner-qemuwrapper',
'/home/joao/poky_imx6/build/tmp-glibc/work/cortexa9t2hf-neon-angstrom-linux-gnueabi/gobject-introspection/1.58.3-r0/build/tmp-introspect5euoldbk/GLib-2.0',
'--introspect-dump=/home/joao/poky_imx6/build/tmp-glibc/work/cortexa9t2hf-neon-angstrom-linux-gnueabi/gobject-introspection/1.58.3-r0/build/tmp-introspect5euoldbk/functions.txt,/home/joao/poky_imx6/build/tmp-glibc/work/cortexa9t2hf-neon-angstrom-linux-gnueabi/gobject-introspection/1.58.3-r0/build/tmp-introspect5euoldbk/dump.xml']'
returned non-zero exit status 1.
| ninja: build stopped: subcommand failed.
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_compile (log file is located at
/home/joao/poky_imx6/build/tmp-glibc/work/cortexa9t2hf-neon-angstrom-linux-gnueabi/gobject-introspection/1.58.3-r0/temp/log.do_compile.20894)
ERROR: Task
(/home/joao/poky_imx6/poky/meta/recipes-gnome/gobject-introspection/gobject-introspection_1.58.3.bb:do_compile)
failed with exit code '1'
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [EXTERNAL] Problems using MIRRORS variables
Quick _workaround_:
1. Modify/extend your Repo manifest to pull your mirror repos to the
appropriate place under downloads/git2.
2. Override the non-sha1 SRCREVs with an appropriate SHA1.
Either in .bbappend files or via conf file extensions.
The mega-manual describes the latter in association with the
buildhistory-collect-srcrevs command.
Item 1 should not be needed, but it works.
One can make a fair case that item 2 SHOULD be done.
A mirror is NOT the same thing as the “official” repo. This also gives you A
clear way to record the version used for the build (though it might not have
been the way you planned). It is easier to make this case for branches/AUTOREV
than tags, but tags _can_ change and so fetchers bypass the download cache for
them.
Virgil Smith
FLIR Detection
From: yocto-boun...@yoctoproject.org On Behalf
Of Ryan Harkin
Sent: Wednesday, February 20, 2019 12:04
To: yocto@yoctoproject.org
Subject: [EXTERNAL] [yocto] Problems using MIRRORS variables
Hello,
I'm having a few problems when using the MIRRORS variable for GIT repos. I see
the same problems with the PREMIRRORS variable.
My use-case is:
1. company A has a private layer with SRC_URI that points to private git
2. company A needs to share layers with company B
3. company B cannot access company A's private git tree
4. company B has a mirror of the git trees with the same contents, including
SRC_URIs pointing to the company A private git trees
I have tried to resolve this using the MIRRORS variable in local.conf.
If SRCREV is a SHA, it seems to work for me.
However, it fails when the SRCREV is not a fixed SHA, eg. if SRCREV is a
branch, tag, or ${AUTOREV}. It looks like do_fetch is trying to pull the repo
to work out the SHA, but before decoding MIRRORS or PREMIRRORS. It appears to
do an ls-remote on the original repo, not the mirror, and fails.
The next issue is when using MIRRORS to replace a GIT repo with one using SSH.
This may simply be a syntax problem on my side.
Example:
MIRRORS += \
git://git.fake.org/landing-teams/working/qualcomm/wcnss-config.git
\
ssh://g...@git.linaro.org/landing-teams/working/qualcomm/wcnss-config.git;protocol=ssh
\n \
"
The MIRROR doesn't seem to be used at all in the above example. I've tried
adding ";protocol=https" to the first line; it doesn't help, and fails in a
different way, giving a "Exception: KeyError: 'protocol'" error.
I've shown detailed examples below. People may not need them, but if my email
isn't clear enough, hopefully they will help explain.
Setup
--
For an example, I'm using Linaro's OE-RPB master. More info here:
https://protect2.fireeye.com/url?k=e7212319-bb3560cf-e72339b5-0cc47aa8d93e-cd7528c3d8ac86ba=https://github.com/96boards/oe-rpb-manifest
First, set up the environment:
$ mkdir -p ${WORKSPACE}
$ repo init -u
https://protect2.fireeye.com/url?k=47a0bd31-1bb4fee7-47a2a79d-0cc47aa8d93e-27ddccb5db2a6c87=https://github.com/96boards/oe-rpb-manifest.git
-b master
$ repo sync
$ export MACHINE=dragonboard-410c ; export DISTRO=rpb ; . setup-environment
Then, make sure it's working:
$ bitbake -c do_fetch wcnss-config
Mod a recipe to use a fake SRC_URI, and test that it no longer works.
$ sed -i
${WORKSPACE}/layers/meta-qcom/recipes-bsp/wcnss-config/wcnss-config_1.13.bb
-e
's#git.linaro.org#git.fake.org#g'
$ rm -rf tmp-rpb-glibc/ ../downloads/git2/*wcnss-config*
$ bitbake -c do_fetch wcnss-config
I see this error output, as expected:
WARNING: wcnss-config-1.13-r0 do_fetch: Failed to fetch URL
git://git.fake.org/landing-teams/working/qualcomm/wcnss-config.git;branch=master;protocol=https,
attempting MIRRORS if available
ERROR: wcnss-config-1.13-r0 do_fetch: Fetcher failure: Fetch command export
PSEUDO_DISABLED=1; export
[yocto] [meta-mingw][PATCH] classes/toolchain-scripts-mingw32: Fix bad cmd flag
The command to properly set the exit code at the end of the toolchain
environment was using the correct flag delimiter '/', but the code to
coerce all the unix-style paths to windows paths was incorrectly
changing this to a '\'. This worked find in wines cmd, but on an actual
Windows host, this caused cmd to wait indefinitely. Fix this by
appending the command after the path separators are coerced.
Signed-off-by: Joshua Watt
---
classes/toolchain-scripts-mingw32.bbclass | 22 +++---
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git a/classes/toolchain-scripts-mingw32.bbclass
b/classes/toolchain-scripts-mingw32.bbclass
index 32493d7..0afbf7d 100644
--- a/classes/toolchain-scripts-mingw32.bbclass
+++ b/classes/toolchain-scripts-mingw32.bbclass
@@ -38,6 +38,17 @@ toolchain_create_sdk_env_script_sdkmingw32 () {
# Change unix '/' to Win32 '\'
sed -e 's,/,\\,g' -i $script
+ # set has some annoying properties:
+ # 1) If it is successful %ERRORLEVEL% is unchanged (as opposed to being
set
+ #to 0 to indicate success)
+ # 2) Making an assignment like "set A=" is considered an error and sets
+ #%ERRORLEVEL% to 1.
+ #
+ # Practically, this means that if any of the set calls make an empty
+ # assignment that error will be propagated. To prevent this, a command
is
+ # run to ensure that the "exit code" of this script is 0
+ echo "@%COMSPEC% /C exit 0 > NUL" >> $script
+
# Make the file windows friendly...
awk 'sub("$", "\r")' $script > $script.new
mv $script.new $script
@@ -81,17 +92,6 @@ toolchain_shared_env_script_sdkmingw32 () {
FOR %%x IN (%OECORE_NATIVE_SYSROOT%\\environment-setup.d\\*.bat) DO call
"%%x"
)
EOF
-
- # set has some annoying properties:
- # 1) If it is successful %ERRORLEVEL% is unchanged (as opposed to being
set
- #to 0 to indicate success)
- # 2) Making an assignment like "set A=" is considered an error and sets
- #%ERRORLEVEL% to 1.
- #
- # Practically, this means that if any of the set calls make an empty
- # assignment that error will be propagated. To prevent this, a command
is
- # run to ensure that the "exit code" of this script is 0
- echo "@%COMSPEC% /C exit 0 > NUL" >> $script
}
toolchain_create_sdk_siteconfig_append_sdkmingw32 () {
--
2.20.1
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-mingw][PATCH] diffutils: Upgrade to 3.7
Upgrade diffutils from 3.6 to 3.7. The upstream made several fixes so
the local patches are no longer necessary, but the gnulib-tests need to
be dropped since they do not compile properly. Since there are no more
local patches, the bbappend can be made to match all versions.
Signed-off-by: Joshua Watt
---
.../diffutils/diffutils/sdiff-no-kill.patch | 32 ---
.../diffutils/diffutils_%.bbappend| 14
.../diffutils/diffutils_3.6.bbappend | 18 ---
3 files changed, 14 insertions(+), 50 deletions(-)
delete mode 100644 recipes-extended/diffutils/diffutils/sdiff-no-kill.patch
create mode 100644 recipes-extended/diffutils/diffutils_%.bbappend
delete mode 100644 recipes-extended/diffutils/diffutils_3.6.bbappend
diff --git a/recipes-extended/diffutils/diffutils/sdiff-no-kill.patch
b/recipes-extended/diffutils/diffutils/sdiff-no-kill.patch
deleted file mode 100644
index c9fbc24..000
--- a/recipes-extended/diffutils/diffutils/sdiff-no-kill.patch
+++ /dev/null
@@ -1,32 +0,0 @@
-Upstream-Status: Backport
-Signed-off-by: Ross Burton
-
-From 56225ecca4f9598c0c9dbd7c46a51dd4816a383f Mon Sep 17 00:00:00 2001
-From: Paul Eggert
-Date: Fri, 20 Apr 2018 13:39:15 -0700
-Subject: sdiff: port to mingw
-MIME-Version: 1.0
-Content-Type: text/plain; charset=UTF-8
-Content-Transfer-Encoding: 8bit
-
-Problem reported by Ross Burton (Bug#31218).
-* src/sdiff.c (checksigs): Use ‘raise’, not ‘kill’.
- src/sdiff.c | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/src/sdiff.c b/src/sdiff.c
-index 1b23a0c..b08bc74 100644
a/src/sdiff.c
-+++ b/src/sdiff.c
-@@ -805,7 +805,7 @@ checksigs (void)
-
- /* Yield an exit status indicating that a signal was received. */
- untrapsig (s);
-- kill (getpid (), s);
-+ raise (s);
-
- /* That didn't work, so exit with error status. */
- exit (EXIT_TROUBLE);
---
-cgit v1.0-41-gc330
diff --git a/recipes-extended/diffutils/diffutils_%.bbappend
b/recipes-extended/diffutils/diffutils_%.bbappend
new file mode 100644
index 000..2c54a55
--- /dev/null
+++ b/recipes-extended/diffutils/diffutils_%.bbappend
@@ -0,0 +1,14 @@
+FILESEXTRAPATHS_prepend_mingw32 := "${THISDIR}/${BPN}:"
+
+# Add some definitions for POSIX signals..
+CFLAGS_append_mingw32 = " -DSIGALRM=14 -DSIGHUP=1 -DSIGQUIT=3 -DSIGPIPE=13
-DSIGTSTP=18 -DSIGSTOP=17 "
+
+do_configure_prepend_mingw32 () {
+# Remove building of "man" and "gnulib-tests". The tests don't
+# cross-compile for mingw, but we aren't using them anyway
+sed -i \
+-e 's:^SUBDIRS =\(.*\) man\>:SUBDIRS = \1 :g' \
+-e 's:^SUBDIRS =\(.*\) gnulib-tests\>:SUBDIRS = \1 :g' \
+${S}/Makefile.am
+}
+
diff --git a/recipes-extended/diffutils/diffutils_3.6.bbappend
b/recipes-extended/diffutils/diffutils_3.6.bbappend
deleted file mode 100644
index f301349..000
--- a/recipes-extended/diffutils/diffutils_3.6.bbappend
+++ /dev/null
@@ -1,18 +0,0 @@
-
-FILESEXTRAPATHS_prepend_mingw32 := "${THISDIR}/${BPN}:"
-
-SRC_URI_remove_mingw32 =
"file://0001-explicitly-disable-replacing-getopt.patch"
-SRC_URI_append_mingw32 = " file://sdiff-no-kill.patch"
-
-CACHED_CONFIGUREVARS_append_mingw32 = " ac_cv_header_getopt_h=yes "
-
-# Add some definitions for POSIX signals..
-CFLAGS_append_mingw32 = " -DSIGALRM=14 -DSIGHUP=1 -DSIGQUIT=3 -DSIGPIPE=13
-DSIGTSTP=18 -DSIGSTOP=17 "
-
-do_configure_prepend_mingw32 () {
-# Remove building of "man"
-sed -i -e 's:^SUBDIRS = lib src tests doc man po gnulib-test:SUBDIRS = lib
src tests doc po gnulib-test:g' ${S}/Makefile.am
-}
-
-
-
--
2.20.1
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] local.conf confusion
Well, I'm feeling bad, the Yocto system that I'm using is from Qt for their
Boot2Qt builds. It seems that the include is pointing their private dir tree.
Sorry for bothering the list with this noise.
Regards,
Greg Wilson-Lindberg
> -Original Message-
> From: Greg Wilson-Lindberg
> Sent: Wednesday, February 20, 2019 10:16 AM
> To: yocto@yoctoproject.org
> Subject: local.conf confusion
>
> Hello list,
>
> I've run into a confusion that should be simple. I've got a build based on
> sumo, at the
> bottom of my local.conf file is the line:
>
> include conf/distro/include/${MACHINE}.pre.inc
>
> This should be straight forward, just find the conf/distro/include directory
> and all of
> the *.pre.inc files should be there. I just searched all of the sources
> directory
> for '*.pre.inc' and I get nothing. I'm building for a raspberry pi3, so I
> would expect at
> least 'raspberry*.inc', still nothing. I'm not getting an error for bitbake
> not being able
> to find the file.
>
> So where do I find the machine include files?
>
> Regards,
> Greg Wilson-Lindberg
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] local.conf confusion
Greg,
I am not entirely sure why you are including a machine configuration
include file into your conf/local.conf file.
However, the "include" directive is optional include and hence if the
file is not found Bitbake will not raise an error and terminate. If you
need that behavior use "require" instead.
Machine configuration files do commonly use includes for shared
configuration. You typically find them where the machine configuration
files are: conf/machine or in a subdirectory there. The directory
conf/machine is commonly found in BSP layers such as meta-raspberrypi
which you are probably using as you are building for RPi.
:rjs
On 2/20/19 10:16 AM, Greg Wilson-Lindberg wrote:
> Hello list,
>
> I've run into a confusion that should be simple. I've got a build based on
> sumo, at the bottom of my local.conf file is the line:
>
> include conf/distro/include/${MACHINE}.pre.inc
>
> This should be straight forward, just find the conf/distro/include directory
> and all of the *.pre.inc files should be there. I just searched all of the
> sources directory for '*.pre.inc' and I get nothing. I'm building for a
> raspberry pi3, so I would expect at least 'raspberry*.inc', still nothing.
> I'm not getting an error for bitbake not being able to find the file.
>
> So where do I find the machine include files?
>
> Regards,
> Greg Wilson-Lindberg
>
signature.asc
Description: OpenPGP digital signature
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] local.conf confusion
Hello list,
I've run into a confusion that should be simple. I've got a build based on
sumo, at the bottom of my local.conf file is the line:
include conf/distro/include/${MACHINE}.pre.inc
This should be straight forward, just find the conf/distro/include directory
and all of the *.pre.inc files should be there. I just searched all of the
sources directory for '*.pre.inc' and I get nothing. I'm building for a
raspberry pi3, so I would expect at least 'raspberry*.inc', still nothing. I'm
not getting an error for bitbake not being able to find the file.
So where do I find the machine include files?
Regards,
Greg Wilson-Lindberg
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-mingw][PATCH] diffutils: Upgrade to 3.7
On Wed, 2019-02-20 at 19:13 +0100, Alexander Kanavin wrote: > On Wed, 20 Feb 2019 at 19:08, Joshua Watt > wrote: > > .../diffutils/diffutils/sdiff-no-kill.patch | 32 - > > -- > > .../diffutils/diffutils_3.6.bbappend | 18 --- > > .../diffutils/diffutils_3.7.bbappend | 14 > > Should this be called simply diffutils_%.bbappend ? > This way things won't suddenly break when oe-core gets a new version. > (a possible resulting build failure is better than a certain parsing > failure imo) Ya, that seems reasonable now that the local patches have been removed. > > Alex -- Joshua Watt -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [meta-mingw][PATCH] diffutils: Upgrade to 3.7
On Wed, 20 Feb 2019 at 19:08, Joshua Watt wrote: > .../diffutils/diffutils/sdiff-no-kill.patch | 32 --- > .../diffutils/diffutils_3.6.bbappend | 18 --- > .../diffutils/diffutils_3.7.bbappend | 14 Should this be called simply diffutils_%.bbappend ? This way things won't suddenly break when oe-core gets a new version. (a possible resulting build failure is better than a certain parsing failure imo) Alex -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] [meta-mingw][PATCH] diffutils: Upgrade to 3.7
Upgrade diffutils from 3.6 to 3.7. The upstream made several fixes so
the local patches are no longer necessary, but the gnulib-tests need to
be dropped since they do not compile properly
Signed-off-by: Joshua Watt
---
.../diffutils/diffutils/sdiff-no-kill.patch | 32 ---
.../diffutils/diffutils_3.6.bbappend | 18 ---
.../diffutils/diffutils_3.7.bbappend | 14
3 files changed, 14 insertions(+), 50 deletions(-)
delete mode 100644 recipes-extended/diffutils/diffutils/sdiff-no-kill.patch
delete mode 100644 recipes-extended/diffutils/diffutils_3.6.bbappend
create mode 100644 recipes-extended/diffutils/diffutils_3.7.bbappend
diff --git a/recipes-extended/diffutils/diffutils/sdiff-no-kill.patch
b/recipes-extended/diffutils/diffutils/sdiff-no-kill.patch
deleted file mode 100644
index c9fbc24..000
--- a/recipes-extended/diffutils/diffutils/sdiff-no-kill.patch
+++ /dev/null
@@ -1,32 +0,0 @@
-Upstream-Status: Backport
-Signed-off-by: Ross Burton
-
-From 56225ecca4f9598c0c9dbd7c46a51dd4816a383f Mon Sep 17 00:00:00 2001
-From: Paul Eggert
-Date: Fri, 20 Apr 2018 13:39:15 -0700
-Subject: sdiff: port to mingw
-MIME-Version: 1.0
-Content-Type: text/plain; charset=UTF-8
-Content-Transfer-Encoding: 8bit
-
-Problem reported by Ross Burton (Bug#31218).
-* src/sdiff.c (checksigs): Use ‘raise’, not ‘kill’.
- src/sdiff.c | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/src/sdiff.c b/src/sdiff.c
-index 1b23a0c..b08bc74 100644
a/src/sdiff.c
-+++ b/src/sdiff.c
-@@ -805,7 +805,7 @@ checksigs (void)
-
- /* Yield an exit status indicating that a signal was received. */
- untrapsig (s);
-- kill (getpid (), s);
-+ raise (s);
-
- /* That didn't work, so exit with error status. */
- exit (EXIT_TROUBLE);
---
-cgit v1.0-41-gc330
diff --git a/recipes-extended/diffutils/diffutils_3.6.bbappend
b/recipes-extended/diffutils/diffutils_3.6.bbappend
deleted file mode 100644
index f301349..000
--- a/recipes-extended/diffutils/diffutils_3.6.bbappend
+++ /dev/null
@@ -1,18 +0,0 @@
-
-FILESEXTRAPATHS_prepend_mingw32 := "${THISDIR}/${BPN}:"
-
-SRC_URI_remove_mingw32 =
"file://0001-explicitly-disable-replacing-getopt.patch"
-SRC_URI_append_mingw32 = " file://sdiff-no-kill.patch"
-
-CACHED_CONFIGUREVARS_append_mingw32 = " ac_cv_header_getopt_h=yes "
-
-# Add some definitions for POSIX signals..
-CFLAGS_append_mingw32 = " -DSIGALRM=14 -DSIGHUP=1 -DSIGQUIT=3 -DSIGPIPE=13
-DSIGTSTP=18 -DSIGSTOP=17 "
-
-do_configure_prepend_mingw32 () {
-# Remove building of "man"
-sed -i -e 's:^SUBDIRS = lib src tests doc man po gnulib-test:SUBDIRS = lib
src tests doc po gnulib-test:g' ${S}/Makefile.am
-}
-
-
-
diff --git a/recipes-extended/diffutils/diffutils_3.7.bbappend
b/recipes-extended/diffutils/diffutils_3.7.bbappend
new file mode 100644
index 000..2c54a55
--- /dev/null
+++ b/recipes-extended/diffutils/diffutils_3.7.bbappend
@@ -0,0 +1,14 @@
+FILESEXTRAPATHS_prepend_mingw32 := "${THISDIR}/${BPN}:"
+
+# Add some definitions for POSIX signals..
+CFLAGS_append_mingw32 = " -DSIGALRM=14 -DSIGHUP=1 -DSIGQUIT=3 -DSIGPIPE=13
-DSIGTSTP=18 -DSIGSTOP=17 "
+
+do_configure_prepend_mingw32 () {
+# Remove building of "man" and "gnulib-tests". The tests don't
+# cross-compile for mingw, but we aren't using them anyway
+sed -i \
+-e 's:^SUBDIRS =\(.*\) man\>:SUBDIRS = \1 :g' \
+-e 's:^SUBDIRS =\(.*\) gnulib-tests\>:SUBDIRS = \1 :g' \
+${S}/Makefile.am
+}
+
--
2.20.1
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
[yocto] Problems using MIRRORS variables
Hello,
I'm having a few problems when using the MIRRORS variable for GIT repos. I
see the same problems with the PREMIRRORS variable.
My use-case is:
1. company A has a private layer with SRC_URI that points to private git
2. company A needs to share layers with company B
3. company B cannot access company A's private git tree
4. company B has a mirror of the git trees with the same contents,
including SRC_URIs pointing to the company A private git trees
I have tried to resolve this using the MIRRORS variable in local.conf.
If SRCREV is a SHA, it seems to work for me.
However, it fails when the SRCREV is not a fixed SHA, eg. if SRCREV is a
branch, tag, or ${AUTOREV}. It looks like do_fetch is trying to pull the
repo to work out the SHA, but before decoding MIRRORS or PREMIRRORS. It
appears to do an ls-remote on the original repo, not the mirror, and fails.
The next issue is when using MIRRORS to replace a GIT repo with one using
SSH. This may simply be a syntax problem on my side.
Example:
MIRRORS += \
git://git.fake.org/landing-teams/working/qualcomm/wcnss-config.git \
ssh://
g...@git.linaro.org/landing-teams/working/qualcomm/wcnss-config.git;protocol=ssh
\n \
"
The MIRROR doesn't seem to be used at all in the above example. I've tried
adding ";protocol=https" to the first line; it doesn't help, and fails in a
different way, giving a "Exception: KeyError: 'protocol'" error.
I've shown detailed examples below. People may not need them, but if my
email isn't clear enough, hopefully they will help explain.
Setup
--
For an example, I'm using Linaro's OE-RPB master. More info here:
https://github.com/96boards/oe-rpb-manifest
First, set up the environment:
$ mkdir -p ${WORKSPACE}
$ repo init -u https://github.com/96boards/oe-rpb-manifest.git -b master
$ repo sync
$ export MACHINE=dragonboard-410c ; export DISTRO=rpb ; .
setup-environment
Then, make sure it's working:
$ bitbake -c do_fetch wcnss-config
Mod a recipe to use a fake SRC_URI, and test that it no longer works.
$ sed -i ${WORKSPACE}/layers/meta-qcom/recipes-bsp/wcnss-config/
wcnss-config_1.13.bb -e 's#git.linaro.org#git.fake.org#g'
$ rm -rf tmp-rpb-glibc/ ../downloads/git2/*wcnss-config*
$ bitbake -c do_fetch wcnss-config
I see this error output, as expected:
WARNING: wcnss-config-1.13-r0 do_fetch: Failed to fetch URL git://
git.fake.org/landing-teams/working/qualcomm/wcnss-config.git;branch=master;protocol=https,
attempting MIRRORS if available
ERROR: wcnss-config-1.13-r0 do_fetch: Fetcher failure: Fetch command export
PSEUDO_DISABLED=1; export
DBUS_SESSION_BUS_ADDRESS="unix:path=/run/user/1000/bus"; export
SSH_AGENT_PID="3371"; export SSH_AUTH_SOCK="/run/user/1000/keyring/ssh";
export
PATH="/linaro/oe-rpb-workspace-testing/layers/openembedded-core/scripts:/linaro/oe-rpb-workspace-testing/build-rpb/tmp-rpb-glibc/work/all-linaro-linux/wcnss-config/1.13-r0/recipe-sysroot-native/usr/bin/allarch-linaro-linux:/linaro/oe-rpb-workspace-testing/build-rpb/tmp-rpb-glibc/work/all-linaro-linux/wcnss-config/1.13-r0/recipe-sysroot/usr/bin/crossscripts:/linaro/oe-rpb-workspace-testing/build-rpb/tmp-rpb-glibc/work/all-linaro-linux/wcnss-config/1.13-r0/recipe-sysroot-native/usr/sbin:/linaro/oe-rpb-workspace-testing/build-rpb/tmp-rpb-glibc/work/all-linaro-linux/wcnss-config/1.13-r0/recipe-sysroot-native/usr/bin:/linaro/oe-rpb-workspace-testing/build-rpb/tmp-rpb-glibc/work/all-linaro-linux/wcnss-config/1.13-r0/recipe-sysroot-native/sbin:/linaro/oe-rpb-workspace-testing/build-rpb/tmp-rpb-glibc/work/all-linaro-linux/wcnss-config/1.13-r0/recipe-sysroot-native/bin:/linaro/oe-rpb-workspace-testing/bitbake/bin:/linaro/oe-rpb-workspace-testing/build-rpb/tmp-rpb-glibc/hosttools";
export HOME="/home/ryan"; LANG=C git -c core.fsyncobjectfiles=0 clone
--bare --mirror
https://git.fake.org/landing-teams/working/qualcomm/wcnss-config.git
/linaro/oe-rpb-workspace-testing/downloads/git2/git.fake.org.landing-teams.working.qualcomm.wcnss-config.git
--progress failed with exit code 128, output:
Cloning into bare repository
'/linaro/oe-rpb-workspace-testing/downloads/git2/git.fake.org.landing-teams.working.qualcomm.wcnss-config.git'...
fatal: unable to access '
https://git.fake.org/landing-teams/working/qualcomm/wcnss-config.git/':
Could not resolve host: git.fake.org
ERROR: wcnss-config-1.13-r0 do_fetch: Fetcher failure for URL: 'git://
git.fake.org/landing-teams/working/qualcomm/wcnss-config.git;branch=master;protocol=https'.
Unable to fetch URL from any source.
ERROR: wcnss-config-1.13-r0 do_fetch:
ERROR: wcnss-config-1.13-r0 do_fetch: Function failed: base_do_fetch
ERROR: Logfile of failure stored in:
/linaro/oe-rpb-workspace-testing/build-rpb/tmp-rpb-glibc/work/all-linaro-linux/wcnss-config/1.13-r0/temp/log.do_fetch.2525
ERROR: Task
Re: [yocto] Add new compiler macro
On Wed, Feb 20, 2019 at 12:42 AM wrote: > Hi, > > i tried to add CFLAGS += "-MMC_WRITE" > (i dont know if -DMMC_WRITE was a typo or not and tryed both) > -D is right way to pass defines it seems your makefiles are ignoring cflags so you might have to fix that > > > i dont get any error but in my recipes the code wrapped in > #ifdef MMC_WRITE > #endif > > is not compiled... i even tried to add a sintax error between the ifdef > so, if compiler see MMC_WRITE macro, i should get a compiler error but i > don't. > > Im still missing something? > > code example : > > #ifdef MMC_WRITE > dev_info(host->parent , "retune_now MMC !!! \n\r"); asdasdasd > //asdasdasdasd is a syntax error that should came out > > #elif SD_WRITE > > Thanks > > Il 18 febbraio 2019 alle 16.45 Khem Raj ha scritto: > > On Mon, Feb 18, 2019 at 7:43 AM wrote: > > > > Hi, i wanted to add a compiler macro (NEW_MACRO) in order to compile all > the code hidden beetween > > #ifdef NEW_MACRO > > #endif > in all my recipes. I think that the right place to do that is in > bitbake.conf file present under poky/meta/conf but when i try to do: > > TARGET_CPPFLAGS += "-MMC_WRITE" > > it depends on recipes respecting compiler flags from environment but > most of them do. > > CFLAGS += "-DMMC_WRITE" could do it. > > > > > I get the error : > configure: error: cannot compute suffix of object files: cannot compile > > How can i send the macro to the compiler in the correct way? > > Thanks > > -- > > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] icecast error
Good morning. I'm trying to compile the icecast, and I had this issue: Initialising tasks: 100% |#| Time: 0:00:03 NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks ERROR: icecast-2.3.2-r2 do_compile: oe_runmake failed ERROR: icecast-2.3.2-r2 do_compile: Function failed: do_compile (log file is located at /home/igor/oe-core/build/tmp-glibc/work/armv7at2hf-neon-angstrom-linux-gnueabi/icecast/2.3.2-r2/temp/log.do_compile.38033) ERROR: Logfile of failure stored in: /home/igor/oe-core/build/tmp-glibc/work/armv7at2hf-neon-angstrom-linux-gnueabi/icecast/2.3.2-r2/temp/log.do_compile.38033 Log data follows: | DEBUG: SITE files ['endian-little', 'bit-32', 'arm-common', 'arm-32', 'common-linux', 'common-glibc', 'arm-linux', 'arm-linux-gnueabi', 'common'] | DEBUG: Executing shell function do_compile | NOTE: make -j 1 | make all-recursive | make[1]: Entering directory '/home/igor/oe-core/build/tmp-glibc/work/armv7at2hf-neon-angstrom-linux-gnueabi/icecast/2.3.2-r2/build' | Making all in src | make[2]: Entering directory '/home/igor/oe-core/build/tmp-glibc/work/armv7at2hf-neon-angstrom-linux-gnueabi/icecast/2.3.2-r2/build/src' | Making all in avl | make[3]: Entering directory '/home/igor/oe-core/build/tmp-glibc/work/armv7at2hf-neon-angstrom-linux-gnueabi/icecast/2.3.2-r2/build/src/avl' | ../../arm-angstrom-linux-gnueabi-libtool --tag=CC --mode=compile arm-angstrom-linux-gnueabi-gcc -march=armv7-a -mthumb -mfpu=neon -mfloat-abi=hard --sysroot=/home/igor/oe-core/build/tmp-glibc/sysroots/apalis-imx6 -DHAVE_CONFIG_H -I. -I../../../icecast-2.3.2/src/avl -I../.. -I../../../icecast-2.3.2/src/avl/.. -pthread -O2 -pipe -g -feliminate-unused-debug-types -fdebug-prefix-map=/home/igor/oe-core/build/tmp-glibc/work/armv7at2hf-neon-angstrom-linux-gnueabi/icecast/2.3.2-r2=/usr/src/debug/icecast/2.3.2-r2 -fdebug-prefix-map=/home/igor/oe-core/build/tmp-glibc/sysroots/x86_64-linux= -fdebug-prefix-map=/home/igor/oe-core/build/tmp-glibc/sysroots/apalis-imx6= -c -o libiceavl_la-avl.lo `test -f 'avl.c' || echo '../../../icecast-2.3.2/src/avl/'`avl.c | arm-angstrom-linux-gnueabi-libtool: compile: arm-angstrom-linux-gnueabi-gcc -march=armv7-a -mthumb -mfpu=neon -mfloat-abi=hard --sysroot=/home/igor/oe-core/build/tmp-glibc/sysroots/apalis-imx6 -DHAVE_CONFIG_H -I. -I../../../icecast-2.3.2/src/avl -I../.. -I../../../icecast-2.3.2/src/avl/.. -pthread -O2 -pipe -g -feliminate-unused-debug-types -fdebug-prefix-map=/home/igor/oe-core/build/tmp-glibc/work/armv7at2hf-neon-angstrom-linux-gnueabi/icecast/2.3.2-r2=/usr/src/debug/icecast/2.3.2-r2 -fdebug-prefix-map=/home/igor/oe-core/build/tmp-glibc/sysroots/x86_64-linux= -fdebug-prefix-map=/home/igor/oe-core/build/tmp-glibc/sysroots/apalis-imx6= -c ../../../icecast-2.3.2/src/avl/avl.c -fPIC -DPIC -o .libs/libiceavl_la-avl.o | arm-angstrom-linux-gnueabi-libtool: compile: arm-angstrom-linux-gnueabi-gcc -march=armv7-a -mthumb -mfpu=neon -mfloat-abi=hard --sysroot=/home/igor/oe-core/build/tmp-glibc/sysroots/apalis-imx6 -DHAVE_CONFIG_H -I. -I../../../icecast-2.3.2/src/avl -I../.. -I../../../icecast-2.3.2/src/avl/.. -pthread -O2 -pipe -g -feliminate-unused-debug-types -fdebug-prefix-map=/home/igor/oe-core/build/tmp-glibc/work/armv7at2hf-neon-angstrom-linux-gnueabi/icecast/2.3.2-r2=/usr/src/debug/icecast/2.3.2-r2 -fdebug-prefix-map=/home/igor/oe-core/build/tmp-glibc/sysroots/x86_64-linux= -fdebug-prefix-map=/home/igor/oe-core/build/tmp-glibc/sysroots/apalis-imx6= -c ../../../icecast-2.3.2/src/avl/avl.c -o libiceavl_la-avl.o >/dev/null 2>&1 | ../../arm-angstrom-linux-gnueabi-libtool --tag=CC --mode=link arm-angstrom-linux-gnueabi-gcc -march=armv7-a -mthumb -mfpu=neon -mfloat-abi=hard --sysroot=/home/igor/oe-core/build/tmp-glibc/sysroots/apalis-imx6 -pthread -O2 -pipe -g -feliminate-unused-debug-types -fdebug-prefix-map=/home/igor/oe-core/build/tmp-glibc/work/armv7at2hf-neon-angstrom-linux-gnueabi/icecast/2.3.2-r2=/usr/src/debug/icecast/2.3.2-r2 -fdebug-prefix-map=/home/igor/oe-core/build/tmp-glibc/sysroots/x86_64-linux= -fdebug-prefix-map=/home/igor/oe-core/build/tmp-glibc/sysroots/apalis-imx6= -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -o libiceavl.la libiceavl_la-avl.lo | arm-angstrom-linux-gnueabi-libtool: link: arm-angstrom-linux-gnueabi-ar cru .libs/libiceavl.a .libs/libiceavl_la-avl.o | arm-angstrom-linux-gnueabi-ar: `u' modifier ignored since `D' is the default (see `U') | arm-angstrom-linux-gnueabi-libtool: link: arm-angstrom-linux-gnueabi-ranlib .libs/libiceavl.a | arm-angstrom-linux-gnueabi-libtool: link: ( cd ".libs" && rm -f " libiceavl.la" && ln -s "../libiceavl.la" "libiceavl.la" ) | make[3]: Leaving directory '/home/igor/oe-core/build/tmp-glibc/work/armv7at2hf-neon-angstrom-linux-gnueabi/icecast/2.3.2-r2/build/src/avl' | Making all in thread | make[3]: Entering directory
Re: [yocto] Add cmd.py library for python-core package
śr., 20 lut 2019 o 12:30 Alexander Kanavin napisał(a): > > On Wed, 20 Feb 2019 at 12:25, Piotr Piwko wrote: > > I would like to add cmd.py library to my final image. In order to do > > so I modified python2-manifest.json file from poky delivery. > I'm not sure why you had to modify the manifest, as cmd.py is provided > by python-shell package according to the manifest. Yes, you are right. I've overlooked it. Thanks a lot! -- Piotr Piwko http://www.embedded-engineering.pl/ -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Add cmd.py library for python-core package
On Wed, 20 Feb 2019 at 12:25, Piotr Piwko wrote: > I would like to add cmd.py library to my final image. In order to do > so I modified python2-manifest.json file from poky delivery. > > This solution works fine. However, is there any possibility to do not > change the global poky/python2-manifest,json file and get the same > result? I would like to provide this library only for particular image > not for all my supported ones. I tried to put new manifest file in > upper layers of my meta, but it seems to not be taken into > consideration by python recipe. I'm not sure why you had to modify the manifest, as cmd.py is provided by python-shell package according to the manifest. If you show your changes, it may be easier to understand the issue. Alex -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Add cmd.py library for python-core package
Hi, I would like to add cmd.py library to my final image. In order to do so I modified python2-manifest.json file from poky delivery. This solution works fine. However, is there any possibility to do not change the global poky/python2-manifest,json file and get the same result? I would like to provide this library only for particular image not for all my supported ones. I tried to put new manifest file in upper layers of my meta, but it seems to not be taken into consideration by python recipe. Thanks in advance for help. -- Piotr Piwko http://www.embedded-engineering.pl/ -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Add new compiler macro
Hi, i tried to add CFLAGS += "-MMC_WRITE" (i dont know if -DMMC_WRITE was a typo or not and tryed both) i dont get any error but in my recipes the code wrapped in #ifdef MMC_WRITE #endif is not compiled... i even tried to add a sintax error between the ifdef so, if compiler see MMC_WRITE macro, i should get a compiler error but i don't. Im still missing something? code example : #ifdef MMC_WRITE dev_info(host->parent , "retune_now MMC !!! \n\r"); asdasdasd //asdasdasdasd is a syntax error that should came out #elif SD_WRITE Thanks > > Il 18 febbraio 2019 alle 16.45 Khem Raj ha scritto: > > On Mon, Feb 18, 2019 at 7:43 AM wrote: > > > > > > > > Hi, i wanted to add a compiler macro (NEW_MACRO) in order to > > compile all the code hidden beetween > > > > #ifdef NEW_MACRO > > > > #endif > > in all my recipes. I think that the right place to do that is in > > bitbake.conf file present under poky/meta/conf but when i try to do: > > > > TARGET_CPPFLAGS += "-MMC_WRITE" > > > > > > it depends on recipes respecting compiler flags from environment but > most of them do. > > CFLAGS += "-DMMC_WRITE" could do it. > > > > > > > > > I get the error : > > configure: error: cannot compute suffix of object files: cannot > > compile > > > > How can i send the macro to the compiler in the correct way? > > > > Thanks > > > > -- > > > > ___ > > yocto mailing list > > yocto@yoctoproject.org > > https://lists.yoctoproject.org/listinfo/yocto > > > > > -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
