Re: [OE-core] [PATCH] sysvinit rc: Use PSPLASH_FIFO_DIR for progress fifo
I was meaning to send the backport request as well. This is a long standing
bug and rc hasn't changed in quite some time, so the patch should apply
cleanly to dunfell.
Should I send the patch for dunfell, or can
c19c69ae8ddcb37ad5683b6962ec3def37ad4512 be cherry-picked?
Michael
On Sat, Sep 26, 2020 at 12:26 PM Randy MacLeod
wrote:
> Add Steve, who maintains dunfell.
>
> On 2020-09-26 7:27 a.m., mihai.lind...@gmail.com wrote:
> > Please backport this to dunfell.
>
> Hi Mihai,
>
> Steve might do that but it would be better if you
> could cherry-pick it back, test it, and send a patch:
>http://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded
>
> Thanks,
>
> ../Randy
>
> >
> > Thanks,
> > Mihai
> >
> > On Sat, Aug 29, 2020 at 06:09 AM, Michael Gloff wrote:
> >
> >>
> >> psplash expects the fifo to be in /run or specified
> >> by PSPLASH_FIFO_DIR. This patch allows psplash to
> >> quit normally. Also, fix the work around of using
> >> echo directly into the fifo and use psplash-write.
> >>
> >> Signed-off-by: Michael Gloff
> >> ---
> >> meta/recipes-core/sysvinit/sysvinit/rc | 9 +++--
> >> 1 file changed, 3 insertions(+), 6 deletions(-)
> >>
> >> diff --git a/meta/recipes-core/sysvinit/sysvinit/rc
> >> b/meta/recipes-core/sysvinit/sysvinit/rc
> >> index 7ca41ae1ae..fd1fdd26ba 100755
> >> --- a/meta/recipes-core/sysvinit/sysvinit/rc
> >> +++ b/meta/recipes-core/sysvinit/sysvinit/rc
> >> @@ -26,11 +26,8 @@ startup_progress() {
> >> progress=$progress_size
> >> fi
> >> #echo "PROGRESS is $progress $runlevel $first_step + ($step of
> >> $num_steps) $step_change $progress_size"
> >> -#if type psplash-write >/dev/null 2>&1; then
> >> -#TMPDIR=/mnt/.psplash psplash-write "PROGRESS $progress" ||
> true
> >> -#fi
> >> -if [ -e /mnt/.psplash/psplash_fifo ]; then
> >> -echo "PROGRESS $progress" > /mnt/.psplash/psplash_fifo
> >> +if type psplash-write >/dev/null 2>&1; then
> >> +PSPLASH_FIFO_DIR=/mnt/.psplash psplash-write "PROGRESS
> $progress" ||
> >> true
> >> fi
> >> }
> >>
> >> @@ -176,7 +173,7 @@ startup() {
> >> #Uncomment to cause psplash to exit manually, otherwise it exits when
> it sees
> >> a VC switch
> >> if [ "x$runlevel" != "xS" ] && [ ! -x
> /etc/rc${runlevel}.d/S??xserver-nodm ];
> >> then
> >> if type psplash-write >/dev/null 2>&1; then
> >> -TMPDIR=/mnt/.psplash psplash-write "QUIT" || true
> >> +PSPLASH_FIFO_DIR=/mnt/.psplash psplash-write "QUIT" || true
> >> umount -l /mnt/.psplash
> >> fi
> >> fi
> >> --
> >> 2.28.0
> >>
> >>
> >>
> >>
> >>
> >>
>
>
> --
> # Randy MacLeod
> # Wind River Linux
>
>
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#142817):
https://lists.openembedded.org/g/openembedded-core/message/142817
Mute This Topic: https://lists.openembedded.org/mt/76488288/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core][dunfell][PATCH V2] sysvinit: Remove ${B} assignment
The VERSION variable is not set unless the
top level Makefile is used as the version is
derived from the Changelog.
If VERSION is not set, none of the binaries built
in the sysvinit recipe will have a valid version
output.
Before:
INIT: version booting
After:
INIT: version 2.96 booting
Using the top level Makefile does not cause any
additional builds to occur.
Signed-off-by: Michael Gloff
---
meta/recipes-core/sysvinit/sysvinit_2.96.bb | 1 -
1 file changed, 1 deletion(-)
diff --git a/meta/recipes-core/sysvinit/sysvinit_2.96.bb
b/meta/recipes-core/sysvinit/sysvinit_2.96.bb
index d2b85ed9c0..7358f02385 100644
--- a/meta/recipes-core/sysvinit/sysvinit_2.96.bb
+++ b/meta/recipes-core/sysvinit/sysvinit_2.96.bb
@@ -25,7 +25,6 @@ SRC_URI[md5sum] = "48cebffebf2a96ab09bec14bf9976016"
SRC_URI[sha256sum] =
"2a2e26b72aa235a23ab1c8471005f890309ce1196c83fbc9413c57b9ab62b587"
S = "${WORKDIR}/sysvinit-${PV}"
-B = "${S}/src"
inherit update-alternatives features_check
DEPENDS_append = " update-rc.d-native base-passwd virtual/crypt"
--
2.28.0
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#142468):
https://lists.openembedded.org/g/openembedded-core/message/142468
Mute This Topic: https://lists.openembedded.org/mt/76810616/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core][PATCH V2] sysvinit: Remove ${B} assignment
The VERSION variable is not set unless the
top level Makefile is used as the version is
derived from the Changelog.
If VERSION is not set, none of the binaries built
in the sysvinit recipe will have a valid version
output.
Before:
INIT: version booting
After:
INIT: version 2.96 booting
Using the top level Makefile does not cause any
additional builds to occur.
Signed-off-by: Michael Gloff
---
meta/recipes-core/sysvinit/sysvinit_2.97.bb | 1 -
1 file changed, 1 deletion(-)
diff --git a/meta/recipes-core/sysvinit/sysvinit_2.97.bb
b/meta/recipes-core/sysvinit/sysvinit_2.97.bb
index 80ab9d70e7..98916f7f19 100644
--- a/meta/recipes-core/sysvinit/sysvinit_2.97.bb
+++ b/meta/recipes-core/sysvinit/sysvinit_2.97.bb
@@ -24,7 +24,6 @@ SRC_URI =
"${SAVANNAH_GNU_MIRROR}/sysvinit/sysvinit-${PV}.tar.xz \
SRC_URI[sha256sum] =
"2d5996857519bfd8634d2e1debabb3238fb38440f65fbfdc46420ee8bdf25110"
S = "${WORKDIR}/sysvinit-${PV}"
-B = "${S}/src"
inherit update-alternatives features_check
DEPENDS_append = " update-rc.d-native base-passwd virtual/crypt"
--
2.28.0
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#142467):
https://lists.openembedded.org/g/openembedded-core/message/142467
Mute This Topic: https://lists.openembedded.org/mt/76810605/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core][PATCH] sysvinit: Remove ${B} assignment
On Sat, Sep 12, 2020 at 3:11 PM Andre McCurdy wrote:
> On Sat, Sep 12, 2020 at 12:46 PM Michael Gloff wrote:
> >
> > On Sat, Sep 12, 2020 at 2:11 PM Richard Purdie <
> richard.pur...@linuxfoundation.org> wrote:
> >>
> >> On Sat, 2020-09-12 at 11:48 -0500, Michael Gloff wrote:
> >> > In order for the VERSION variable to be set, the
> >> > top level Makefile should be used, which only
> >> > builds the code in /src anyway.
> >> >
> >> > Signed-off-by: Michael Gloff
> >> > ---
> >> > meta/recipes-core/sysvinit/sysvinit_2.97.bb | 1 -
> >> > 1 file changed, 1 deletion(-)
> >> >
> >> > diff --git a/meta/recipes-core/sysvinit/sysvinit_2.97.bb
> >> > b/meta/recipes-core/sysvinit/sysvinit_2.97.bb
> >> > index 80ab9d70e7..98916f7f19 100644
> >> > --- a/meta/recipes-core/sysvinit/sysvinit_2.97.bb
> >> > +++ b/meta/recipes-core/sysvinit/sysvinit_2.97.bb
> >> > @@ -24,7 +24,6 @@ SRC_URI =
> >> > "${SAVANNAH_GNU_MIRROR}/sysvinit/sysvinit-${PV}.tar.xz \
> >> > SRC_URI[sha256sum] =
> >> > "2d5996857519bfd8634d2e1debabb3238fb38440f65fbfdc46420ee8bdf25110"
> >> >
> >> > S = "${WORKDIR}/sysvinit-${PV}"
> >> > -B = "${S}/src"
> >> >
> >> > inherit update-alternatives features_check
> >> > DEPENDS_append = " update-rc.d-native base-passwd virtual/crypt"
> >>
> >> I don't understand what you're saying. Why do we need the VERSION
> >> variable to be set? Does sysvinit not support a separate build
> >> directory?
> >>
> >> Can you rewrite the commit message so that someone who hasn't looked at
> >> the code can understand what the problem is we're fixing, why its a
> >> problem and why this is the correct solution.
> >>
> >> Thanks!
> >>
> >> Richard
> >
> > This issue is seeing no version on boot up since the switch from 2.88:
> > INIT: version booting
> > instead of:
> > INIT: version 2.96 booting
> > with this change.
> >
> > The VERSION variable that is used for all of the binaries of sysvinit is
> defined in the top level Makefile.
> >
> > VERSION=$(shell sed -rn '1s/.*[[:blank:]]\((.*)\)[[:blank:]].*/\1/p'
> doc/Changelog)
> >
> > I'm not sure about the separate build directory. Any tips?
> > Thanks,
>
> A separate build directory typically only applies for components which
> build with autotools, cmake, etc. For components such as this one
> which build with handwritten Makefiles the default is to build in the
> source directory.
>
> Anyway, the patch looks fine. Key point is that you want to run make
> in the top level source directory rather than the "src" subdirectory
> to ensure that variables set by the top level Makefile are correctly
> defined.
>
> Thanks Andre,
I kind of thought we couldn't do a separate build directory, but wanted to
try.
I'll amend the commit message
> > Michael
> >
> >
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#142466):
https://lists.openembedded.org/g/openembedded-core/message/142466
Mute This Topic: https://lists.openembedded.org/mt/76804079/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core][PATCH] sysvinit: Remove ${B} assignment
On Sat, Sep 12, 2020 at 2:11 PM Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
> On Sat, 2020-09-12 at 11:48 -0500, Michael Gloff wrote:
> > In order for the VERSION variable to be set, the
> > top level Makefile should be used, which only
> > builds the code in /src anyway.
> >
> > Signed-off-by: Michael Gloff
> > ---
> > meta/recipes-core/sysvinit/sysvinit_2.97.bb | 1 -
> > 1 file changed, 1 deletion(-)
> >
> > diff --git a/meta/recipes-core/sysvinit/sysvinit_2.97.bb
> > b/meta/recipes-core/sysvinit/sysvinit_2.97.bb
> > index 80ab9d70e7..98916f7f19 100644
> > --- a/meta/recipes-core/sysvinit/sysvinit_2.97.bb
> > +++ b/meta/recipes-core/sysvinit/sysvinit_2.97.bb
> > @@ -24,7 +24,6 @@ SRC_URI =
> > "${SAVANNAH_GNU_MIRROR}/sysvinit/sysvinit-${PV}.tar.xz \
> > SRC_URI[sha256sum] =
> > "2d5996857519bfd8634d2e1debabb3238fb38440f65fbfdc46420ee8bdf25110"
> >
> > S = "${WORKDIR}/sysvinit-${PV}"
> > -B = "${S}/src"
> >
> > inherit update-alternatives features_check
> > DEPENDS_append = " update-rc.d-native base-passwd virtual/crypt"
>
> I don't understand what you're saying. Why do we need the VERSION
> variable to be set? Does sysvinit not support a separate build
> directory?
>
> Can you rewrite the commit message so that someone who hasn't looked at
> the code can understand what the problem is we're fixing, why its a
> problem and why this is the correct solution.
>
> Thanks!
>
> Richard
>
This issue is seeing no version on boot up since the switch from 2.88:
INIT: version booting
instead of:
INIT: version 2.96 booting
with this change.
The VERSION variable that is used for all of the binaries of sysvinit is
defined in the top level Makefile.
VERSION=$(shell sed -rn '1s/.*[[:blank:]]\((.*)\)[[:blank:]].*/\1/p'
doc/Changelog)
I'm not sure about the separate build directory. Any tips?
Thanks,
Michael
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#142460):
https://lists.openembedded.org/g/openembedded-core/message/142460
Mute This Topic: https://lists.openembedded.org/mt/76804079/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core][dunfell][PATCH] sysvinit: Remove ${B} assignment
In order for the VERSION variable to be set, the
top level Makefile should be used, which only
builds the code in /src anyway.
Signed-off-by: Michael Gloff
---
meta/recipes-core/sysvinit/sysvinit_2.96.bb | 1 -
1 file changed, 1 deletion(-)
diff --git a/meta/recipes-core/sysvinit/sysvinit_2.96.bb
b/meta/recipes-core/sysvinit/sysvinit_2.96.bb
index d2b85ed9c0..7358f02385 100644
--- a/meta/recipes-core/sysvinit/sysvinit_2.96.bb
+++ b/meta/recipes-core/sysvinit/sysvinit_2.96.bb
@@ -25,7 +25,6 @@ SRC_URI[md5sum] = "48cebffebf2a96ab09bec14bf9976016"
SRC_URI[sha256sum] =
"2a2e26b72aa235a23ab1c8471005f890309ce1196c83fbc9413c57b9ab62b587"
S = "${WORKDIR}/sysvinit-${PV}"
-B = "${S}/src"
inherit update-alternatives features_check
DEPENDS_append = " update-rc.d-native base-passwd virtual/crypt"
--
2.28.0
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#142456):
https://lists.openembedded.org/g/openembedded-core/message/142456
Mute This Topic: https://lists.openembedded.org/mt/76804142/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core][PATCH] sysvinit: Remove ${B} assignment
In order for the VERSION variable to be set, the
top level Makefile should be used, which only
builds the code in /src anyway.
Signed-off-by: Michael Gloff
---
meta/recipes-core/sysvinit/sysvinit_2.97.bb | 1 -
1 file changed, 1 deletion(-)
diff --git a/meta/recipes-core/sysvinit/sysvinit_2.97.bb
b/meta/recipes-core/sysvinit/sysvinit_2.97.bb
index 80ab9d70e7..98916f7f19 100644
--- a/meta/recipes-core/sysvinit/sysvinit_2.97.bb
+++ b/meta/recipes-core/sysvinit/sysvinit_2.97.bb
@@ -24,7 +24,6 @@ SRC_URI =
"${SAVANNAH_GNU_MIRROR}/sysvinit/sysvinit-${PV}.tar.xz \
SRC_URI[sha256sum] =
"2d5996857519bfd8634d2e1debabb3238fb38440f65fbfdc46420ee8bdf25110"
S = "${WORKDIR}/sysvinit-${PV}"
-B = "${S}/src"
inherit update-alternatives features_check
DEPENDS_append = " update-rc.d-native base-passwd virtual/crypt"
--
2.28.0
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#142455):
https://lists.openembedded.org/g/openembedded-core/message/142455
Mute This Topic: https://lists.openembedded.org/mt/76804079/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
[OE-core][PATCH] sysvinit rc: Use PSPLASH_FIFO_DIR for progress fifo
psplash expects the fifo to be in /run or specified
by PSPLASH_FIFO_DIR. This patch allows psplash to
quit normally. Also, fix the work around of using
echo directly into the fifo and use psplash-write.
Signed-off-by: Michael Gloff
---
meta/recipes-core/sysvinit/sysvinit/rc | 9 +++--
1 file changed, 3 insertions(+), 6 deletions(-)
diff --git a/meta/recipes-core/sysvinit/sysvinit/rc
b/meta/recipes-core/sysvinit/sysvinit/rc
index 7ca41ae1ae..fd1fdd26ba 100755
--- a/meta/recipes-core/sysvinit/sysvinit/rc
+++ b/meta/recipes-core/sysvinit/sysvinit/rc
@@ -26,11 +26,8 @@ startup_progress() {
progress=$progress_size
fi
#echo "PROGRESS is $progress $runlevel $first_step + ($step of $num_steps)
$step_change $progress_size"
-#if type psplash-write >/dev/null 2>&1; then
-#TMPDIR=/mnt/.psplash psplash-write "PROGRESS $progress" || true
-#fi
-if [ -e /mnt/.psplash/psplash_fifo ]; then
-echo "PROGRESS $progress" > /mnt/.psplash/psplash_fifo
+if type psplash-write >/dev/null 2>&1; then
+PSPLASH_FIFO_DIR=/mnt/.psplash psplash-write "PROGRESS $progress" ||
true
fi
}
@@ -176,7 +173,7 @@ startup() {
#Uncomment to cause psplash to exit manually, otherwise it exits when it sees
a VC switch
if [ "x$runlevel" != "xS" ] && [ ! -x /etc/rc${runlevel}.d/S??xserver-nodm ];
then
if type psplash-write >/dev/null 2>&1; then
-TMPDIR=/mnt/.psplash psplash-write "QUIT" || true
+PSPLASH_FIFO_DIR=/mnt/.psplash psplash-write "QUIT" || true
umount -l /mnt/.psplash
fi
fi
--
2.28.0
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#141942):
https://lists.openembedded.org/g/openembedded-core/message/141942
Mute This Topic: https://lists.openembedded.org/mt/76488288/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] Sumo webkitgtk fails to compile
I'm not sure either why I am seeing this and thought that this would have been also seen on the autobuilder. Is there some configuration on the AB that does not trigger the clash? Can anyone else validate the clash with a fresh checkout of Sumo? Michael On Thu, Jun 28, 2018 at 6:14 AM, Alexander Kanavin wrote: > TBH, I'm not sure why Michael is seeing this failure either. Sumo does > get built on the AB against several qemu targets, and the failure does > not happen there. > > Alex > > 2018-06-28 4:28 GMT+02:00 Carlos Alberto Lopez Perez : > > On 27/06/18 19:27, Michael Gloff wrote: > >> # GL/GLES header clash: both define the same thing, differently, on 32 > bit > >> x86 > >> EXTRA_OECMAKE_append_x86 = " -DUSE_GSTREAMER_GL=OFF " > >> EXTRA_OECMAKE_append_x86-x32 = " -DUSE_GSTREAMER_GL=OFF " > >> > >> I think the best thing to do it to turn off USE_GSTREAMER_GL for all > >> architectures. Would a patch doing so be acceptable? I've verified that > it > >> will build with the _armv5 case. > > > > USE_GSTREAMER_GL is a feature of WebKitGTK+ that allows it to leverage > > hardware-accelerated video decoding (for example: on i.MX6). > > > > I think is acceptable to disable this for ARMv5 (because, AFAIK, there > > isn't any ARMv5 hardware that can leverage this in any case), but this > > should remain enabled for other architectures. > > > > > -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] Sumo webkitgtk fails to compile
Alex, Thanks. I looked into the patch [1], but it does not apply to gstreamer 1.12.x. After refreshing the patch, gstreamer1.0-plugins-bad does not build because of the move of some header files to plugins-base in 1.13. I noticed in the recipe: # GL/GLES header clash: both define the same thing, differently, on 32 bit x86 EXTRA_OECMAKE_append_x86 = " -DUSE_GSTREAMER_GL=OFF " EXTRA_OECMAKE_append_x86-x32 = " -DUSE_GSTREAMER_GL=OFF " I think the best thing to do it to turn off USE_GSTREAMER_GL for all architectures. Would a patch doing so be acceptable? I've verified that it will build with the _armv5 case. Thanks, Michael Gloff [1] https://bug784779.bugzilla-attachments.gnome.org/attachment.cgi?id=357732 On Tue, Jun 26, 2018 at 2:24 PM, Alexander Kanavin wrote: > The bug refers to a gstreamer bug with patches, which you should probably > apply: > https://bugzilla.gnome.org/show_bug.cgi?id=784779 > > Alex > > 2018-06-26 20:55 GMT+02:00 Michael Gloff : > > I'm seeing the below errors when trying to build webkitgtk. I am using > base > > poky distro on sumo branch without any extra layers with qemuarm > machine. It > > looks similar to: > > https://bugs.webkit.org/show_bug.cgi?id=175127 > > which reports that this was fixed upstream, but obviously not in 2.18.6. > > Does anyone know what the proper fix for this is or at least a work > around? > > Thanks, > > > > Michael Gloff > > > > In file included from > > /home/mgloff/poky/build/tmp/work/armv5e-poky-linux- > gnueabi/webkitgtk/2.18.6-r0/recipe-sysroot/usr/include/GL/gl.h:2055:0, > > from > > /home/mgloff/poky/build/tmp/work/armv5e-poky-linux- > gnueabi/webkitgtk/2.18.6-r0/webkitgtk-2.18.6/Source/ > WebCore/platform/graphics/OpenGLShims.h:23, > > from > > /home/mgloff/poky/build/tmp/work/armv5e-poky-linux- > gnueabi/webkitgtk/2.18.6-r0/webkitgtk-2.18.6/Source/ > WebCore/platform/graphics/ANGLEWebKitBridge.h:50, > > from > > /home/mgloff/poky/build/tmp/work/armv5e-poky-linux- > gnueabi/webkitgtk/2.18.6-r0/webkitgtk-2.18.6/Source/ > WebCore/platform/graphics/GraphicsContext3D.h:28, > > from > > /home/mgloff/poky/build/tmp/work/armv5e-poky-linux- > gnueabi/webkitgtk/2.18.6-r0/webkitgtk-2.18.6/Source/ > WebCore/platform/graphics/GLContext.h:23, > > from > > /home/mgloff/poky/build/tmp/work/armv5e-poky-linux- > gnueabi/webkitgtk/2.18.6-r0/webkitgtk-2.18.6/Source/ > WebCore/platform/graphics/gstreamer/MediaPlayerPrivateGStreamerBas > e.cpp:72: > > /home/mgloff/poky/build/tmp/work/armv5e-poky-linux- > gnueabi/webkitgtk/2.18.6-r0/recipe-sysroot/usr/include/GL/glext.h: > > At global scope: > > /home/mgloff/poky/build/tmp/work/armv5e-poky-linux- > gnueabi/webkitgtk/2.18.6-r0/recipe-sysroot/usr/include/GL/glext.h:468:19: > > error: conflicting declaration 'typedef ptrdiff_t GLsizeiptr' > > typedef ptrdiff_t GLsizeiptr; > >^~ > > In file included from > > /home/mgloff/poky/build/tmp/work/armv5e-poky-linux- > gnueabi/webkitgtk/2.18.6-r0/recipe-sysroot/usr/include/ > gstreamer-1.0/gst/gl/gstglapi.h:40:0, > > from > > /home/mgloff/poky/build/tmp/work/armv5e-poky-linux- > gnueabi/webkitgtk/2.18.6-r0/recipe-sysroot/usr/include/ > gstreamer-1.0/gst/gl/gstgl_fwd.h:26, > > from > > /home/mgloff/poky/build/tmp/work/armv5e-poky-linux- > gnueabi/webkitgtk/2.18.6-r0/recipe-sysroot/usr/include/ > gstreamer-1.0/gst/gl/gl.h:29, > > from > > /home/mgloff/poky/build/tmp/work/armv5e-poky-linux- > gnueabi/webkitgtk/2.18.6-r0/webkitgtk-2.18.6/Source/ > WebCore/platform/graphics/gstreamer/MediaPlayerPrivateGStreamerBas > e.cpp:69: > > /home/mgloff/poky/build/tmp/work/armv5e-poky-linux- > gnueabi/webkitgtk/2.18.6-r0/recipe-sysroot/usr/include/GLES3/gl3.h:75:25: > > note: previous declaration as 'typedef khronos_ssize_t GLsizeiptr' > > typedef khronos_ssize_t GLsizeiptr; > > ^~ > > In file included from > > /home/mgloff/poky/build/tmp/work/armv5e-poky-linux- > gnueabi/webkitgtk/2.18.6-r0/recipe-sysroot/usr/include/GL/gl.h:2055:0, > > from > > /home/mgloff/poky/build/tmp/work/armv5e-poky-linux- > gnueabi/webkitgtk/2.18.6-r0/webkitgtk-2.18.6/Source/ > WebCore/platform/graphics/OpenGLShims.h:23, > > from > > /home/mgloff/poky/build/tmp/work/armv5e-poky-linux- > gnueabi/webkitgtk/2.18.6-r0/webkitgtk-2.18.6/Source/ > WebCore/platform/graphics/ANGLEWebKitBridge.h:50, > > from > > /home/mgloff/poky/build/tmp/work/armv5e-pok
[OE-core] Sumo webkitgtk fails to compile
I'm seeing the below errors when trying to build webkitgtk. I am using base poky distro on sumo branch without any extra layers with qemuarm machine. It looks similar to: https://bugs.webkit.org/show_bug.cgi?id=175127 which reports that this was fixed upstream, but obviously not in 2.18.6. Does anyone know what the proper fix for this is or at least a work around? Thanks, Michael Gloff In file included from /home/mgloff/poky/build/tmp/work/armv5e-poky-linux-gnueabi/webkitgtk/2.18.6-r0/recipe-sysroot/usr/include/GL/gl.h:2055:0, from /home/mgloff/poky/build/tmp/work/armv5e-poky-linux-gnueabi/webkitgtk/2.18.6-r0/webkitgtk-2.18.6/Source/WebCore/platform/graphics/OpenGLShims.h:23, from /home/mgloff/poky/build/tmp/work/armv5e-poky-linux-gnueabi/webkitgtk/2.18.6-r0/webkitgtk-2.18.6/Source/WebCore/platform/graphics/ANGLEWebKitBridge.h:50, from /home/mgloff/poky/build/tmp/work/armv5e-poky-linux-gnueabi/webkitgtk/2.18.6-r0/webkitgtk-2.18.6/Source/WebCore/platform/graphics/GraphicsContext3D.h:28, from /home/mgloff/poky/build/tmp/work/armv5e-poky-linux-gnueabi/webkitgtk/2.18.6-r0/webkitgtk-2.18.6/Source/WebCore/platform/graphics/GLContext.h:23, from /home/mgloff/poky/build/tmp/work/armv5e-poky-linux-gnueabi/webkitgtk/2.18.6-r0/webkitgtk-2.18.6/Source/WebCore/platform/graphics/gstreamer/MediaPlayerPrivateGStreamerBase.cpp:72: /home/mgloff/poky/build/tmp/work/armv5e-poky-linux-gnueabi/webkitgtk/2.18.6-r0/recipe-sysroot/usr/include/GL/glext.h: At global scope: /home/mgloff/poky/build/tmp/work/armv5e-poky-linux-gnueabi/webkitgtk/2.18.6-r0/recipe-sysroot/usr/include/GL/glext.h:468:19: error: conflicting declaration 'typedef ptrdiff_t GLsizeiptr' typedef ptrdiff_t GLsizeiptr; ^~ In file included from /home/mgloff/poky/build/tmp/work/armv5e-poky-linux-gnueabi/webkitgtk/2.18.6-r0/recipe-sysroot/usr/include/gstreamer-1.0/gst/gl/gstglapi.h:40:0, from /home/mgloff/poky/build/tmp/work/armv5e-poky-linux-gnueabi/webkitgtk/2.18.6-r0/recipe-sysroot/usr/include/gstreamer-1.0/gst/gl/gstgl_fwd.h:26, from /home/mgloff/poky/build/tmp/work/armv5e-poky-linux-gnueabi/webkitgtk/2.18.6-r0/recipe-sysroot/usr/include/gstreamer-1.0/gst/gl/gl.h:29, from /home/mgloff/poky/build/tmp/work/armv5e-poky-linux-gnueabi/webkitgtk/2.18.6-r0/webkitgtk-2.18.6/Source/WebCore/platform/graphics/gstreamer/MediaPlayerPrivateGStreamerBase.cpp:69: /home/mgloff/poky/build/tmp/work/armv5e-poky-linux-gnueabi/webkitgtk/2.18.6-r0/recipe-sysroot/usr/include/GLES3/gl3.h:75:25: note: previous declaration as 'typedef khronos_ssize_t GLsizeiptr' typedef khronos_ssize_t GLsizeiptr; ^~ In file included from /home/mgloff/poky/build/tmp/work/armv5e-poky-linux-gnueabi/webkitgtk/2.18.6-r0/recipe-sysroot/usr/include/GL/gl.h:2055:0, from /home/mgloff/poky/build/tmp/work/armv5e-poky-linux-gnueabi/webkitgtk/2.18.6-r0/webkitgtk-2.18.6/Source/WebCore/platform/graphics/OpenGLShims.h:23, from /home/mgloff/poky/build/tmp/work/armv5e-poky-linux-gnueabi/webkitgtk/2.18.6-r0/webkitgtk-2.18.6/Source/WebCore/platform/graphics/ANGLEWebKitBridge.h:50, from /home/mgloff/poky/build/tmp/work/armv5e-poky-linux-gnueabi/webkitgtk/2.18.6-r0/webkitgtk-2.18.6/Source/WebCore/platform/graphics/GraphicsContext3D.h:28, from /home/mgloff/poky/build/tmp/work/armv5e-poky-linux-gnueabi/webkitgtk/2.18.6-r0/webkitgtk-2.18.6/Source/WebCore/platform/graphics/GLContext.h:23, from /home/mgloff/poky/build/tmp/work/armv5e-poky-linux-gnueabi/webkitgtk/2.18.6-r0/webkitgtk-2.18.6/Source/WebCore/platform/graphics/gstreamer/MediaPlayerPrivateGStreamerBase.cpp:72: /home/mgloff/poky/build/tmp/work/armv5e-poky-linux-gnueabi/webkitgtk/2.18.6-r0/recipe-sysroot/usr/include/GL/glext.h:469:19: error: conflicting declaration 'typedef ptrdiff_t GLintptr' typedef ptrdiff_t GLintptr; ^~~~ In file included from /home/mgloff/poky/build/tmp/work/armv5e-poky-linux-gnueabi/webkitgtk/2.18.6-r0/recipe-sysroot/usr/include/gstreamer-1.0/gst/gl/gstglapi.h:40:0, from /home/mgloff/poky/build/tmp/work/armv5e-poky-linux-gnueabi/webkitgtk/2.18.6-r0/recipe-sysroot/usr/include/gstreamer-1.0/gst/gl/gstgl_fwd.h:26, from /home/mgloff/poky/build/tmp/work/armv5e-poky-linux-gnueabi/webkitgtk/2.18.6-r0/recipe-sysroot/usr/include/gstreamer-1.0/gst/gl/gl.h:29, from /home/mgloff/poky/build/tmp/work/armv5e-poky-linux-gnueabi/webkitgtk/2.18.6-r0/webkitgtk-2.18.6/Source/WebCore/platform/graphics/gstreamer/MediaPlayerPrivateGStreamerBase.cpp:69: /home/mgloff/poky/build/tmp/work/armv5e-poky-linux-gnueabi/webkitgtk/2.18.6-r0/recipe-sysroot/usr/include/GLES3/gl3.h:76:26: note: previous declaration as 'typedef khronos_intptr_t GLintptr' typedef khronos_intptr_t GLintptr
[OE-core] Busybox post install
I am seeing with the latest in Sumo/Master that the busybox post install is failing to create all of the applet symlinks if there is already a package installed from another provider during do_rootfs. This can be seen, for example, when enabling lsattr applet and having e2fsprogs installed into an image. The error is: update-alternatives: Error: not linking /home/developer/oe-test/build_ master/tmp/work/somimx6-emac-linux-gnueabi/emac-image/1.0-r0/rootfs/usr/bin/lsattr to /usr/bin/busybox.nosuid since /home/developer/oe-test/build_ master/tmp/work/somimx6-emac-linux-gnueabi/emac-image/1.0-r0/rootfs/usr/bin/lsattr exists and is not a link In Rocko and before, this error is present, but the script continues creating the rest of the symlinks and exits with success. Does anyone have any idea why the failure is now causing the script to stop executing? Michael Gloff mgl...@emacinc.com -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] Sumo/Master Busybox post install
I am seeing with the latest in Sumo/Master that the busybox post install with ipk packages is failing to create all of the applet symlinks if there is already a package installed from another provider. This can be seen, for example, when enabling lsattr applet and having e2fsprogs installed into an image. The error is: update-alternatives: Error: not linking /home/developer/oe-test/build_master/tmp/work/somimx6-emac-linux-gnueabi/emac-image/1.0-r0/rootfs/usr/bin/lsattr to /usr/bin/busybox.nosuid since /home/developer/oe-test/build_master/tmp/work/somimx6-emac-linux-gnueabi/emac-image/1.0-r0/rootfs/usr/bin/lsattr exists and is not a link In Rocko and before, this error is present, but the script continues creating the rest of the symlinks and exits with success. Does anyone have any idea why the failure is now causing the script to stop executing? Michael Gloff mgl...@emacinc.com -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH] utils.py: Use minimum value for PARALLEL_MAKE.
feded5fe2755fc6523c235fd6e82a0972e197c08 introduces parallel_make_argument with optional limit value. We need the min of PARRALLEL_MAKE and limit. Signed-off-by: Michael Gloff <mgl...@emacinc.com> --- meta/lib/oe/utils.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/lib/oe/utils.py b/meta/lib/oe/utils.py index ec91927233..80f0442d0a 100644 --- a/meta/lib/oe/utils.py +++ b/meta/lib/oe/utils.py @@ -195,7 +195,7 @@ def parallel_make_argument(d, fmt, limit=None): v = parallel_make(d) if v: if limit: -v = max(limit, v) +v = min(limit, v) return fmt % v return '' -- 2.16.2 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] Debugfs + nfs-utils-client + ipkg
Thanks Robert! Bug filed: https://bugzilla.yoctoproject.org/show_bug.cgi?id=10761 Michael On Fri, Dec 2, 2016 at 1:17 AM, Robert Yang <liezhi.y...@windriver.com> wrote: > Hi Michael, > > On 12/02/2016 11:19 AM, Michael Gloff wrote: > >> I've run into an issue recently when trying to build an image along with >> the >> companion debugfs. This error only occurs if 'nfs-utils-client' is added >> to >> IMAGE_INSTALL and ipkg packages are selected. I don't get the error with >> RPM or >> with removing nfs-utils-client. Also, I can see the missing files are >> present at >> some point during do_rootfs, but then must be getting wiped out? I >> noticed this >> in Krogoth first, but can reproduce in latest master. Any ideas? >> > > Maybe something is wrong with opkg, it only happens when files are in > /var/lib/foo, here is a *workaround*: > > diff --git a/meta/lib/oe/rootfs.py b/meta/lib/oe/rootfs.py > index a348b97..ba072c0 100644 > --- a/meta/lib/oe/rootfs.py > +++ b/meta/lib/oe/rootfs.py > @@ -951,7 +951,7 @@ class OpkgRootfs(DpkgOpkgRootfs): > if self.progress_reporter: > self.progress_reporter.next_stage() > > -self._setup_dbg_rootfs(['/etc', '/var/lib/opkg', '/usr/lib/ssl']) > +self._setup_dbg_rootfs(['/etc', '/var/lib/opkg', '/usr/lib/ssl', > '/var/lib/nfs']) > > execute_pre_post_process(self.d, opkg_post_process_cmds) > > > This is not a regular fix, you can file a bug here: > https://bugzilla.yoctoproject.org/ > > We may fix it later. > > // Robert > > >> developer@OEBuilder:~/oe/recipes/poky/build$ bitbake core-image-minimal >> Loading cache: 100% >> |### >> >> ###| >> Time: 0:00:00 >> Loaded 1304 entries from dependency cache. >> NOTE: Resolving any missing task queue dependencies >> >> Build Configuration: >> BB_VERSION= "1.32.0" >> BUILD_SYS = "x86_64-linux" >> NATIVELSBSTRING = "universal" >> TARGET_SYS= "i586-poky-linux" >> MACHINE = "qemux86" >> DISTRO= "poky" >> DISTRO_VERSION= "2.2" >> TUNE_FEATURES = "m32 i586" >> TARGET_FPU= "" >> meta >> meta-poky >> meta-yocto-bsp= "master:9e63f81c78e284c9b325fe04a1b59e61c7ad8a1a" >> >> Initialising tasks: 100% >> |### >> >> ##| >> Time: 0:00:03 >> NOTE: Executing SetScene Tasks >> NOTE: Executing RunQueue Tasks >> ERROR: core-image-minimal-1.0-r0 do_rootfs: Cannot get the installed >> packages >> list. Command >> '/home/developer/oe/recipes/poky/build/tmp/sysroots/x86_64-linux/usr/bin/opkg >> -f >> /home/developer/oe/recipes/poky/build/tmp/work/qemux86-poky- >> linux/core-image-minimal/1.0-r0/opkg.conf >> -o >> /home/developer/oe/recipes/poky/build/tmp/work/qemux86-poky- >> linux/core-image-minimal/1.0-r0/rootfs >> --force_postinstall --prefer-arch-to-version status' returned 0 and >> stderr: >> Collected errors: >> * file_md5sum_alloc: Failed to open file >> /home/developer/oe/recipes/poky/build/tmp/work/qemux86-poky- >> linux/core-image-minimal/1.0-r0/rootfs/var/lib/nfs/etab: >> No such file or directory. >> * file_md5sum_alloc: Failed to open file >> /home/developer/oe/recipes/poky/build/tmp/work/qemux86-poky- >> linux/core-image-minimal/1.0-r0/rootfs/var/lib/nfs/rmtab: >> No such file or directory. >> * file_md5sum_alloc: Failed to open file >> /home/developer/oe/recipes/poky/build/tmp/work/qemux86-poky- >> linux/core-image-minimal/1.0-r0/rootfs/var/lib/nfs/xtab: >> No such file or directory. >> * file_md5sum_alloc: Failed to open file >> /home/developer/oe/recipes/poky/build/tmp/work/qemux86-poky- >> linux/core-image-minimal/1.0-r0/rootfs/var/lib/nfs/statd/state: >> No such file or directory. >> >> ERROR: core-image-minimal-1.0-r0 do_rootfs: Function failed: do_rootfs >> ERROR: Logfile of failure stored in: >> /home/developer/oe/recipes/poky/build/tmp/work/qemux86-poky- >> linux/core-image-minimal/1.0-r0/temp/log.do_rootfs.5361 >> ERROR: Task >> (/home/developer/oe/recipes/poky/meta/recipes-core/images/co >> re-image-minimal.bb:do_rootfs) >> failed with exit code '1' >> NOTE: Tasks Summary: Attempted 2168 tasks of which 2167 didn't need to be >> rerun >> and 1 failed. >> >> Summary: 1 task failed: >> >> /home/developer/oe/recipes/poky/meta/recipes-core/images/cor >> e-image-minimal.bb:do_rootfs >> Summary: There were 2 ERROR messages shown, returning a non-zero exit >> code. >> >> Thanks, >> >> Michael Gloff >> mgl...@emacinc.com <mailto:mgl...@emacinc.com> >> >> >> -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] Debugfs + nfs-utils-client + ipkg
I've run into an issue recently when trying to build an image along with the companion debugfs. This error only occurs if 'nfs-utils-client' is added to IMAGE_INSTALL and ipkg packages are selected. I don't get the error with RPM or with removing nfs-utils-client. Also, I can see the missing files are present at some point during do_rootfs, but then must be getting wiped out? I noticed this in Krogoth first, but can reproduce in latest master. Any ideas? developer@OEBuilder:~/oe/recipes/poky/build$ bitbake core-image-minimal Loading cache: 100% |##| Time: 0:00:00 Loaded 1304 entries from dependency cache. NOTE: Resolving any missing task queue dependencies Build Configuration: BB_VERSION= "1.32.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "universal" TARGET_SYS= "i586-poky-linux" MACHINE = "qemux86" DISTRO= "poky" DISTRO_VERSION= "2.2" TUNE_FEATURES = "m32 i586" TARGET_FPU= "" meta meta-poky meta-yocto-bsp= "master:9e63f81c78e284c9b325fe04a1b59e61c7ad8a1a" Initialising tasks: 100% |#| Time: 0:00:03 NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks ERROR: core-image-minimal-1.0-r0 do_rootfs: Cannot get the installed packages list. Command '/home/developer/oe/recipes/poky/build/tmp/sysroots/x86_64-linux/usr/bin/opkg -f /home/developer/oe/recipes/poky/build/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/opkg.conf -o /home/developer/oe/recipes/poky/build/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/rootfs --force_postinstall --prefer-arch-to-version status' returned 0 and stderr: Collected errors: * file_md5sum_alloc: Failed to open file /home/developer/oe/recipes/poky/build/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/rootfs/var/lib/nfs/etab: No such file or directory. * file_md5sum_alloc: Failed to open file /home/developer/oe/recipes/poky/build/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/rootfs/var/lib/nfs/rmtab: No such file or directory. * file_md5sum_alloc: Failed to open file /home/developer/oe/recipes/poky/build/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/rootfs/var/lib/nfs/xtab: No such file or directory. * file_md5sum_alloc: Failed to open file /home/developer/oe/recipes/poky/build/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/rootfs/var/lib/nfs/statd/state: No such file or directory. ERROR: core-image-minimal-1.0-r0 do_rootfs: Function failed: do_rootfs ERROR: Logfile of failure stored in: /home/developer/oe/recipes/poky/build/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/temp/log.do_rootfs.5361 ERROR: Task (/home/developer/oe/recipes/poky/meta/recipes-core/images/core-image-minimal.bb:do_rootfs) failed with exit code '1' NOTE: Tasks Summary: Attempted 2168 tasks of which 2167 didn't need to be rerun and 1 failed. Summary: 1 task failed: /home/developer/oe/recipes/poky/meta/recipes-core/images/core-image-minimal.bb: do_rootfs Summary: There were 2 ERROR messages shown, returning a non-zero exit code. Thanks, Michael Gloff mgl...@emacinc.com -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH] sanity.bbclass: Add syntax check on MACHINE variable
Why? Uppercase letters should be allowed and work fine for the most part.
Below are a few excerpts from last year:
On Wed, Mar 5, 2014 at 11:45 AM, Paul Eggleton
paul.eggle...@linux.intel.com wrote:
On Wednesday 05 March 2014 11:00:31 Michael Gloff wrote:
On Mon, Mar 3, 2014 at 12:52 PM, Paul Eggleton
paul.eggle...@linux.intel.com
wrote:
On Sunday 02 March 2014 19:58:41 Michael Gloff wrote:
Is there a reason why the toolchain cannot be built with a machine
name
that contains capital letters? Seems weird, everything else builds
fine,
but meta-toolchain fails complaining about caps.
Although machine names are traditionally all lower case in our build
system, there's no deliberate restriction in place that enforces this.
Would you be able to provide more details, such as the version of the
build system you are using, the exact capital letters you used in the
machine name, and the error you received?
The error is below. Machine name: PMX-090T. This is on dora 1.5.1
ERROR: Function failed: opkg-build execution failed
ERROR: Logfile of failure stored in:
/opt/oe/build/tmp/work/i686-nativesdk-emacsdk-linux/meta-environment-PMX-090
T/1.0-r8/temp/log.do_package_write_ipk.15358
Log data follows:
| DEBUG: Executing python function sstate_task_prefunc
| DEBUG: Python function sstate_task_prefunc finished
| DEBUG: Executing python function do_package_write_ipk
| DEBUG: Executing python function read_subpackage_metadata
| DEBUG: Python function read_subpackage_metadata finished
| DEBUG: Executing python function do_package_ipk
| meta-environment-PMX-090T
| *** Error: Package name contains illegal characters, (other than
[a-z0-9.+-])
Perhaps I spoke too soon. There might not be a direct restriction on
machine
names; but opkg does restrict characters allowed in package names, and for
meta-environment the machine name ends up as part of the package name. You
could probably hack around it if you felt the need to, but the simplest
thing
would be to just change the machine name to be all lower-case.
Cheers,
Paul
=
Paul Barker p...@paulbarker.me.uk
3/6/14
to Khem, me, Paul, Yocto
On 5 March 2014 21:14, Khem Raj raj.k...@gmail.com wrote:
On Wed, Mar 5, 2014 at 9:00 AM, Michael Gloff mgl...@emacinc.com wrote:
| *** Error: Package name contains illegal characters, (other than
[a-z0-9.+-])
hmm meta-environment-PMX-090T is a package name and
thats limitation of opkg backend, if you are too tied to
opkg itself doesn't seem to have this limitation, I just created and
installed a
test package named 'A' perfectly fine.
The Debian policy says:
Package names (both source and binary, see Package, Section 5.6.7) must
consist only of lower case letters (a-z), digits (0-9), plus (+) and
minus
(-) signs, and periods (.). They must be at least two characters long
and
must start with an alphanumeric character.
So I think the restriction is there to keep generated packages
compatible with dpkg-deb.
We could consider removing the restriction if that compatibility isn't
necessary.
===
I think we should fix the SDK generation that has a problem with caps
instead of dis-allowing it completely.
Michael Gloff
On Tue, Mar 3, 2015 at 5:01 AM, Baptiste DURAND baptiste.dur...@gmail.com
wrote:
MACHINE variable should not contain uppercase characters.
Having uppercase in Machine name can lead to this kind of error : (here
Machine is set to nuc-E3815)
ERROR: initramfs-live-boot not found in the base feeds (nuc_E3815
corei7-64-intel-common corei7-64 core2-64 x86_64 noarch any all).
Signed-off-by: Baptiste DURAND baptiste.dur...@gmail.com
---
meta/classes/sanity.bbclass | 15 ++-
1 file changed, 10 insertions(+), 5 deletions(-)
diff --git a/meta/classes/sanity.bbclass b/meta/classes/sanity.bbclass
index 31b99d4..1fa2e58 100644
--- a/meta/classes/sanity.bbclass
+++ b/meta/classes/sanity.bbclass
@@ -713,12 +713,17 @@ def check_sanity_everybuild(status, d):
# Check that the MACHINE is valid, if it is set
machinevalid = True
-if d.getVar('MACHINE', True):
-if not check_conf_exists(conf/machine/${MACHINE}.conf, d):
-status.addresult('Please set a valid MACHINE in your
local.conf or environment\n')
-machinevalid = False
+machinevar = d.getVar('MACHINE', True)
+if machinevar:
+if machinevar == machinevar.lower():
+if not check_conf_exists(conf/machine/${MACHINE}.conf, d):
+ status.addresult('Please set a valid MACHINE in your
local.conf or environment\n')
+ machinevalid = False
+else:
+ status.addresult(check_sanity_validmachine(d))
else:
-status.addresult(check_sanity_validmachine(d
[OE-core] [PATCH V3 1/2] volatiles: Link /media appropriately
Since the change of /etc/udev/scripts/mount.sh to use tmpfs, link /media to it Signed-off-by: Michael Gloff mgl...@emacinc.com --- .../initscripts/initscripts-1.0/volatiles |2 ++ 1 file changed, 2 insertions(+) diff --git a/meta/recipes-core/initscripts/initscripts-1.0/volatiles b/meta/recipes-core/initscripts/initscripts-1.0/volatiles index 297245d..1fc5816 100644 --- a/meta/recipes-core/initscripts/initscripts-1.0/volatiles +++ b/meta/recipes-core/initscripts/initscripts-1.0/volatiles @@ -34,3 +34,5 @@ f root root 0664 /var/log/wtmp none f root root 0664 /var/run/utmp none l root root 0644 /etc/resolv.conf /var/run/resolv.conf f root root 0644 /var/run/resolv.conf none +d root root 1777 /run/media none +l root root 1777 /media /run/media -- 1.7.9.5 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH V3 2/2] volatiles: Change linking ordering of resolv.conf
Fixes error on boot on readonly rootfs rm: can't remove '/etc/resolv.conf': Read-only file system ln: /etc/resolv.conf: File exists Signed-off-by: Michael Gloff mgl...@emacinc.com --- .../initscripts/initscripts-1.0/volatiles |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-core/initscripts/initscripts-1.0/volatiles b/meta/recipes-core/initscripts/initscripts-1.0/volatiles index 1fc5816..e6f0695 100644 --- a/meta/recipes-core/initscripts/initscripts-1.0/volatiles +++ b/meta/recipes-core/initscripts/initscripts-1.0/volatiles @@ -32,7 +32,7 @@ l root root 1777 /tmp /var/tmp d root root 0755 /var/lock/subsys none f root root 0664 /var/log/wtmp none f root root 0664 /var/run/utmp none -l root root 0644 /etc/resolv.conf /var/run/resolv.conf f root root 0644 /var/run/resolv.conf none +l root root 0644 /etc/resolv.conf /var/run/resolv.conf d root root 1777 /run/media none l root root 1777 /media /run/media -- 1.7.9.5 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] NFS server
All,
I have run into the issue of nfs server seg faulting when trying to start.
After some searching I found that it is related to GCC 4.9.x and
nfs-utils-1.3.X
http://lists.linuxfromscratch.org/pipermail/blfs-dev/2014-July/027853.html
There is a patch that I have tested locally that works.
I'm not sure how to proceed, but this pretty much breaks nfs server
capabilities.
Michael Gloff
From 25e83c2270b2d2966c992885faed0b79be09f474 Mon Sep 17 00:00:00 2001
From: Jeff Layton jlay...@poochiereds.net
Date: Thu, 1 May 2014 11:15:16 -0400
Subject: [PATCH [nfs-utils]] mountd: fix segfault in add_name with newer gcc
compilers
I hit a segfault in add_name with a mountd built with gcc-4.9.0. Some
NULL pointer checks got reordered such that a pointer was dereferenced
before checking to see whether it was NULL. The problem was due to
nfs-utils relying on undefined behavior, which tricked gcc into assuming
that the pointer would never be NULL.
At first I assumed that this was a compiler bug, but Jakub Jelinek and
Jeff Law pointed out:
If old is NULL, then:
strncpy(new, old, cp-old);
is undefined behavior (even when cp == old == NULL in that case),
therefore gcc assumes that old is never NULL, as otherwise it would be
invalid.
Just guard
strncpy(new, old, cp-old);
new[cp-old] = 0;
with if (old) { ... }.
This patch does that. If old is NULL though, then we still need to
ensure that new is NULL terminated, lest the subsequent strcats walk off
the end of it.
Cc: Jeff Law l...@redhat.com
Cc: Jakub Jelinek ja...@redhat.com
Signed-off-by: Jeff Layton jlay...@poochiereds.net
Signed-off-by: Steve Dickson ste...@redhat.com
---
support/export/client.c | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/support/export/client.c b/support/export/client.c
index dbf47b9..f85e11c 100644
--- a/support/export/client.c
+++ b/support/export/client.c
@@ -482,8 +482,12 @@ add_name(char *old, const char *add)
else
cp = cp + strlen(cp);
}
- strncpy(new, old, cp-old);
- new[cp-old] = 0;
+ if (old) {
+ strncpy(new, old, cp-old);
+ new[cp-old] = 0;
+ } else {
+ new[0] = 0;
+ }
if (cp != old !*cp)
strcat(new, ,);
strcat(new, add);
--
2.0.0
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH V2 2/2] volatiles: Create /var/run/resolv.conf before linking to it
Sorry for such a late reply. I'll fix the commit log. The reason for the order change is that I get: rm: can't remove '/etc/resolv.conf': Read-only file system ln: /etc/resolv.conf: File exists every time on boot up. When switched, no error messages. It does still 'work', I just thought I'd clear up an error message while I was at it. Michael Gloff On Mon, Dec 15, 2014 at 8:13 AM, Gary Thomas g...@mlbassoc.com wrote: No commit log? Also, the order for a symbolic link should not matter, so why make this change? On 2014-12-13 12:57, Michael Gloff wrote: Signed-off-by: Michael Gloff mgl...@emacinc.com --- meta/recipes-core/initscripts/initscripts-1.0/volatiles | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-core/initscripts/initscripts-1.0/volatiles b/meta/recipes-core/initscripts/initscripts-1.0/volatiles index 1fc5816..e6f0695 100644 --- a/meta/recipes-core/initscripts/initscripts-1.0/volatiles +++ b/meta/recipes-core/initscripts/initscripts-1.0/volatiles @@ -32,7 +32,7 @@ l root root 1777 /tmp /var/tmp d root root 0755 /var/lock/subsys none f root root 0664 /var/log/wtmp none f root root 0664 /var/run/utmp none -l root root 0644 /etc/resolv.conf /var/run/resolv.conf f root root 0644 /var/run/resolv.conf none +l root root 0644 /etc/resolv.conf /var/run/resolv.conf d root root 1777 /run/media none l root root 1777 /media /run/media -- Gary Thomas | Consulting for the MLB Associates |Embedded world -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] opkg, opkg-config-base and opkg-collateral
Paul,
Thanks for looking into this further. I agree that poky-feed-config-opkg
does not work for anything other than a reference. I've resorted to
creating my own, but should be maybe even a part of the opkg recipe so as
not to disturb rpm/deb. Below is what I am using. arch.conf and
base-feeds.conf only really need all, architecture and machine.
FEEDURIPREFIX ?= ftp://MYMACHINE;
do_compile() {
mkdir -p ${S}/${sysconfdir}/opkg/
ipkgarchs=all ${MACHINE_ARCH} ${PACKAGE_ARCH}
basefeedconf=${S}/${sysconfdir}/opkg/base-feeds.conf
rm -f $basefeedconf
touch $basefeedconf
for arch in $ipkgarchs; do
echo src/gz $arch ${FEEDURIPREFIX}/$arch $basefeedconf
done
}
do_install () {
install -d ${D}${sysconfdir}/opkg
install -m 0644 ${S}/${sysconfdir}/opkg/* ${D}${sysconfdir}/opkg/
}
FILES_${PN} = ${sysconfdir}/opkg/
CONFFILES_${PN} += ${sysconfdir}/opkg/base-feeds.conf
Michael Gloff
On Sat, Dec 13, 2014 at 6:54 AM, Paul Barker p...@paulbarker.me.uk wrote:
On Wed, Nov 26, 2014 at 04:17:08PM +0100, Martin Jansa wrote:
On Wed, Nov 26, 2014 at 01:50:38PM +, Paul Barker wrote:
I'd keep three, but refactor them as I've described above:
- opkg: Includes '/etc/opkg/opkg.conf'
- opkg-arch-config: Includes '/etc/opkg/arch.conf', machine specific
- opkg-feed-config: Includes '/etc/opkg/feeds.conf', distro and
possibly machine specific
Please also check
http://git.openembedded.org/meta-openembedded/tree/meta-oe/recipes-core/meta/distro-feed-configs.bb
+ filtering the architectures
https://github.com/shr-distribution/meta-smartphone/blob/master/meta-shr-distro/recipes-core/meta/distro-feed-configs.bbappend
+ stricter filter for individual MACHINEs based on selected DEFAULTTUNE
https://github.com/shr-distribution/meta-smartphone/blob/master/meta-shr-distro/conf/distro/include/defaulttunes.inc
Thanks for the pointer Martin, I forgot to check outside oe-core. Also,
sorry
for the late reply, been rather busy recently!
I suggest we drop poky-feed-config-opkg from oe-core as it isn't really
usable
as-is and the Yocto Project manual recommends using distro-feed-config
anyway
(
http://www.yoctoproject.org/docs/1.7/mega-manual/mega-manual.html#runtime-package-management-build
).
I still think the opkg and opkg-collateral recipes should be refactored as
I
proposed in my previous email. I'll try to throw together some RFC patches
this
week.
We could also consider moving distro-feed-config to oe-core if it is the
recommended way to setup opkg feeds. I do think that a unified way of
configuring ipk/deb/rpm feeds would be good to have in the long term, but
we can
at least tidy up the opkg configuration for now.
Thanks,
--
Paul Barker
Email: p...@paulbarker.me.uk
http://www.paulbarker.me.uk
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 1/2] Link /media to /run/media
Since the change in automout.sh to mount devices to /run/media, we create the /run/media directory on startup and link /media to it. Signed-off-by: Michael Gloff mgl...@emacinc.com --- meta/recipes-core/initscripts/initscripts-1.0/volatiles | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta/recipes-core/initscripts/initscripts-1.0/volatiles b/meta/recipes-core/initscripts/initscripts-1.0/volatiles index 297245d..1fc5816 100644 --- a/meta/recipes-core/initscripts/initscripts-1.0/volatiles +++ b/meta/recipes-core/initscripts/initscripts-1.0/volatiles @@ -34,3 +34,5 @@ f root root 0664 /var/log/wtmp none f root root 0664 /var/run/utmp none l root root 0644 /etc/resolv.conf /var/run/resolv.conf f root root 0644 /var/run/resolv.conf none +d root root 1777 /run/media none +l root root 1777 /media /run/media -- 2.1.2.374.g63a4513 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 2/2] volatiles: Link /media to /run/media
Backport to dizzy also please since the automount change is already in. Michael Gloff On Sat, Dec 13, 2014 at 1:37 PM, Michael Gloff mgl...@emacinc.com wrote: Since the change in automout.sh to mount devices to /run/media, we create the /run/media directory on startup and link /media to it. Signed-off-by: Michael Gloff mgl...@emacinc.com --- meta/recipes-core/initscripts/initscripts-1.0/volatiles | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-core/initscripts/initscripts-1.0/volatiles b/meta/recipes-core/initscripts/initscripts-1.0/volatiles index 1fc5816..e6f0695 100644 --- a/meta/recipes-core/initscripts/initscripts-1.0/volatiles +++ b/meta/recipes-core/initscripts/initscripts-1.0/volatiles @@ -32,7 +32,7 @@ l root root 1777 /tmp /var/tmp d root root 0755 /var/lock/subsys none f root root 0664 /var/log/wtmp none f root root 0664 /var/run/utmp none -l root root 0644 /etc/resolv.conf /var/run/resolv.conf f root root 0644 /var/run/resolv.conf none +l root root 0644 /etc/resolv.conf /var/run/resolv.conf d root root 1777 /run/media none l root root 1777 /media /run/media -- 2.1.2.374.g63a4513 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH V2 2/2] volatiles: Create /var/run/resolv.conf before linking to it
Signed-off-by: Michael Gloff mgl...@emacinc.com --- meta/recipes-core/initscripts/initscripts-1.0/volatiles | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-core/initscripts/initscripts-1.0/volatiles b/meta/recipes-core/initscripts/initscripts-1.0/volatiles index 1fc5816..e6f0695 100644 --- a/meta/recipes-core/initscripts/initscripts-1.0/volatiles +++ b/meta/recipes-core/initscripts/initscripts-1.0/volatiles @@ -32,7 +32,7 @@ l root root 1777 /tmp /var/tmp d root root 0755 /var/lock/subsys none f root root 0664 /var/log/wtmp none f root root 0664 /var/run/utmp none -l root root 0644 /etc/resolv.conf /var/run/resolv.conf f root root 0644 /var/run/resolv.conf none +l root root 0644 /etc/resolv.conf /var/run/resolv.conf d root root 1777 /run/media none l root root 1777 /media /run/media -- 2.1.2.374.g63a4513 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH V2 1/2] Link /media to /run/media
Since the change in automout.sh to mount devices to /run/media, we create the /run/media directory on startup and link /media to it. Signed-off-by: Michael Gloff mgl...@emacinc.com --- meta/recipes-core/initscripts/initscripts-1.0/volatiles | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta/recipes-core/initscripts/initscripts-1.0/volatiles b/meta/recipes-core/initscripts/initscripts-1.0/volatiles index 297245d..1fc5816 100644 --- a/meta/recipes-core/initscripts/initscripts-1.0/volatiles +++ b/meta/recipes-core/initscripts/initscripts-1.0/volatiles @@ -34,3 +34,5 @@ f root root 0664 /var/log/wtmp none f root root 0664 /var/run/utmp none l root root 0644 /etc/resolv.conf /var/run/resolv.conf f root root 0644 /var/run/resolv.conf none +d root root 1777 /run/media none +l root root 1777 /media /run/media -- 2.1.2.374.g63a4513 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH V2 2/2] volatiles: Create /var/run/resolv.conf before linking to it
I really messed up the commit messages on the first one, please accept V2. Michael Gloff On Sat, Dec 13, 2014 at 1:57 PM, Michael Gloff mgl...@emacinc.com wrote: Signed-off-by: Michael Gloff mgl...@emacinc.com --- meta/recipes-core/initscripts/initscripts-1.0/volatiles | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-core/initscripts/initscripts-1.0/volatiles b/meta/recipes-core/initscripts/initscripts-1.0/volatiles index 1fc5816..e6f0695 100644 --- a/meta/recipes-core/initscripts/initscripts-1.0/volatiles +++ b/meta/recipes-core/initscripts/initscripts-1.0/volatiles @@ -32,7 +32,7 @@ l root root 1777 /tmp /var/tmp d root root 0755 /var/lock/subsys none f root root 0664 /var/log/wtmp none f root root 0664 /var/run/utmp none -l root root 0644 /etc/resolv.conf /var/run/resolv.conf f root root 0644 /var/run/resolv.conf none +l root root 0644 /etc/resolv.conf /var/run/resolv.conf d root root 1777 /run/media none l root root 1777 /media /run/media -- 2.1.2.374.g63a4513 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] /media automounting
Since the change in mount.sh to using /run/media, /media is nothing but an empty directory now. Should volatiles (00_core) be modified to create /run/media and link /media to it? This has worked for me on a read-only rootfs on a CF card, just not sure if this works for all scenarios. Also, I noticed that by changing the order creating /var/run/resolv.conf and linking it to /etc/resolve.conf got rid of an error of trying to remove and link it on startup. Should I include both of these fixes in one patch? Thanks, Michael Gloff -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] Opkg 0.2.3
On Thu, Oct 30, 2014 at 2:48 PM, Paul Barker p...@paulbarker.me.uk wrote: On 30 October 2014 19:15, Michael Gloff mgl...@emacinc.com wrote: As Paul mentioned yesterday opkg 0.2.4 is on it's way and 0.2.3 has been available for 2 months. If there are not any objections, I have an updated recipe and re-created previous patches that I could send. This should also modify opkg-colateral to use the new syntax for lists_dir. I'm also sat on tested patches, I was planning to send them tomorrow. I've held the patches back as the deadline for such changes for OE 1.7 had passed. Thanks Paul. I'll wait for your patch set. I hit send before checking inbox. I would also at this time like to propose changing the default list directory from /var/lib to something else (/usr/lib ?). On a read only rootfs, everything in /var/lib/ gets mounted on the tmpfs, therefore packages installed get lost. Changes in v0.3.0 will make this much easier to configure. You'll be able to set cache_dir, lists_dir, info_dir, lock_file and status_file in opkg.conf. I'd rather we left the defaults as-is and use those settings once v0.3.0 is released. v0.3.0 will also create any directories needed if they don't exist. So it may make sense to set cache_dir to something under /tmp, lock_file to something under /var or /run and everything else under /usr if that's what's desired. Cool, I'm looking forward to v0.3.0 and beyond Why not use the new syntax? The recipe should reflect the version of the package. Changing the lists_dir with 0.2.1 did not work for me. I can test the old syntax on 0.2.3 and see, if there is interest. Is there a reason why opkg-collateral.bb exists? And couldn't be merged with opkg? Michael Gloff I've tested changing the lists_dir and everything is working as expected. Michael Gloff Thanks, -- Paul Barker Email: p...@paulbarker.me.uk http://www.paulbarker.me.uk -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] Busybox/RFKILL
All,
I've run into a slight issue that when I enable RFKILL in busybox config,
my config gets overwritten by busybox.inc. I do not have wifi in
DISTRO_FEATURES. I believe that
busybox_cfg(bb.utils.contains('DISTRO_FEATURES', 'wifi', True, False, d),
'CONFIG_RFKILL', cnf, rem)
is not performing as intended and am unsure how to fix. I've tried a couple
of variations, but wound up just commenting it out for my local builds.
Basically, rfkill does not get configured in unless you have wifi
DISRO_FEATURES.
Michael Gloff
--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH] syslog: Change unused variable declaration LOCAL=0 to LOG_LOCAL=1
This fix allows the correct appending of -L to syslogd arguments when both file and remote logging are selected. Signed-off-by: Michael Gloff mgl...@emacinc.com --- meta/recipes-core/busybox/files/syslog |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-core/busybox/files/syslog b/meta/recipes-core/busybox/files/syslog index 2944d3d..89c4d12 100644 --- a/meta/recipes-core/busybox/files/syslog +++ b/meta/recipes-core/busybox/files/syslog @@ -28,7 +28,7 @@ if [ -f /etc/syslog-startup.conf ]; then if [ -n $ROTATEGENS ]; then SYSLOG_ARGS=$SYSLOG_ARGS -b $ROTATEGENS fi - LOCAL=0 + LOG_LOCAL=1 elif [ $D = remote ]; then SYSLOG_ARGS=$SYSLOG_ARGS -R $REMOTE LOG_REMOTE=1 -- 1.7.9.5 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
