Re: [oe] [meta-browser][PATCH] nspr: rename .bbappend to match new version from oe-core
On Wed, Sep 10, 2014 at 4:08 PM, Burton, Ross wrote:
> On 10 September 2014 20:06, Burton, Ross wrote:
>> On 10 September 2014 19:37, Trevor Woerner wrote:
>>> rename recipes-support/nspr/{nspr_4.10.3.bbappend => nspr_4.10.7.bbappend}
>>> (100%)
>>
>> Maybe use a wildcard bbappend?
>
> Or even better, try and make that bbappend disappear.
>
> A patch to add the BBCLASSEXTEND is trivial, the hacks may not be
> needed any more as nss in oe-core builds on all architectures.
I will try it here, and remove the bbappend. So we can be sure it can
be removed.
--
Otavio Salvador O.S. Systems
http://www.ossystems.com.brhttp://code.ossystems.com.br
Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [meta-browser][PATCH] nspr: rename .bbappend to match new version from oe-core
On 10 September 2014 20:06, Burton, Ross wrote:
> On 10 September 2014 19:37, Trevor Woerner wrote:
>> rename recipes-support/nspr/{nspr_4.10.3.bbappend => nspr_4.10.7.bbappend}
>> (100%)
>
> Maybe use a wildcard bbappend?
Or even better, try and make that bbappend disappear.
A patch to add the BBCLASSEXTEND is trivial, the hacks may not be
needed any more as nss in oe-core builds on all architectures.
Ross
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [meta-browser][PATCH] nspr: rename .bbappend to match new version from oe-core
On 10 September 2014 19:37, Trevor Woerner wrote:
> rename recipes-support/nspr/{nspr_4.10.3.bbappend => nspr_4.10.7.bbappend}
> (100%)
Maybe use a wildcard bbappend?
Ross
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [meta-browser][PATCH] nspr: rename .bbappend to match new version from oe-core
Signed-off-by: Trevor Woerner
---
recipes-support/nspr/{nspr_4.10.3.bbappend => nspr_4.10.7.bbappend} | 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename recipes-support/nspr/{nspr_4.10.3.bbappend => nspr_4.10.7.bbappend}
(100%)
diff --git a/recipes-support/nspr/nspr_4.10.3.bbappend
b/recipes-support/nspr/nspr_4.10.7.bbappend
similarity index 100%
rename from recipes-support/nspr/nspr_4.10.3.bbappend
rename to recipes-support/nspr/nspr_4.10.7.bbappend
--
2.0.1.563.g66f467c
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] [PATCH 02/14] autofs: add bash to RDEPENDS_autofs
Wouldn't it be a LOT more constructive to fix the bashism. I fail to see
the virtue in adding 2MB of "bash" to an embedded system just for a text
echo statement that no-one will actually read unless they hook up a
serial console to their TV set or so.
On 9-9-2014 18:27, Robert Yang wrote:
Bashism:
[snip]
possible bashism in autofs/etc/init.d/autofs line 116 ($"foo" should be eval_gettext
"foo"):
echo $"$prog not running"
possible bashism in autofs/etc/init.d/autofs line 120 ($"foo" should be eval_gettext
"foo"):
echo $"Reloading maps"
possible bashism in autofs/etc/init.d/autofs line 150 ($"foo" should be eval_gettext
"foo"):
echo $"Usage: $0
{start|forcestart|stop|restart|forcerestart|reload}"
[snip]
Signed-off-by: Robert Yang
---
.../recipes-daemons/autofs/autofs_5.1.0.bb |1 +
1 file changed, 1 insertion(+)
diff --git a/meta-networking/recipes-daemons/autofs/autofs_5.1.0.bb
b/meta-networking/recipes-daemons/autofs/autofs_5.1.0.bb
index aab2187..06ee77b 100644
--- a/meta-networking/recipes-daemons/autofs/autofs_5.1.0.bb
+++ b/meta-networking/recipes-daemons/autofs/autofs_5.1.0.bb
@@ -4,6 +4,7 @@ LICENSE = "GPL-2.0"
LIC_FILES_CHKSUM = "file://COPYING;md5=0636e73ff0215e8d672dc4c32c317bb3"
DEPENDS += "libtirpc flex-native bison-native"
+RDEPENDS_${PN} += "bash"
inherit autotools-brokensep systemd
--
Mike Looijmans
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
[oe] [meta-qt5] [daisy] qtwayland fetch fail
Hi all,
working on daisy, it looks like the fetching url of qtwayland is no
longer available.
The following patch helped me to solve the problem, hope it will help...
Regards
Pierluigi
===
diff --git a/recipes-qt/qt5/qtwayland-native_git.bb
b/recipes-qt/qt5/qtwayland-native_git.bb
index 988aa98..64485de 100644
--- a/recipes-qt/qt5/qtwayland-native_git.bb
+++ b/recipes-qt/qt5/qtwayland-native_git.bb
@@ -4,4 +4,5 @@ require ${PN}.inc
# qtwayland wasn't released yet, last tag before this SRCREV is
5.0.0-beta1
# qt5-git PV is only to indicate that this recipe is compatible with
qt5 5.2.1
-SRCREV = "a23777866ab77c4e8e6b501cf0fbe7c9223e"
+QT_MODULE_BRANCH = "dev"
+SRCREV = "573d0ee5ba86d99095f217ea9e19172bfc5e75fd"
diff --git a/recipes-qt/qt5/qtwayland_git.bb
b/recipes-qt/qt5/qtwayland_git.bb
index 789a882..c192914 100644
--- a/recipes-qt/qt5/qtwayland_git.bb
+++ b/recipes-qt/qt5/qtwayland_git.bb
@@ -4,6 +4,7 @@ require ${PN}.inc
# qtwayland wasn't released yet, last tag before this SRCREV is
5.0.0-beta1
# qt5-git PV is only to indicate that this recipe is compatible with
qt5 5.2.1
+QT_MODULE_BRANCH = "dev"
SRCREV = "573d0ee5ba86d99095f217ea9e19172bfc5e75fd"
SRC_URI += " \
--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] Backporting of latest recipes on oe-classic
On Wednesday 10 September 2014 19:39:58 Bryan wrote: > Can u please tell me which latest bitbake version i can use with > oe-classic. I used bitbake version 1.8.12 with my infra. So i need to use > bitbake version which would be suitable with my old recipes as well. If you use 1.8.12 and it works, wouldn't you just stick with that? Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] Backporting of latest recipes on oe-classic
Can u please tell me which latest bitbake version i can use with oe-classic. I used bitbake version 1.8.12 with my infra. So i need to use bitbake version which would be suitable with my old recipes as well. Regards Bryan On Sep 10, 2014 7:13 PM, "Bryan" wrote: > Hi Paul, > Do you know any forked repository where we can found support > for glibc 2.11.x, 2.12.x onwards. > > One more query is related to glibc version. Does it become eglibc in later > versions as we could not get later version recipes. > > Actually i have an old infra and i need to support icaclient 13 (citrix > receiver) which require libraries of later versions e.g. glibc, gtk, > libwebkit... > > Regards > Bryan > On Sep 9, 2014 6:32 PM, "Paul Eggleton" > wrote: > >> On Tuesday 09 September 2014 18:23:24 Bryan wrote: >> >We have some queries regarding OE-Classic. >> > 1. Where can we find latest recipes for oe-classic. >> >> http://cgit.openembedded.org/cgit.cgi/openembedded/ >> >> That's as up-to-date as it gets. There might be other forked repositories >> floating around, but that is the last official one. >> >> > Does oe-classic is still get updation for latest package support? >> >> No, as discussed on IRC, OE-Classic is now unmaintained. OE-Core and >> layers on >> top of it should ideally be used instead. >> >> > 2. How can we compile latest recipes of oe-core on oe-classic and >> ofcourse >> > there bitbake version would be different.Basically, we can say we need >> to >> > backport the recipe to classic. >> > e.g. gtk+2.20.1 & above, glibc-2.11.3 & above >> >> If you are determined to stay with OE-Classic I think you'd be better off >> just >> upgrading the recipes in OE-Classic - going backwards is going to be more >> painful. >> >> Here's the only semi-related information we have, which is about >> migration in >> the other direction; it could be helpful in terms of providing pointers: >> >> http://www.openembedded.org/wiki/Migrating_metadata_to_OE-Core >> >> Cheers, >> Paul >> >> -- >> >> Paul Eggleton >> Intel Open Source Technology Centre >> > -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] Backporting of latest recipes on oe-classic
On Wednesday 10 September 2014 19:13:58 Bryan wrote: > Hi Paul, > Do you know any forked repository where we can found support > for glibc 2.11.x, 2.12.x onwards. I don't, no, sorry. I don't keep track of OE-Classic forks and OpenEmbedded no longer maintains OE-Classic. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] Backporting of latest recipes on oe-classic
Hi Paul, Do you know any forked repository where we can found support for glibc 2.11.x, 2.12.x onwards. One more query is related to glibc version. Does it become eglibc in later versions as we could not get later version recipes. Actually i have an old infra and i need to support icaclient 13 (citrix receiver) which require libraries of later versions e.g. glibc, gtk, libwebkit... Regards Bryan On Sep 9, 2014 6:32 PM, "Paul Eggleton" wrote: > On Tuesday 09 September 2014 18:23:24 Bryan wrote: > >We have some queries regarding OE-Classic. > > 1. Where can we find latest recipes for oe-classic. > > http://cgit.openembedded.org/cgit.cgi/openembedded/ > > That's as up-to-date as it gets. There might be other forked repositories > floating around, but that is the last official one. > > > Does oe-classic is still get updation for latest package support? > > No, as discussed on IRC, OE-Classic is now unmaintained. OE-Core and > layers on > top of it should ideally be used instead. > > > 2. How can we compile latest recipes of oe-core on oe-classic and > ofcourse > > there bitbake version would be different.Basically, we can say we need to > > backport the recipe to classic. > > e.g. gtk+2.20.1 & above, glibc-2.11.3 & above > > If you are determined to stay with OE-Classic I think you'd be better off > just > upgrading the recipes in OE-Classic - going backwards is going to be more > painful. > > Here's the only semi-related information we have, which is about migration > in > the other direction; it could be helpful in terms of providing pointers: > > http://www.openembedded.org/wiki/Migrating_metadata_to_OE-Core > > Cheers, > Paul > > -- > > Paul Eggleton > Intel Open Source Technology Centre > -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] Error while bitbake meta-toolchain-qt5
i am using Daisy branch. On Wed, Sep 10, 2014 at 4:47 PM, Otavio Salvador wrote: > On Wed, Sep 10, 2014 at 1:17 AM, Switesh Fulpagare > wrote: > > Hi Otavio, > > Please confirm the following that i had understood - > > > > 1. You have pushed the fix. > > 2. Now, i have to apply the patch, with > > > > SRCREV = "98dca3b54f52f08117c1e0d3a1b4826ed12ef23f" > > +QT_MODULE_BRANCH = "5.4" > > > > SRC_URI += " \ > > > file://0001-examples.pro-include-server-buffer-only-when-buildin.patch > > \ > > > > 3. I need to write > > SRCREV = "98dca3b54f52f08117c1e0d3a1b4826ed12ef23f" > > +QT_MODULE_BRANCH = "5.4" > > in the file, > Home/bin/fsl-community-bsp/sources/meta-qt5//recipes-qt/qt5/ > > qtwayland_git.bb > > > > 4. Then apply patch > > $ patch < > > file://0001-examples.pro-include-server-buffer-only-when-buildin.patch \ > > > > Are the above steps are right? Please Otavio consider that i m beginner > in > > the Linux platform. > > Are you using Daisy or master? > > > -- > Otavio Salvador O.S. Systems > http://www.ossystems.com.brhttp://code.ossystems.com.br > Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750 > -- > ___ > Openembedded-devel mailing list > Openembedded-devel@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-devel > -- “The contents of this e-mail message and any attachments are confidential and are intended solely for addressee. The information may also be legally privileged. This transmission is sent in trust, for the sole purpose of delivery to the intended recipient. If you have received this transmission in error, any use, reproduction or dissemination of this transmission is strictly prohibited. If you are not the intended recipient, please immediately notify the sender by reply e-mail or phone and delete this message and its attachments, if any.” -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
Re: [oe] Error while bitbake meta-toolchain-qt5
On Wed, Sep 10, 2014 at 1:17 AM, Switesh Fulpagare wrote: > Hi Otavio, > Please confirm the following that i had understood - > > 1. You have pushed the fix. > 2. Now, i have to apply the patch, with > > SRCREV = "98dca3b54f52f08117c1e0d3a1b4826ed12ef23f" > +QT_MODULE_BRANCH = "5.4" > > SRC_URI += " \ > file://0001-examples.pro-include-server-buffer-only-when-buildin.patch > \ > > 3. I need to write > SRCREV = "98dca3b54f52f08117c1e0d3a1b4826ed12ef23f" > +QT_MODULE_BRANCH = "5.4" > in the file, Home/bin/fsl-community-bsp/sources/meta-qt5//recipes-qt/qt5/ > qtwayland_git.bb > > 4. Then apply patch > $ patch < > file://0001-examples.pro-include-server-buffer-only-when-buildin.patch \ > > Are the above steps are right? Please Otavio consider that i m beginner in > the Linux platform. Are you using Daisy or master? -- Otavio Salvador O.S. Systems http://www.ossystems.com.brhttp://code.ossystems.com.br Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750 -- ___ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-devel
