* Re: xerver-xorg build problem
From: Koen Kooi @ 2011-10-19 19:19 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
Cc: Patches and discussions about the oe-core layer
In-Reply-To: <201110192102.50043.schnitzeltony@gmx.de>
add mesa-dri to DEPENDS in the xorg .bb, not the .inc
Op 19 okt. 2011 om 21:02 heeft Andreas Müller <schnitzeltony@gmx.de> het volgende geschreven:
> On Wednesday, October 19, 2011 08:22:27 PM Khem Raj wrote:
>> Hi
>>
>> I am seeing this error today
>>
>>
>> | checking for GL... yes
>> | checking for DRIPROTO... yes
>> | checking for DRI... no
>> | configure: error: Package requirements (glproto >= 1.4.14 dri >=
>> 7.8.0) were not met:
>> |
>> | No package 'dri' found
>> |
>> | Consider adjusting the PKG_CONFIG_PATH environment variable if you
>> | installed software in a non-standard prefix.
>> |
>> | Alternatively, you may set the environment variables DRI_CFLAGS
>> | and DRI_LIBS to avoid the need to call pkg-config.
>> | See the pkg-config man page for more details.
>> | + bbfatal 'oe_runconf failed'
>> | + echo 'ERROR: oe_runconf failed'
>> | ERROR: oe_runconf failed
>> | + exit 1
>> | ERROR: Function 'do_configure' failed (see
>> /home/kraj/work/angstrom/build/tmp-angstrom_2010_x-eglibc/work/ppc603e-angstrom-linux/xserver-xorg-2_1.11.1-r1/temp/log.do_configure.21621
>> for further information)
>> NOTE: package xserver-xorg-2_1.11.1-r1: task do_configure: Failed
>> ERROR: Task 1518
>> (/home/kraj/work/angstrom/sources/openembedded-core/meta/recipes-graphics/xorg-xserver/xserver-xorg_1.11.1.bb,
>> do_configure) failed with exit code '1'
>> Waiting for 2 active tasks to finish:
>>
>>
>> any hints ?
>>
> I think it is this one [1]: manually build mesa-xlib and mesa-dri. What could be a proper solution on that?
>
> Andreas
>
> [1] http://lists.linuxtogo.org/pipermail/openembedded-core/2011-October/011281.html
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
^ permalink raw reply
* Re: [oe-core 2/4] qt4-x11-free: bring back pkg-config fixups
From: Simon Busch @ 2011-10-19 19:02 UTC (permalink / raw)
To: openembedded-core
In-Reply-To: <4E95D6EB.4050703@gravedo.de>
On 12.10.2011 20:05, Simon Busch wrote:
> On 12.10.2011 11:23, Paul Eggleton wrote:
>> On Wednesday 12 October 2011 08:45:03 Martin Jansa wrote:
>>> From: Simon Busch <morphis@gravedo.de>
>>>
>>> With b40b9c024be5e1ec81a31961158b3e6b529acfe0 some pkg-config fixups where
>>> removed from qt4.inc which breaks the pkg-config files for qt4-embedded.
>>> Without that the pkg-config files for qt4-x11-free are broken. So this
>>> patch puts the fixes into the qt4-x11-free.inc file to be used by
>>> qt4-x11-free and not qt4-embedded.
>>
>> So why do we need these only in the X11 version? Surely they should be
>> applicable to both embedded and X11, or not at all...?
>
> With b40b9c024be5e1ec81a31961158b3e6b529acfe0 I removed this fixups from
> qt4.inc as I had problems with building agains qt4-embedded as cflags
> were incorrect in the created pkg-config files.
>
> Now I switched my application to x11 and got other problems with the
> pkg-config files from qt4-x11-free which can be resolved with the fixups
> I removed before.
>
> So you are right we need them for qt4-x11-free but not for qt4-embedded.
> I didn't investigated from where these differences are coming.
>
> regards,
> Simon
>
Still any comments on this or is the patch already accepted?
regards,
Simon
--
Simon Busch - http://mm.gravedo.de/blog/
^ permalink raw reply
* Re: [CONSOLIDATED PULL 14/16] distro-tracking: update data for some toolchain recipes
From: Otavio Salvador @ 2011-10-19 19:00 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer; +Cc: Phil Blundell, Saul Wold
In-Reply-To: <CAMKF1sqffiB0WMnhv3wVNseaMcL8TjXUePYXhvdUcwwk4roPag@mail.gmail.com>
On Wed, Oct 19, 2011 at 16:30, Khem Raj <raj.khem@gmail.com> wrote:
...
>>>> Many upstreams we can't track if updates are required automagically, so
>>>> we
>>>> need a place to record when the last manual check was, also possible
>>>> reasons
>>>> why we should not update to newer versions, ...
>
> hmm manual check means it has to be done manually is there any thing
> that needs it ?
>
> I think unless they are distro specific which seems not since they are
> in oe-core
> they could exist in recipes thats my opinion.
I agree that this should be put into the recipes. Besides this allows
for checking if it was updated when the version has been updated.
If done right, when updating the version this data will be updated
together. I see no change in the amount of changes.
A plus of this choice is it will be more difficult to forget to update
that info. This happened in last qt update for an example.
--
Otavio Salvador O.S. Systems
E-mail: otavio@ossystems.com.br http://www.ossystems.com.br
Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br
^ permalink raw reply
* Re: xerver-xorg build problem
From: Andreas Müller @ 2011-10-19 19:02 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
In-Reply-To: <CAMKF1spgu+h2_LD3Qp6129QCxb5XHKSru0ggOHt3vCqG=8s7Jw@mail.gmail.com>
On Wednesday, October 19, 2011 08:22:27 PM Khem Raj wrote:
> Hi
>
> I am seeing this error today
>
>
> | checking for GL... yes
> | checking for DRIPROTO... yes
> | checking for DRI... no
> | configure: error: Package requirements (glproto >= 1.4.14 dri >=
> 7.8.0) were not met:
> |
> | No package 'dri' found
> |
> | Consider adjusting the PKG_CONFIG_PATH environment variable if you
> | installed software in a non-standard prefix.
> |
> | Alternatively, you may set the environment variables DRI_CFLAGS
> | and DRI_LIBS to avoid the need to call pkg-config.
> | See the pkg-config man page for more details.
> | + bbfatal 'oe_runconf failed'
> | + echo 'ERROR: oe_runconf failed'
> | ERROR: oe_runconf failed
> | + exit 1
> | ERROR: Function 'do_configure' failed (see
> /home/kraj/work/angstrom/build/tmp-angstrom_2010_x-eglibc/work/ppc603e-angstrom-linux/xserver-xorg-2_1.11.1-r1/temp/log.do_configure.21621
> for further information)
> NOTE: package xserver-xorg-2_1.11.1-r1: task do_configure: Failed
> ERROR: Task 1518
> (/home/kraj/work/angstrom/sources/openembedded-core/meta/recipes-graphics/xorg-xserver/xserver-xorg_1.11.1.bb,
> do_configure) failed with exit code '1'
> Waiting for 2 active tasks to finish:
>
>
> any hints ?
>
I think it is this one [1]: manually build mesa-xlib and mesa-dri. What could be a proper solution on that?
Andreas
[1] http://lists.linuxtogo.org/pipermail/openembedded-core/2011-October/011281.html
^ permalink raw reply
* Re: [CONSOLIDATED PULL 14/16] distro-tracking: update data for some toolchain recipes
From: Khem Raj @ 2011-10-19 18:30 UTC (permalink / raw)
To: Saul Wold; +Cc: Phil Blundell, Patches and discussions about the oe-core layer
In-Reply-To: <4E9F0CCF.3070404@intel.com>
On Wed, Oct 19, 2011 at 10:45 AM, Saul Wold <saul.wold@intel.com> wrote:
> On 10/19/2011 10:00 AM, Khem Raj wrote:
>>
>> On Wed, Oct 19, 2011 at 9:57 AM, Saul Wold<saul.wold@intel.com> wrote:
>>>
>>> On 10/19/2011 09:49 AM, Phil Blundell wrote:
>>>>
>>>> On Wed, 2011-10-19 at 18:37 +0200, Koen Kooi wrote:
>>>>>
>>>>> Op 19 okt. 2011, om 18:24 heeft Kamble, Nitin A het volgende
>>>>> geschreven:
>>>>>>
>>>>>> It will be too many recipes to list on one line, shall I split the
>>>>>> commit into multiple one for each recipe whose data is changed?
>>>>>
>>>>> Or per group, but saying "some toolchain recipes" is way too vague.
>>>>
>>>> Why do we have this distro tracking data in oe-core git anyway? I'm not
>>>> entirely clear on what it's used by.
>>>>
>>> Phil:
>>>
>>> It's used by the tools that build http://packages.yoctoproject.org and to
>>> help recipe manage maintainer-ship and track what needs updating.
>>
>> This could be managed via meta-data in packages I believe all that
>> information is there.
>>
> Khem,
>
> I am not quite following, are you suggesting incorporating the
> distro_tracking_fields info into the final packages (this word is overloaded
> sometimes), or adding it the recipe bb files?
I think this information is better generated at build time. Since that
will be accurate and the meta data can be
>
> If adding it to the recipe bb files, this was discussed and deemed
> inappropriate, as it's too dynamic and would clutter the recipe.
is it more dynamic than making any other change to the recipe ?
in other words are there chances that you just need to change the
recipe to mark this information.
>
> Sau!
>>>
>>> Many upstreams we can't track if updates are required automagically, so
>>> we
>>> need a place to record when the last manual check was, also possible
>>> reasons
>>> why we should not update to newer versions, ...
hmm manual check means it has to be done manually is there any thing
that needs it ?
I think unless they are distro specific which seems not since they are
in oe-core
they could exist in recipes thats my opinion.
>>>
>>> Sau!
>>>
>>>
>>>> p.
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Openembedded-core mailing list
>>>> Openembedded-core@lists.openembedded.org
>>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>>>
>>>
>>>
>>> _______________________________________________
>>> Openembedded-core mailing list
>>> Openembedded-core@lists.openembedded.org
>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>>
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
^ permalink raw reply
* xerver-xorg build problem
From: Khem Raj @ 2011-10-19 18:22 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
Hi
I am seeing this error today
| checking for GL... yes
| checking for DRIPROTO... yes
| checking for DRI... no
| configure: error: Package requirements (glproto >= 1.4.14 dri >=
7.8.0) were not met:
|
| No package 'dri' found
|
| Consider adjusting the PKG_CONFIG_PATH environment variable if you
| installed software in a non-standard prefix.
|
| Alternatively, you may set the environment variables DRI_CFLAGS
| and DRI_LIBS to avoid the need to call pkg-config.
| See the pkg-config man page for more details.
| + bbfatal 'oe_runconf failed'
| + echo 'ERROR: oe_runconf failed'
| ERROR: oe_runconf failed
| + exit 1
| ERROR: Function 'do_configure' failed (see
/home/kraj/work/angstrom/build/tmp-angstrom_2010_x-eglibc/work/ppc603e-angstrom-linux/xserver-xorg-2_1.11.1-r1/temp/log.do_configure.21621
for further information)
NOTE: package xserver-xorg-2_1.11.1-r1: task do_configure: Failed
ERROR: Task 1518
(/home/kraj/work/angstrom/sources/openembedded-core/meta/recipes-graphics/xorg-xserver/xserver-xorg_1.11.1.bb,
do_configure) failed with exit code '1'
Waiting for 2 active tasks to finish:
any hints ?
-Khem
^ permalink raw reply
* Re: [CONSOLIDATED PULL 14/16] distro-tracking: update data for some toolchain recipes
From: Saul Wold @ 2011-10-19 17:45 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer; +Cc: Phil Blundell
In-Reply-To: <CAMKF1srj1OrgnSwihsVGDCVasAc6zTHRJkfAkjFOpM80mUFM9A@mail.gmail.com>
On 10/19/2011 10:00 AM, Khem Raj wrote:
> On Wed, Oct 19, 2011 at 9:57 AM, Saul Wold<saul.wold@intel.com> wrote:
>> On 10/19/2011 09:49 AM, Phil Blundell wrote:
>>>
>>> On Wed, 2011-10-19 at 18:37 +0200, Koen Kooi wrote:
>>>>
>>>> Op 19 okt. 2011, om 18:24 heeft Kamble, Nitin A het volgende geschreven:
>>>>>
>>>>> It will be too many recipes to list on one line, shall I split the
>>>>> commit into multiple one for each recipe whose data is changed?
>>>>
>>>> Or per group, but saying "some toolchain recipes" is way too vague.
>>>
>>> Why do we have this distro tracking data in oe-core git anyway? I'm not
>>> entirely clear on what it's used by.
>>>
>> Phil:
>>
>> It's used by the tools that build http://packages.yoctoproject.org and to
>> help recipe manage maintainer-ship and track what needs updating.
>
> This could be managed via meta-data in packages I believe all that
> information is there.
>
Khem,
I am not quite following, are you suggesting incorporating the
distro_tracking_fields info into the final packages (this word is
overloaded sometimes), or adding it the recipe bb files?
If adding it to the recipe bb files, this was discussed and deemed
inappropriate, as it's too dynamic and would clutter the recipe.
Sau!
>>
>> Many upstreams we can't track if updates are required automagically, so we
>> need a place to record when the last manual check was, also possible reasons
>> why we should not update to newer versions, ...
>>
>> Sau!
>>
>>
>>> p.
>>>
>>>
>>>
>>> _______________________________________________
>>> Openembedded-core mailing list
>>> Openembedded-core@lists.openembedded.org
>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>>
>>
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
^ permalink raw reply
* Re: [CONSOLIDATED PULL 14/16] distro-tracking: update data for some toolchain recipes
From: Khem Raj @ 2011-10-19 17:00 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer; +Cc: Phil Blundell
In-Reply-To: <4E9F018D.7030703@intel.com>
On Wed, Oct 19, 2011 at 9:57 AM, Saul Wold <saul.wold@intel.com> wrote:
> On 10/19/2011 09:49 AM, Phil Blundell wrote:
>>
>> On Wed, 2011-10-19 at 18:37 +0200, Koen Kooi wrote:
>>>
>>> Op 19 okt. 2011, om 18:24 heeft Kamble, Nitin A het volgende geschreven:
>>>>
>>>> It will be too many recipes to list on one line, shall I split the
>>>> commit into multiple one for each recipe whose data is changed?
>>>
>>> Or per group, but saying "some toolchain recipes" is way too vague.
>>
>> Why do we have this distro tracking data in oe-core git anyway? I'm not
>> entirely clear on what it's used by.
>>
> Phil:
>
> It's used by the tools that build http://packages.yoctoproject.org and to
> help recipe manage maintainer-ship and track what needs updating.
This could be managed via meta-data in packages I believe all that
information is there.
>
> Many upstreams we can't track if updates are required automagically, so we
> need a place to record when the last manual check was, also possible reasons
> why we should not update to newer versions, ...
>
> Sau!
>
>
>> p.
>>
>>
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
^ permalink raw reply
* Re: [CONSOLIDATED PULL 14/16] distro-tracking: update data for some toolchain recipes
From: Saul Wold @ 2011-10-19 16:57 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer; +Cc: Phil Blundell
In-Reply-To: <1319042998.22985.257.camel@phil-desktop>
On 10/19/2011 09:49 AM, Phil Blundell wrote:
> On Wed, 2011-10-19 at 18:37 +0200, Koen Kooi wrote:
>> Op 19 okt. 2011, om 18:24 heeft Kamble, Nitin A het volgende geschreven:
>>> It will be too many recipes to list on one line, shall I split the commit into multiple one for each recipe whose data is changed?
>>
>> Or per group, but saying "some toolchain recipes" is way too vague.
>
> Why do we have this distro tracking data in oe-core git anyway? I'm not
> entirely clear on what it's used by.
>
Phil:
It's used by the tools that build http://packages.yoctoproject.org and
to help recipe manage maintainer-ship and track what needs updating.
Many upstreams we can't track if updates are required automagically, so
we need a place to record when the last manual check was, also possible
reasons why we should not update to newer versions, ...
Sau!
> p.
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
^ permalink raw reply
* Re: [CONSOLIDATED PULL 14/16] distro-tracking: update data for some toolchain recipes
From: Phil Blundell @ 2011-10-19 16:49 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
In-Reply-To: <158EAB1C-0C40-4C5B-B47A-A4B8C90A2055@dominion.thruhere.net>
On Wed, 2011-10-19 at 18:37 +0200, Koen Kooi wrote:
> Op 19 okt. 2011, om 18:24 heeft Kamble, Nitin A het volgende geschreven:
> > It will be too many recipes to list on one line, shall I split the commit into multiple one for each recipe whose data is changed?
>
> Or per group, but saying "some toolchain recipes" is way too vague.
Why do we have this distro tracking data in oe-core git anyway? I'm not
entirely clear on what it's used by.
p.
^ permalink raw reply
* Re: [CONSOLIDATED PULL 14/16] distro-tracking: update data for some toolchain recipes
From: Koen Kooi @ 2011-10-19 16:37 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
In-Reply-To: <9DA5872FEF993D41B7173F58FCF6BE94E2F42F6A@orsmsx504.amr.corp.intel.com>
Op 19 okt. 2011, om 18:24 heeft Kamble, Nitin A het volgende geschreven:
>
>
>> -----Original Message-----
>> From: openembedded-core-bounces@lists.openembedded.org
>> [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf Of
>> Koen Kooi
>> Sent: Wednesday, October 19, 2011 8:52 AM
>> To: Patches and discussions about the oe-core layer
>> Subject: Re: [OE-core] [CONSOLIDATED PULL 14/16] distro-tracking:
>> update data for some toolchain recipes
>>
>>
>> Op 19 okt. 2011, om 17:49 heeft Kamble, Nitin A het volgende
>> geschreven:
>>
>>> Koen,
>>> Why do you ask ?
>>
>> Because I want the commit message to match to commit and now it
>> doesn't.
>>
> It will be too many recipes to list on one line, shall I split the commit into multiple one for each recipe whose data is changed?
Or per group, but saying "some toolchain recipes" is way too vague.
^ permalink raw reply
* Re: [CONSOLIDATED PULL 14/16] distro-tracking: update data for some toolchain recipes
From: Kamble, Nitin A @ 2011-10-19 16:24 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
In-Reply-To: <E8FAD09F-4767-4ACB-9588-EFC57570F176@dominion.thruhere.net>
> -----Original Message-----
> From: openembedded-core-bounces@lists.openembedded.org
> [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf Of
> Koen Kooi
> Sent: Wednesday, October 19, 2011 8:52 AM
> To: Patches and discussions about the oe-core layer
> Subject: Re: [OE-core] [CONSOLIDATED PULL 14/16] distro-tracking:
> update data for some toolchain recipes
>
>
> Op 19 okt. 2011, om 17:49 heeft Kamble, Nitin A het volgende
> geschreven:
>
> > Koen,
> > Why do you ask ?
>
> Because I want the commit message to match to commit and now it
> doesn't.
>
It will be too many recipes to list on one line, shall I split the commit into multiple one for each recipe whose data is changed?
Nitin
> >
> > Nitin
> >
> >> -----Original Message-----
> >> From: openembedded-core-bounces@lists.openembedded.org
> >> [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf
> Of
> >> Koen Kooi
> >> Sent: Wednesday, October 19, 2011 1:31 AM
> >> To: Patches and discussions about the oe-core layer
> >> Subject: Re: [OE-core] [CONSOLIDATED PULL 14/16] distro-tracking:
> >> update data for some toolchain recipes
> >>
> >> btrfs-tools is a toolchain recipe?!?!?!
> >>
> >>
> >>
> >> Op 19 okt. 2011, om 10:28 heeft Saul Wold het volgende geschreven:
> >>
> >>> From: Nitin A Kamble <nitin.a.kamble@intel.com>
> >>>
> >>> Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
> >>> ---
> >>> .../conf/distro/include/distro_tracking_fields.inc | 42
> >> ++++++++++++--------
> >>> 1 files changed, 25 insertions(+), 17 deletions(-)
> >>>
> >>> diff --git a/meta/conf/distro/include/distro_tracking_fields.inc
> >> b/meta/conf/distro/include/distro_tracking_fields.inc
> >>> index abc2cbf..e68bbe1 100644
> >>> --- a/meta/conf/distro/include/distro_tracking_fields.inc
> >>> +++ b/meta/conf/distro/include/distro_tracking_fields.inc
> >>> @@ -3005,11 +3005,19 @@ RECIPE_STATUS_pn-run-postinsts="green" #
> all
> >> local code
> >>> RECIPE_LATEST_VERSION_pn-postinsts="1.0"
> >>> RECIPE_MAINTAINER_pn-postinsts = "Nitin A Kamble
> >> <nitin.a.kamble@intel.com>"
> >>>
> >>> -RECIPE_STATUS_pn-nasm="green"
> >>> +RECIPE_STATUS_pn-nasm="green"
> >>> RECIPE_LATEST_VERSION_pn-nasm="2.07"
> >>> -RECIPE_MANUAL_CHECK_DATE_pn-nasm = "Jul 06, 2011"
> >>> +RECIPE_MANUAL_CHECK_DATE_pn-nasm = "Oct 18, 2011"
> >>> +RECIPE_LAST_UPDATE_pn-nasm = "Jun 23, 2010"
> >>> RECIPE_MAINTAINER_pn-nasm = "Nitin A Kamble
> >> <nitin.a.kamble@intel.com>"
> >>>
> >>> +RECIPE_STATUS_pn-btrfs-tools="green"
> >>> +RECIPE_LATEST_VERSION_pn-btrfs-tools="git"
> >>> +RECIPE_MANUAL_CHECK_DATE_pn-btrfs-tools = "Oct 18, 2011"
> >>> +RECIPE_LAST_UPDATE_pn-btrfs-tools = "Jun 09, 2011"
> >>> +RECIPE_MAINTAINER_pn-btrfs-tools = "Nitin A Kamble
> >> <nitin.a.kamble@intel.com>"
> >>> +DISTRO_PN_ALIAS_pn-btrfs-tools = "Debian=btrfs-tools Fedora=btrfs-
> >> progs"
> >>> +
> >>> RECIPE_STATUS_pn-perl="red" # upgrade needed
> >>> RECIPE_LATEST_VERSION_pn-perl="5.12.1"
> >>> RECIPE_LAST_UPDATE_pn-perl = "May 27, 2007"
> >>> @@ -3020,9 +3028,9 @@ RECIPE_LATEST_VERSION_pn-
> >> prelink="1.0+git0+0x909470ee441237563d6236c505cb2d02ddc
> >>> RECIPE_LAST_UPDATE_pn-perl = "Jul 23, 2010"
> >>> RECIPE_MAINTAINER_pn-prelink = "Mark Hatle
> >> <mark.hatle@windriver.com>"
> >>>
> >>> -RECIPE_STATUS_pn-python-dbus="red"
> >>> -RECIPE_LATEST_VERSION_pn-python-dbus="0.83.1"
> >>> -RECIPE_LAST_UPDATE_pn-python-dbus = "Jul 7, 2010"
> >>> +RECIPE_STATUS_pn-python-dbus="green"
> >>> +RECIPE_LATEST_VERSION_pn-python-dbus="0.84.0"
> >>> +RECIPE_LAST_UPDATE_pn-python-dbus = "Oct 18, 2011"
> >>> RECIPE_MAINTAINER_pn-python-dbus = "Nitin A Kamble
> >> <nitin.a.kamble@intel.com>"
> >>> DISTRO_PN_ALIAS_pn-python-dbus = "Ubuntu=python-dbus Debian=python-
> >> dbus Mandriva=python-dbus"
> >>>
> >>> @@ -3062,7 +3070,8 @@ RECIPE_MAINTAINER_pn-python-pyrex = "Nitin A
> >> Kamble <nitin.a.kamble@intel.com>"
> >>> DISTRO_PN_ALIAS_pn-python-pyrex = "Mandriva=python-pyrex
> >> Ubuntu=python-pyrex"
> >>>
> >>> RECIPE_STATUS_pn-python-scons="green"
> >>> -RECIPE_LATEST_VERSION_pn-python-scons="2.0.1"
> >>> +RECIPE_LATEST_VERSION_pn-python-scons="2.1.0"
> >>> +RECIPE_LAST_UPDATE_pn-python-scons = "Oct 18, 2011"
> >>> DISTRO_PN_ALIAS_pn-python-scons = "Fedora=scons OpenSuSE=scons
> >> Ubuntu=scons Mandriva=scons Debian=scons"
> >>> RECIPE_LAST_UPDATE_pn-python-scons = "Nov 8, 2010"
> >>> RECIPE_MAINTAINER_pn-python-scons = "Nitin A Kamble
> >> <nitin.a.kamble@intel.com>"
> >>> @@ -3087,15 +3096,16 @@ RECIPE_LATEST_VERSION_pn-
> unifdef="2.6.18+git"
> >>> RECIPE_MAINTAINER_pn-unifdef = "Nitin A Kamble
> >> <nitin.a.kamble@intel.com>"
> >>>
> >>> RECIPE_STATUS_pn-gnu-config="green"
> >>> -RECIPE_LATEST_VERSION_pn-gnu-config="0.0+git3155524"
> >>> +RECIPE_LATEST_VERSION_pn-gnu-config="svn"
> >>> DISTRO_PN_ALIAS_pn-gnu-config = "OpenedHand"
> >>> RECIPE_LAST_UPDATE_pn-gnu-config = "Jun 21, 2010"
> >>> -RECIPE_MANUAL_CHECK_DATE_pn-gnu-config = "Jul 06, 2011"
> >>> +RECIPE_MANUAL_CHECK_DATE_pn-gnu-config = "Oct 18, 2011"
> >>> RECIPE_MAINTAINER_pn-gnu-config = "Nitin A Kamble
> >> <nitin.a.kamble@intel.com>"
> >>>
> >>> RECIPE_STATUS_pn-mpfr="green"
> >>> -RECIPE_LATEST_VERSION_pn-mpfr="3.0.0"
> >>> -RECIPE_MANUAL_CHECK_DATE_pn-mpfr = "Jul 06, 2011"
> >>> +RECIPE_LATEST_VERSION_pn-mpfr="3.0.1"
> >>> +RECIPE_MANUAL_CHECK_DATE_pn-mpfr = "Oct 18, 2011"
> >>> +RECIPE_LAST_UPDATE_pn-mpfr = "Apr 07, 2011"
> >>> RECIPE_MAINTAINER_pn-mpfr = "Nitin A Kamble
> >> <nitin.a.kamble@intel.com>"
> >>>
> >>> RECIPE_STATUS_pn-gmp="green"
> >>> @@ -3110,9 +3120,10 @@ RECIPE_MANUAL_CHECK_DATE_pn-libmpc = "Jan
> 25,
> >> 2011"
> >>> RECIPE_MAINTAINER_pn-libmpc = "Nitin A Kamble
> >> <nitin.a.kamble@intel.com>"
> >>> DISTRO_PN_ALIAS_pn-libmpc = "Fedora=libmpc OpenSuse=libmpc2"
> >>>
> >>> -RECIPE_STATUS_pn-byacc="red"
> >>> +RECIPE_STATUS_pn-byacc="green"
> >>> RECIPE_LATEST_VERSION_pn-byacc="20101229"
> >>> -RECIPE_MANUAL_CHECK_DATE_pn-byacc = "Jul 06, 2011"
> >>> +RECIPE_MANUAL_CHECK_DATE_pn-byacc = "Oct 18, 2011"
> >>> +RECIPE_LAST_UPDATE_pn-byacc = "Oct 18, 2010"
> >>> RECIPE_MAINTAINER_pn-byacc = "Nitin A Kamble
> >> <nitin.a.kamble@intel.com>"
> >>>
> >>> RECIPE_STATUS_pn-libconvert-asn1-perl="green"
> >>> @@ -3122,8 +3133,8 @@ RECIPE_LAST_UPDATE_pn-libconvert-asn1-perl =
> >> "Aug 13, 2010"
> >>> RECIPE_MAINTAINER_pn-libconvert-asn1-perl = "Nitin A Kamble
> >> <nitin.a.kamble@intel.com>"
> >>>
> >>> RECIPE_STATUS_pn-libxml-parser-perl="green"
> >>> -RECIPE_LATEST_VERSION_pn-libxml-parser-perl="2.36"
> >>> -RECIPE_LAST_UPDATE_pn-libxml-parser-perl = "Nov 18, 2009"
> >>> +RECIPE_LATEST_VERSION_pn-libxml-parser-perl="2.41"
> >>> +RECIPE_LAST_UPDATE_pn-libxml-parser-perl = "Oct 18, 2011"
> >>> RECIPE_MAINTAINER_pn-libxml-parser-perl = "Nitin A Kamble
> >> <nitin.a.kamble@intel.com>"
> >>>
> >>> RECIPE_STATUS_pn-cmake-native="green"
> >>> @@ -5922,9 +5933,6 @@ RECIPE_COMMENTS_pn-pseudo = "Yocto Project
> >> maintained"
> >>> RECIPE_MANUAL_CHECK_DATE_pn-pseudo = "Jun 06, 2011"
> >>> DISTRO_PN_ALIAS_pn-pseudo = "Windriver"
> >>>
> >>> -DISTRO_PN_ALIAS_pn-btrfs-tools = "Debian=btrfs-tools Fedora=btrfs-
> >> progs"
> >>> -RECIPE_MAINTAINER_pn-btrfs-tools = "Nitin A Kamble
> >> <nitin.a.kamble@intel.com>"
> >>> -
> >>> DISTRO_PN_ALIAS_pn-rt-tests = "Debian=rt-tests Ubuntu=rt-tests"
> >>> RECIPE_MAINTAINER_pn-rt-tests = "Darren Hart
> >> <dvhart@linux.intel.com>"
> >>>
> >>> --
> >>> 1.7.6.2
> >>>
> >>>
> >>> _______________________________________________
> >>> Openembedded-core mailing list
> >>> Openembedded-core@lists.openembedded.org
> >>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-
> core
> >>
> >>
> >> _______________________________________________
> >> Openembedded-core mailing list
> >> Openembedded-core@lists.openembedded.org
> >> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-
> core
> >
> > _______________________________________________
> > Openembedded-core mailing list
> > Openembedded-core@lists.openembedded.org
> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
^ permalink raw reply
* Re: [PATCH 2/2] tzdata: updated SRC_URI and update to 2011k
From: Joshua Lock @ 2011-10-19 16:19 UTC (permalink / raw)
To: openembedded-core
In-Reply-To: <20111019005411.GB27915@sakrah.homelinux.org>
On 10/18/2011 05:54 PM, Khem Raj wrote:
> On (18/10/11 15:24), Joshua Lock wrote:
>> tzdata is now hosted by IANA at http://www.iana.org/time-zones
>>
>> Signed-off-by: Joshua Lock <josh@linux.intel.com>
>> ---
>> .../tzdata/{tzdata_2011k.bb => tzdata_2011l.bb} | 6 +++---
>> 1 files changed, 3 insertions(+), 3 deletions(-)
>> rename meta/recipes-extended/tzdata/{tzdata_2011k.bb => tzdata_2011l.bb} (96%)
>>
>> diff --git a/meta/recipes-extended/tzdata/tzdata_2011k.bb b/meta/recipes-extended/tzdata/tzdata_2011l.bb
>> similarity index 96%
>> rename from meta/recipes-extended/tzdata/tzdata_2011k.bb
>> rename to meta/recipes-extended/tzdata/tzdata_2011l.bb
>> index 45f2c4d..140f8ed 100644
>> --- a/meta/recipes-extended/tzdata/tzdata_2011k.bb
>> +++ b/meta/recipes-extended/tzdata/tzdata_2011l.bb
>> @@ -12,10 +12,10 @@ RCONFLICTS= "timezones timezone-africa timezone-america timezone-antarctica \
>> timezone-australia timezone-europe timezone-indian \
>> timezone-iso3166.tab timezone-pacific timezone-zone.tab"
>>
>> -SRC_URI = "ftp://elsie.nci.nih.gov/pub/tzdata${PV}.tar.gz;name=tzdata"
>> +SRC_URI = "http://www.iana.org/time-zones/repository/releases/tzdata${PV}.tar.gz;name=tzdata"
>
> I think same would be needed for tzcode-native recipes. Could you also
> do that while you are at it.
I'll try and get to it today.
Joshua
--
Joshua Lock
Yocto Project "Johannes factotum"
Intel Open Source Technology Centre
^ permalink raw reply
* Re: [PATCH 1/2] gst-plugins-good: update to 0.10.30
From: Joshua Lock @ 2011-10-19 16:17 UTC (permalink / raw)
To: openembedded-core
In-Reply-To: <20111019084629.GC3522@jama.jama.net>
On 10/19/2011 01:46 AM, Martin Jansa wrote:
> On Tue, Oct 18, 2011 at 03:24:11PM -0700, Joshua Lock wrote:
>> Signed-off-by: Joshua Lock <josh@linux.intel.com>
>> ---
>> ...good_0.10.28.bb => gst-plugins-good_0.10.30.bb} | 4 ++--
>> 1 files changed, 2 insertions(+), 2 deletions(-)
>> rename meta/recipes-multimedia/gstreamer/{gst-plugins-good_0.10.28.bb => gst-plugins-good_0.10.30.bb} (84%)
>>
>> diff --git a/meta/recipes-multimedia/gstreamer/gst-plugins-good_0.10.28.bb b/meta/recipes-multimedia/gstreamer/gst-plugins-good_0.10.30.bb
>> similarity index 84%
>> rename from meta/recipes-multimedia/gstreamer/gst-plugins-good_0.10.28.bb
>> rename to meta/recipes-multimedia/gstreamer/gst-plugins-good_0.10.30.bb
>> index 6c837a7..96855aa 100644
>> --- a/meta/recipes-multimedia/gstreamer/gst-plugins-good_0.10.28.bb
>> +++ b/meta/recipes-multimedia/gstreamer/gst-plugins-good_0.10.30.bb
>> @@ -18,5 +18,5 @@ do_configure_prepend() {
>> rm ${S}/m4/lib-link.m4 || true
>> }
>>
>> -SRC_URI[md5sum] = "6ef1588921f59d85c44ee2e49a3c97a0"
>> -SRC_URI[sha256sum] = "adfbce68b9fbadb7a7aeda2227af6afe1928ef025af4158726617b9d6834b028"
>> +SRC_URI[md5sum] = "62fd7a3ef187c4f99b3d7c352d58dae9"
>> +SRC_URI[sha256sum] = "b12cba90b27d8423cd0a808939098d19db3996cfb9bf528507c6321782e095f6"
>> --
>> 1.7.6.4
>
> Can you please fix:
> NOTE: Running task 2693 of 2701 (ID: 9, /OE/shr-core/openembedded-core/meta/recipes-multimedia/gstreamer/gst-plugins-good_0.10.30.bb, do_package)
> NOTE: package gst-plugins-good-0.10.30-r2: task do_package: Started
> WARNING: For recipe gst-plugins-good, the following files were installed but not shipped in any package:
> WARNING: /etc/gconf/schemas/gstreamer-0.10.schemas
> NOTE: package gst-plugins-good-0.10.30-r2: task do_package: Succeeded
Sure, I'll take a look now - pretty sure that's not new but thanks for
raising it.
Joshua
--
Joshua Lock
Yocto Project "Johannes factotum"
Intel Open Source Technology Centre
^ permalink raw reply
* Re: [CONSOLIDATED PULL 14/16] distro-tracking: update data for some toolchain recipes
From: Koen Kooi @ 2011-10-19 15:52 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
In-Reply-To: <9DA5872FEF993D41B7173F58FCF6BE94E2F42EE2@orsmsx504.amr.corp.intel.com>
Op 19 okt. 2011, om 17:49 heeft Kamble, Nitin A het volgende geschreven:
> Koen,
> Why do you ask ?
Because I want the commit message to match to commit and now it doesn't.
>
> Nitin
>
>> -----Original Message-----
>> From: openembedded-core-bounces@lists.openembedded.org
>> [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf Of
>> Koen Kooi
>> Sent: Wednesday, October 19, 2011 1:31 AM
>> To: Patches and discussions about the oe-core layer
>> Subject: Re: [OE-core] [CONSOLIDATED PULL 14/16] distro-tracking:
>> update data for some toolchain recipes
>>
>> btrfs-tools is a toolchain recipe?!?!?!
>>
>>
>>
>> Op 19 okt. 2011, om 10:28 heeft Saul Wold het volgende geschreven:
>>
>>> From: Nitin A Kamble <nitin.a.kamble@intel.com>
>>>
>>> Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
>>> ---
>>> .../conf/distro/include/distro_tracking_fields.inc | 42
>> ++++++++++++--------
>>> 1 files changed, 25 insertions(+), 17 deletions(-)
>>>
>>> diff --git a/meta/conf/distro/include/distro_tracking_fields.inc
>> b/meta/conf/distro/include/distro_tracking_fields.inc
>>> index abc2cbf..e68bbe1 100644
>>> --- a/meta/conf/distro/include/distro_tracking_fields.inc
>>> +++ b/meta/conf/distro/include/distro_tracking_fields.inc
>>> @@ -3005,11 +3005,19 @@ RECIPE_STATUS_pn-run-postinsts="green" # all
>> local code
>>> RECIPE_LATEST_VERSION_pn-postinsts="1.0"
>>> RECIPE_MAINTAINER_pn-postinsts = "Nitin A Kamble
>> <nitin.a.kamble@intel.com>"
>>>
>>> -RECIPE_STATUS_pn-nasm="green"
>>> +RECIPE_STATUS_pn-nasm="green"
>>> RECIPE_LATEST_VERSION_pn-nasm="2.07"
>>> -RECIPE_MANUAL_CHECK_DATE_pn-nasm = "Jul 06, 2011"
>>> +RECIPE_MANUAL_CHECK_DATE_pn-nasm = "Oct 18, 2011"
>>> +RECIPE_LAST_UPDATE_pn-nasm = "Jun 23, 2010"
>>> RECIPE_MAINTAINER_pn-nasm = "Nitin A Kamble
>> <nitin.a.kamble@intel.com>"
>>>
>>> +RECIPE_STATUS_pn-btrfs-tools="green"
>>> +RECIPE_LATEST_VERSION_pn-btrfs-tools="git"
>>> +RECIPE_MANUAL_CHECK_DATE_pn-btrfs-tools = "Oct 18, 2011"
>>> +RECIPE_LAST_UPDATE_pn-btrfs-tools = "Jun 09, 2011"
>>> +RECIPE_MAINTAINER_pn-btrfs-tools = "Nitin A Kamble
>> <nitin.a.kamble@intel.com>"
>>> +DISTRO_PN_ALIAS_pn-btrfs-tools = "Debian=btrfs-tools Fedora=btrfs-
>> progs"
>>> +
>>> RECIPE_STATUS_pn-perl="red" # upgrade needed
>>> RECIPE_LATEST_VERSION_pn-perl="5.12.1"
>>> RECIPE_LAST_UPDATE_pn-perl = "May 27, 2007"
>>> @@ -3020,9 +3028,9 @@ RECIPE_LATEST_VERSION_pn-
>> prelink="1.0+git0+0x909470ee441237563d6236c505cb2d02ddc
>>> RECIPE_LAST_UPDATE_pn-perl = "Jul 23, 2010"
>>> RECIPE_MAINTAINER_pn-prelink = "Mark Hatle
>> <mark.hatle@windriver.com>"
>>>
>>> -RECIPE_STATUS_pn-python-dbus="red"
>>> -RECIPE_LATEST_VERSION_pn-python-dbus="0.83.1"
>>> -RECIPE_LAST_UPDATE_pn-python-dbus = "Jul 7, 2010"
>>> +RECIPE_STATUS_pn-python-dbus="green"
>>> +RECIPE_LATEST_VERSION_pn-python-dbus="0.84.0"
>>> +RECIPE_LAST_UPDATE_pn-python-dbus = "Oct 18, 2011"
>>> RECIPE_MAINTAINER_pn-python-dbus = "Nitin A Kamble
>> <nitin.a.kamble@intel.com>"
>>> DISTRO_PN_ALIAS_pn-python-dbus = "Ubuntu=python-dbus Debian=python-
>> dbus Mandriva=python-dbus"
>>>
>>> @@ -3062,7 +3070,8 @@ RECIPE_MAINTAINER_pn-python-pyrex = "Nitin A
>> Kamble <nitin.a.kamble@intel.com>"
>>> DISTRO_PN_ALIAS_pn-python-pyrex = "Mandriva=python-pyrex
>> Ubuntu=python-pyrex"
>>>
>>> RECIPE_STATUS_pn-python-scons="green"
>>> -RECIPE_LATEST_VERSION_pn-python-scons="2.0.1"
>>> +RECIPE_LATEST_VERSION_pn-python-scons="2.1.0"
>>> +RECIPE_LAST_UPDATE_pn-python-scons = "Oct 18, 2011"
>>> DISTRO_PN_ALIAS_pn-python-scons = "Fedora=scons OpenSuSE=scons
>> Ubuntu=scons Mandriva=scons Debian=scons"
>>> RECIPE_LAST_UPDATE_pn-python-scons = "Nov 8, 2010"
>>> RECIPE_MAINTAINER_pn-python-scons = "Nitin A Kamble
>> <nitin.a.kamble@intel.com>"
>>> @@ -3087,15 +3096,16 @@ RECIPE_LATEST_VERSION_pn-unifdef="2.6.18+git"
>>> RECIPE_MAINTAINER_pn-unifdef = "Nitin A Kamble
>> <nitin.a.kamble@intel.com>"
>>>
>>> RECIPE_STATUS_pn-gnu-config="green"
>>> -RECIPE_LATEST_VERSION_pn-gnu-config="0.0+git3155524"
>>> +RECIPE_LATEST_VERSION_pn-gnu-config="svn"
>>> DISTRO_PN_ALIAS_pn-gnu-config = "OpenedHand"
>>> RECIPE_LAST_UPDATE_pn-gnu-config = "Jun 21, 2010"
>>> -RECIPE_MANUAL_CHECK_DATE_pn-gnu-config = "Jul 06, 2011"
>>> +RECIPE_MANUAL_CHECK_DATE_pn-gnu-config = "Oct 18, 2011"
>>> RECIPE_MAINTAINER_pn-gnu-config = "Nitin A Kamble
>> <nitin.a.kamble@intel.com>"
>>>
>>> RECIPE_STATUS_pn-mpfr="green"
>>> -RECIPE_LATEST_VERSION_pn-mpfr="3.0.0"
>>> -RECIPE_MANUAL_CHECK_DATE_pn-mpfr = "Jul 06, 2011"
>>> +RECIPE_LATEST_VERSION_pn-mpfr="3.0.1"
>>> +RECIPE_MANUAL_CHECK_DATE_pn-mpfr = "Oct 18, 2011"
>>> +RECIPE_LAST_UPDATE_pn-mpfr = "Apr 07, 2011"
>>> RECIPE_MAINTAINER_pn-mpfr = "Nitin A Kamble
>> <nitin.a.kamble@intel.com>"
>>>
>>> RECIPE_STATUS_pn-gmp="green"
>>> @@ -3110,9 +3120,10 @@ RECIPE_MANUAL_CHECK_DATE_pn-libmpc = "Jan 25,
>> 2011"
>>> RECIPE_MAINTAINER_pn-libmpc = "Nitin A Kamble
>> <nitin.a.kamble@intel.com>"
>>> DISTRO_PN_ALIAS_pn-libmpc = "Fedora=libmpc OpenSuse=libmpc2"
>>>
>>> -RECIPE_STATUS_pn-byacc="red"
>>> +RECIPE_STATUS_pn-byacc="green"
>>> RECIPE_LATEST_VERSION_pn-byacc="20101229"
>>> -RECIPE_MANUAL_CHECK_DATE_pn-byacc = "Jul 06, 2011"
>>> +RECIPE_MANUAL_CHECK_DATE_pn-byacc = "Oct 18, 2011"
>>> +RECIPE_LAST_UPDATE_pn-byacc = "Oct 18, 2010"
>>> RECIPE_MAINTAINER_pn-byacc = "Nitin A Kamble
>> <nitin.a.kamble@intel.com>"
>>>
>>> RECIPE_STATUS_pn-libconvert-asn1-perl="green"
>>> @@ -3122,8 +3133,8 @@ RECIPE_LAST_UPDATE_pn-libconvert-asn1-perl =
>> "Aug 13, 2010"
>>> RECIPE_MAINTAINER_pn-libconvert-asn1-perl = "Nitin A Kamble
>> <nitin.a.kamble@intel.com>"
>>>
>>> RECIPE_STATUS_pn-libxml-parser-perl="green"
>>> -RECIPE_LATEST_VERSION_pn-libxml-parser-perl="2.36"
>>> -RECIPE_LAST_UPDATE_pn-libxml-parser-perl = "Nov 18, 2009"
>>> +RECIPE_LATEST_VERSION_pn-libxml-parser-perl="2.41"
>>> +RECIPE_LAST_UPDATE_pn-libxml-parser-perl = "Oct 18, 2011"
>>> RECIPE_MAINTAINER_pn-libxml-parser-perl = "Nitin A Kamble
>> <nitin.a.kamble@intel.com>"
>>>
>>> RECIPE_STATUS_pn-cmake-native="green"
>>> @@ -5922,9 +5933,6 @@ RECIPE_COMMENTS_pn-pseudo = "Yocto Project
>> maintained"
>>> RECIPE_MANUAL_CHECK_DATE_pn-pseudo = "Jun 06, 2011"
>>> DISTRO_PN_ALIAS_pn-pseudo = "Windriver"
>>>
>>> -DISTRO_PN_ALIAS_pn-btrfs-tools = "Debian=btrfs-tools Fedora=btrfs-
>> progs"
>>> -RECIPE_MAINTAINER_pn-btrfs-tools = "Nitin A Kamble
>> <nitin.a.kamble@intel.com>"
>>> -
>>> DISTRO_PN_ALIAS_pn-rt-tests = "Debian=rt-tests Ubuntu=rt-tests"
>>> RECIPE_MAINTAINER_pn-rt-tests = "Darren Hart
>> <dvhart@linux.intel.com>"
>>>
>>> --
>>> 1.7.6.2
>>>
>>>
>>> _______________________________________________
>>> Openembedded-core mailing list
>>> Openembedded-core@lists.openembedded.org
>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
^ permalink raw reply
* Re: [CONSOLIDATED PULL 14/16] distro-tracking: update data for some toolchain recipes
From: Kamble, Nitin A @ 2011-10-19 15:49 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
In-Reply-To: <758B37BA-B417-4B39-BF1C-0CEC613F067D@dominion.thruhere.net>
Koen,
Why do you ask ?
Nitin
> -----Original Message-----
> From: openembedded-core-bounces@lists.openembedded.org
> [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf Of
> Koen Kooi
> Sent: Wednesday, October 19, 2011 1:31 AM
> To: Patches and discussions about the oe-core layer
> Subject: Re: [OE-core] [CONSOLIDATED PULL 14/16] distro-tracking:
> update data for some toolchain recipes
>
> btrfs-tools is a toolchain recipe?!?!?!
>
>
>
> Op 19 okt. 2011, om 10:28 heeft Saul Wold het volgende geschreven:
>
> > From: Nitin A Kamble <nitin.a.kamble@intel.com>
> >
> > Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
> > ---
> > .../conf/distro/include/distro_tracking_fields.inc | 42
> ++++++++++++--------
> > 1 files changed, 25 insertions(+), 17 deletions(-)
> >
> > diff --git a/meta/conf/distro/include/distro_tracking_fields.inc
> b/meta/conf/distro/include/distro_tracking_fields.inc
> > index abc2cbf..e68bbe1 100644
> > --- a/meta/conf/distro/include/distro_tracking_fields.inc
> > +++ b/meta/conf/distro/include/distro_tracking_fields.inc
> > @@ -3005,11 +3005,19 @@ RECIPE_STATUS_pn-run-postinsts="green" # all
> local code
> > RECIPE_LATEST_VERSION_pn-postinsts="1.0"
> > RECIPE_MAINTAINER_pn-postinsts = "Nitin A Kamble
> <nitin.a.kamble@intel.com>"
> >
> > -RECIPE_STATUS_pn-nasm="green"
> > +RECIPE_STATUS_pn-nasm="green"
> > RECIPE_LATEST_VERSION_pn-nasm="2.07"
> > -RECIPE_MANUAL_CHECK_DATE_pn-nasm = "Jul 06, 2011"
> > +RECIPE_MANUAL_CHECK_DATE_pn-nasm = "Oct 18, 2011"
> > +RECIPE_LAST_UPDATE_pn-nasm = "Jun 23, 2010"
> > RECIPE_MAINTAINER_pn-nasm = "Nitin A Kamble
> <nitin.a.kamble@intel.com>"
> >
> > +RECIPE_STATUS_pn-btrfs-tools="green"
> > +RECIPE_LATEST_VERSION_pn-btrfs-tools="git"
> > +RECIPE_MANUAL_CHECK_DATE_pn-btrfs-tools = "Oct 18, 2011"
> > +RECIPE_LAST_UPDATE_pn-btrfs-tools = "Jun 09, 2011"
> > +RECIPE_MAINTAINER_pn-btrfs-tools = "Nitin A Kamble
> <nitin.a.kamble@intel.com>"
> > +DISTRO_PN_ALIAS_pn-btrfs-tools = "Debian=btrfs-tools Fedora=btrfs-
> progs"
> > +
> > RECIPE_STATUS_pn-perl="red" # upgrade needed
> > RECIPE_LATEST_VERSION_pn-perl="5.12.1"
> > RECIPE_LAST_UPDATE_pn-perl = "May 27, 2007"
> > @@ -3020,9 +3028,9 @@ RECIPE_LATEST_VERSION_pn-
> prelink="1.0+git0+0x909470ee441237563d6236c505cb2d02ddc
> > RECIPE_LAST_UPDATE_pn-perl = "Jul 23, 2010"
> > RECIPE_MAINTAINER_pn-prelink = "Mark Hatle
> <mark.hatle@windriver.com>"
> >
> > -RECIPE_STATUS_pn-python-dbus="red"
> > -RECIPE_LATEST_VERSION_pn-python-dbus="0.83.1"
> > -RECIPE_LAST_UPDATE_pn-python-dbus = "Jul 7, 2010"
> > +RECIPE_STATUS_pn-python-dbus="green"
> > +RECIPE_LATEST_VERSION_pn-python-dbus="0.84.0"
> > +RECIPE_LAST_UPDATE_pn-python-dbus = "Oct 18, 2011"
> > RECIPE_MAINTAINER_pn-python-dbus = "Nitin A Kamble
> <nitin.a.kamble@intel.com>"
> > DISTRO_PN_ALIAS_pn-python-dbus = "Ubuntu=python-dbus Debian=python-
> dbus Mandriva=python-dbus"
> >
> > @@ -3062,7 +3070,8 @@ RECIPE_MAINTAINER_pn-python-pyrex = "Nitin A
> Kamble <nitin.a.kamble@intel.com>"
> > DISTRO_PN_ALIAS_pn-python-pyrex = "Mandriva=python-pyrex
> Ubuntu=python-pyrex"
> >
> > RECIPE_STATUS_pn-python-scons="green"
> > -RECIPE_LATEST_VERSION_pn-python-scons="2.0.1"
> > +RECIPE_LATEST_VERSION_pn-python-scons="2.1.0"
> > +RECIPE_LAST_UPDATE_pn-python-scons = "Oct 18, 2011"
> > DISTRO_PN_ALIAS_pn-python-scons = "Fedora=scons OpenSuSE=scons
> Ubuntu=scons Mandriva=scons Debian=scons"
> > RECIPE_LAST_UPDATE_pn-python-scons = "Nov 8, 2010"
> > RECIPE_MAINTAINER_pn-python-scons = "Nitin A Kamble
> <nitin.a.kamble@intel.com>"
> > @@ -3087,15 +3096,16 @@ RECIPE_LATEST_VERSION_pn-unifdef="2.6.18+git"
> > RECIPE_MAINTAINER_pn-unifdef = "Nitin A Kamble
> <nitin.a.kamble@intel.com>"
> >
> > RECIPE_STATUS_pn-gnu-config="green"
> > -RECIPE_LATEST_VERSION_pn-gnu-config="0.0+git3155524"
> > +RECIPE_LATEST_VERSION_pn-gnu-config="svn"
> > DISTRO_PN_ALIAS_pn-gnu-config = "OpenedHand"
> > RECIPE_LAST_UPDATE_pn-gnu-config = "Jun 21, 2010"
> > -RECIPE_MANUAL_CHECK_DATE_pn-gnu-config = "Jul 06, 2011"
> > +RECIPE_MANUAL_CHECK_DATE_pn-gnu-config = "Oct 18, 2011"
> > RECIPE_MAINTAINER_pn-gnu-config = "Nitin A Kamble
> <nitin.a.kamble@intel.com>"
> >
> > RECIPE_STATUS_pn-mpfr="green"
> > -RECIPE_LATEST_VERSION_pn-mpfr="3.0.0"
> > -RECIPE_MANUAL_CHECK_DATE_pn-mpfr = "Jul 06, 2011"
> > +RECIPE_LATEST_VERSION_pn-mpfr="3.0.1"
> > +RECIPE_MANUAL_CHECK_DATE_pn-mpfr = "Oct 18, 2011"
> > +RECIPE_LAST_UPDATE_pn-mpfr = "Apr 07, 2011"
> > RECIPE_MAINTAINER_pn-mpfr = "Nitin A Kamble
> <nitin.a.kamble@intel.com>"
> >
> > RECIPE_STATUS_pn-gmp="green"
> > @@ -3110,9 +3120,10 @@ RECIPE_MANUAL_CHECK_DATE_pn-libmpc = "Jan 25,
> 2011"
> > RECIPE_MAINTAINER_pn-libmpc = "Nitin A Kamble
> <nitin.a.kamble@intel.com>"
> > DISTRO_PN_ALIAS_pn-libmpc = "Fedora=libmpc OpenSuse=libmpc2"
> >
> > -RECIPE_STATUS_pn-byacc="red"
> > +RECIPE_STATUS_pn-byacc="green"
> > RECIPE_LATEST_VERSION_pn-byacc="20101229"
> > -RECIPE_MANUAL_CHECK_DATE_pn-byacc = "Jul 06, 2011"
> > +RECIPE_MANUAL_CHECK_DATE_pn-byacc = "Oct 18, 2011"
> > +RECIPE_LAST_UPDATE_pn-byacc = "Oct 18, 2010"
> > RECIPE_MAINTAINER_pn-byacc = "Nitin A Kamble
> <nitin.a.kamble@intel.com>"
> >
> > RECIPE_STATUS_pn-libconvert-asn1-perl="green"
> > @@ -3122,8 +3133,8 @@ RECIPE_LAST_UPDATE_pn-libconvert-asn1-perl =
> "Aug 13, 2010"
> > RECIPE_MAINTAINER_pn-libconvert-asn1-perl = "Nitin A Kamble
> <nitin.a.kamble@intel.com>"
> >
> > RECIPE_STATUS_pn-libxml-parser-perl="green"
> > -RECIPE_LATEST_VERSION_pn-libxml-parser-perl="2.36"
> > -RECIPE_LAST_UPDATE_pn-libxml-parser-perl = "Nov 18, 2009"
> > +RECIPE_LATEST_VERSION_pn-libxml-parser-perl="2.41"
> > +RECIPE_LAST_UPDATE_pn-libxml-parser-perl = "Oct 18, 2011"
> > RECIPE_MAINTAINER_pn-libxml-parser-perl = "Nitin A Kamble
> <nitin.a.kamble@intel.com>"
> >
> > RECIPE_STATUS_pn-cmake-native="green"
> > @@ -5922,9 +5933,6 @@ RECIPE_COMMENTS_pn-pseudo = "Yocto Project
> maintained"
> > RECIPE_MANUAL_CHECK_DATE_pn-pseudo = "Jun 06, 2011"
> > DISTRO_PN_ALIAS_pn-pseudo = "Windriver"
> >
> > -DISTRO_PN_ALIAS_pn-btrfs-tools = "Debian=btrfs-tools Fedora=btrfs-
> progs"
> > -RECIPE_MAINTAINER_pn-btrfs-tools = "Nitin A Kamble
> <nitin.a.kamble@intel.com>"
> > -
> > DISTRO_PN_ALIAS_pn-rt-tests = "Debian=rt-tests Ubuntu=rt-tests"
> > RECIPE_MAINTAINER_pn-rt-tests = "Darren Hart
> <dvhart@linux.intel.com>"
> >
> > --
> > 1.7.6.2
> >
> >
> > _______________________________________________
> > Openembedded-core mailing list
> > Openembedded-core@lists.openembedded.org
> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
^ permalink raw reply
* [PATCH] squashfs-tools: add recipe (2nd try)
From: Cliff Brake @ 2011-10-19 12:43 UTC (permalink / raw)
To: openembedded-core; +Cc: Cliff Brake
From: Cliff Brake <cbrake@bec-systems.com>
added xz compression option, general cleanup
---
.../squashfs-tools/squashfs-tools_4.2.bb | 38 ++++++++++++++++++++
1 files changed, 38 insertions(+), 0 deletions(-)
create mode 100644 meta/recipes-devtools/squashfs-tools/squashfs-tools_4.2.bb
diff --git a/meta/recipes-devtools/squashfs-tools/squashfs-tools_4.2.bb b/meta/recipes-devtools/squashfs-tools/squashfs-tools_4.2.bb
new file mode 100644
index 0000000..3a9f12a
--- /dev/null
+++ b/meta/recipes-devtools/squashfs-tools/squashfs-tools_4.2.bb
@@ -0,0 +1,38 @@
+# Note, we can probably remove the lzma option as it has be replaced with xz,
+# and I don't think the kernel supports it any more.
+DESCRIPTION = "Squashfs is a highly compressed read-only filesystem for Linux."
+SECTION = "base"
+LICENSE = "GPLv2 & Public Domain"
+LIC_FILES_CHKSUM = "file://../COPYING;md5=0636e73ff0215e8d672dc4c32c317bb3 \
+ file://../../7zC.txt;beginline=12;endline=16;md5=2056cd6d919ebc3807602143c7449a7c \
+ "
+DEPENDS = "attr zlib xz"
+PR = "0"
+
+SRC_URI = "${SOURCEFORGE_MIRROR}/squashfs/squashfs${PV}.tar.gz;name=squashfs \
+ http://downloads.sourceforge.net/sevenzip/lzma465.tar.bz2;name=lzma \
+ "
+SRC_URI[squashfs.md5sum] = "1b7a781fb4cf8938842279bd3e8ee852"
+SRC_URI[squashfs.sha256sum] = "d9e0195aa922dbb665ed322b9aaa96e04a476ee650f39bbeadb0d00b24022e96"
+SRC_URI[lzma.md5sum] = "29d5ffd03a5a3e51aef6a74e9eafb759"
+SRC_URI[lzma.sha256sum] = "c935fd04dd8e0e8c688a3078f3675d699679a90be81c12686837e0880aa0fa1e"
+
+S = "${WORKDIR}/squashfs${PV}/squashfs-tools"
+
+# EXTRA_OEMAKE is typically: -e MAKEFLAGS=
+# the -e causes problems as CFLAGS is modified in the Makefile, so
+# we redefine EXTRA_OEMAKE here
+EXTRA_OEMAKE = "MAKEFLAGS= LZMA_SUPPORT=1 LZMA_DIR=../.. XZ_SUPPORT=1"
+
+do_compile() {
+ oe_runmake mksquashfs
+}
+do_install () {
+ install -d ${D}${sbindir}
+ install -m 0755 mksquashfs ${D}${sbindir}/
+}
+
+# required to share same place with -lzma specific packages
+FILESPATHPKG =. "squashfs-tools-${PV}:"
+
+BBCLASSEXTEND = "native"
--
1.7.1
^ permalink raw reply related
* Re: [PATCH 1/1] module.bbclass: add lock to prevent error bulding ext modules
From: Anders Darander @ 2011-10-19 11:55 UTC (permalink / raw)
To: openembedded-core
In-Reply-To: <3D79364E-4D29-49B8-B196-4E1FBD4E82FE@dominion.thruhere.net>
* Koen Kooi <koen@dominion.thruhere.net> [111019 13:38]:
> Op 19 okt. 2011, om 13:15 heeft Anders Darander het volgende geschreven:
> > When external modules are built, files in $STAGING_KERNEL_DIR/scripts/basic will/can get
> > rebuilt.
> > This raises a potential race condition. Prevent this by adding a lock around the
> > do_make_scripts() function. Further, make sure that the kernel has been installed
> > to the sysroot, prior to executing this new task.
> So what do external module recipe that aren't using do_compile from
> module.bbclass need to change to keep working?
I haven't tried any, do you know any widely available ones that I could
check?
If they aren't using the do_compile from module.bbclass, are they
inheriting module.bbclass anyway? If they aren't inheriting
module.bbclass, then they shouldn't be affected.
If they inherit module.bbclass, than I guess that we should remove the
call to do_make_scripts from their do_compile. _But_ this is untested,
as I've got no such recipe (that I'm aware of). If my assumptions hold,
we should probably rephrase the comment regarding do_make_scripts.
Cheers,
Anders
--
Anders Darander
ChargeStorm AB / eStorm AB
^ permalink raw reply
* Re: [PATCH 1/1] module.bbclass: add lock to prevent error bulding ext modules
From: Koen Kooi @ 2011-10-19 11:38 UTC (permalink / raw)
To: Patches and discussions about the oe-core layer
In-Reply-To: <40dcebe98e97bb4fabfec74e9e7acb59548da091.1319022793.git.anders@chargestorm.se>
Op 19 okt. 2011, om 13:15 heeft Anders Darander het volgende geschreven:
> When external modules are built, files in $STAGING_KERNEL_DIR/scripts/basic will/can get
> rebuilt.
> This raises a potential race condition. Prevent this by adding a lock around the
> do_make_scripts() function. Further, make sure that the kernel has been installed
> to the sysroot, prior to executing this new task.
So what do external module recipe that aren't using do_compile from module.bbclass need to change to keep working?
^ permalink raw reply
* [PATCH 1/1] module.bbclass: add lock to prevent error bulding ext modules
From: Anders Darander @ 2011-10-19 11:15 UTC (permalink / raw)
To: openembedded-core
In-Reply-To: <cover.1319022793.git.anders@chargestorm.se>
When external modules are built, files in $STAGING_KERNEL_DIR/scripts/basic will/can get
rebuilt.
This raises a potential race condition. Prevent this by adding a lock around the
do_make_scripts() function. Further, make sure that the kernel has been installed
to the sysroot, prior to executing this new task.
Signed-off-by: Anders Darander <anders@chargestorm.se>
---
meta/classes/module.bbclass | 5 ++++-
1 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/meta/classes/module.bbclass b/meta/classes/module.bbclass
index 572df0d..53c16b7 100644
--- a/meta/classes/module.bbclass
+++ b/meta/classes/module.bbclass
@@ -14,8 +14,11 @@ do_make_scripts() {
-C ${STAGING_KERNEL_DIR} scripts
}
+addtask make_scripts before do_compile
+do_make_scripts[lockfiles] = "${TMPDIR}/kernel-scripts.lock"
+do_make_scripts[deptask] = "do_populate_sysroot"
+
module_do_compile() {
- do_make_scripts
unset CFLAGS CPPFLAGS CXXFLAGS LDFLAGS
oe_runmake KERNEL_PATH=${STAGING_KERNEL_DIR} \
KERNEL_SRC=${STAGING_KERNEL_DIR} \
--
1.7.7
^ permalink raw reply related
* [PATCH 0/1] Fix race while building external modules
From: Anders Darander @ 2011-10-19 11:14 UTC (permalink / raw)
To: openembedded-core; +Cc: Anders Darander
When building an image with several external modules, a race is likely to
occur. This race is when building scripts in the staged kernel tree (sysroot).
To prevent this, we promote the do_make_scripts() function to a task, which we
protect by a lock. Tip on how to make this work was received by Richard in
[1]. To avoid new problems, introduced by this promotion, we make this new
task depend on do_populate_sysroot from the modules dependencies
(i.e. virtual/kernel).
This patch has been extensively tested on the 2011-1 release branch, on a
custom ARM-machine and distro with several external modules.
[1] http://lists.linuxtogo.org/pipermail/openembedded-core/2011-October/011163.html
The following changes since commit e31dd9b65f3b03f79cabab25eca157532de3bd9c:
fontconfig: fix fix-pkgconfig.patch (2011-10-18 18:13:47 +0100)
are available in the git repository at:
git://github.com/darander/oe-core ext-mod-race
https://github.com/darander/oe-core/tree/ext-mod-race
Anders Darander (1):
module.bbclass: add lock to prevent error bulding ext modules
meta/classes/module.bbclass | 5 ++++-
1 files changed, 4 insertions(+), 1 deletions(-)
--
1.7.7
^ permalink raw reply
* Re: [PATCH 1/2] qmmp: update to 0.5.2
From: Xiaofeng Yan @ 2011-10-19 10:31 UTC (permalink / raw)
To: openembedded-core
In-Reply-To: <4E9D123F.6090102@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 5137 bytes --]
On 2011年10月18日 13:44, Xiaofeng Yan wrote:
> On 2011年10月18日 13:35, Saul Wold wrote:
>> On 10/17/2011 10:21 PM, Xiaofeng Yan wrote:
>>> From: Xiaofeng Yan<xiaofeng.yan@windriver.com>
>>>
>>> The new version of qmmp can run on core-image-sato by test.
>>> $qmmp *.mp3
>>>
>>> Signed-off-by: Xiaofeng Yan<xiaofeng.yan@windriver.com>
>>> ---
>>> meta/recipes-qt/qt-apps/qmmp_0.5.2.bb | 49
>>> +++++++++++++++++++++++++++++++++
>>> 1 files changed, 49 insertions(+), 0 deletions(-)
>>> create mode 100644 meta/recipes-qt/qt-apps/qmmp_0.5.2.bb
>>>
>>> diff --git a/meta/recipes-qt/qt-apps/qmmp_0.5.2.bb
>>> b/meta/recipes-qt/qt-apps/qmmp_0.5.2.bb
>>> new file mode 100644
>>> index 0000000..f31409b
>>> --- /dev/null
>>> +++ b/meta/recipes-qt/qt-apps/qmmp_0.5.2.bb
>>> @@ -0,0 +1,49 @@
>>> +dESCRIPTION = "Qmmp (Qt-based Multimedia Player) is an
>>> audio-player, written with help of Qt library"
>>> +HOMEPAGE = "http://qmmp.ylsoftware.com"
>>> +LICENSE = "GPLv2"
>>> +LIC_FILES_CHKSUM =
>>> "file://COPYING;md5=393a5ca445f6965873eca0259a17f833"
>>> +SECTION = "multimedia"
>>> +
>>> +PR = "r3"
>>> +
>>> +PROVIDES = "qmmp"
>>> +DEPENDS = "qt4-x11-free taglib libmad libvorbis libogg alsa-lib"
>>> +RDEPENDS_${PN} += "taglib alsa-lib libmad curl"
>>> +
>>> +SRC_URI = "http://qmmp.ylsoftware.com/files/${BPN}-${PV}.tar.bz2"
>>> +
>>> +SRC_URI[md5sum] = "20852f3cce3471bfc5affa9b2e947dc6"
>>> +SRC_URI[sha256sum] =
>>> "6391dec020d2a381d7f4b7890fae6c49eadf88b3c9aef571fe3c5e96140822ec"
>>> +
>>> +
>>> +PARALLEL_MAKE = ""
>>> +
>>> +inherit qmake2 cmake
>>> +
>>> +export EXTRA_OECMAKE = "-DQT_QMAKE_EXECUTABLE=${OE_QMAKE_QMAKE} \
>>> + -DQT_LRELEASE_EXECUTABLE=${OE_QMAKE_LRELEASE} \
>>> + -DQT_MOC_EXECUTABLE=${OE_QMAKE_MOC} \
>>> + -DQT_UIC_EXECUTABLE=${OE_QMAKE_UIC} \
>>> + -DQT_RCC_EXECUTABLE=${OE_QMAKE_RCC} \
>>> + -DQT_LIBRARY_DIR=${OE_QMAKE_LIBDIR_QT} \
>>> + -DQT_HEADERS_DIR=${OE_QMAKE_INCDIR_QT} \
>>> + -DQT_QTCORE_INCLUDE_DIR=${OE_QMAKE_INCDIR_QT}/QtCore \
>>> + "
>>> +
>>> +FILES_${PN} =+ "\
>>> + ${libdir}/qmmp/*/*.so \
>>> + ${datadir}/icons/* \
>>> + ${datadir}/qmmp/images/* \
>>> + ${datadir}/applications/qmmp.desktop \
>>> + "
>>> +
>> Xiaofeng,
>>
>> I was looking into this also, I think it would be better to split all
>> the various plugins into separate packages using do_split_packages(), in
>> the packages.bbclass.
>>
>> I started with this code:
>>> PACKAGES_DYNAMIC = "qmmp-plugin-*"
>>>
>>> python populate_packages_prepend () {
>>> qmmp_libdir = bb.data.expand('${libdir}/qmmp', d)
>>>
>>> do_split_packages(d, qmmp_libdir, '^(.*)/(.*)\.so$',
>>> 'qmmp-plugin-%s-%s', 'Qmmp %s Plugin for %s', extra_depends='')
>>> }
>>
>> But have not completed it yet, if you have time to investigate
>> further and complete this correctly, there might be a problem with
>> using multiple Regular expressions in the do_split_packages code, but
>> I have not fully debugged this yet.
>>
>> Please let me know if you can complete this task.
>>
Hi saul,
The following is my modification to qmmp_0.5.2.bb. Please review it.
I want to get a reply about how to ship files in ${datadir} for qmmp. I
shipped them to FILES_${PN} because qmmp need these files when starting
up. Do you think that they should be packaged like qmmp-plugin-* ?
Please give me your suggestion and I will modify this file.
PACKAGES_DYNAMIC += "qmmp-plugin-*"
python populate_packages_prepend () {
qmmp_libdir = bb.data.expand('${libdir}/qmmp', d)
do_split_packages(d, qmmp_libdir, '^lib(.*)\.so$',
'qmmp-plugin-%s', 'Qmmp %s Plugin for', recursive=True,extra_depends='')
}
FILES_${PN} = "\
${bindir}/qmmp \
${libdir}/lib*${SOLIBS} \
${datadir}/icons/* \
${datadir}/qmmp/images/* \
${datadir}/applications/* \
"
FILES_${PN}-dbg += "\
${libdir}/qmmp/*/.debug/* \
"
PACKAGES += "${PN}-plugin-input-mad ${PN}-plugin-input-vorbis "
FILES_${PN}-plugin-input-mad = "${libdir}/qmmp/Input/libmad.so"
RDEPENDS_${PN}-plugin-input-mad = "libmad"
FILES_${PN}-plugin-input-vorbis = "${libdir}/qmmp/Input/libvorbis.so"
RDEPENDS_${PN}-plugin-input-vorbis = "libvorbis libogg"
Thanks
Yan
> Thanks for your reply and I will investigate it according to your
> suggestion.
>
> Thanks
> Yan
>> Thanks
>> Sau!
>>
>>
>>> +FILES_${PN}-dbg += "\
>>> + ${libdir}/qmmp/*/.debug/* \
>>> + "
>>> +
>>> +PACKAGES += "${PN}-plugin-input-mad ${PN}-plugin-input-vorbis"
>>> +
>>> +FILES_${PN}-plugin-input-mad = "${libdir}/qmmp/Input/libmad.so"
>>> +RDEPENDS_${PN}-plugin-input-mad = "libmad"
>>> +FILES_${PN}-plugin-input-vorbis = "${libdir}/qmmp/Input/libvorbis.so"
>>> +RDEPENDS_${PN}-plugin-input-vorbis = "libvorbis libogg"
>>
>>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
[-- Attachment #2: Type: text/html, Size: 9072 bytes --]
^ permalink raw reply
* [PATCH 0/2] Update packages
From: wenzong.fan @ 2011-10-19 8:53 UTC (permalink / raw)
To: openembedded-core
From: Wenzong Fan <wenzong.fan@windriver.com>
Update ccache/chkconfig to latest version.
The following changes since commit b4757833c3548b5ee3a1cce58e2f059b3f63cb09:
Martin Jansa (1):
fontconfig: fix fix-pkgconfig.patch
are available in the git repository at:
git://git.pokylinux.org/poky-contrib wenzong/update_pkgs
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=wenzong/update_pkgs
Wenzong Fan (2):
ccache: update to 3.1.6
chkconfig: Update to 1.3.55
.../ccache/{ccache_3.1.5.bb => ccache_3.1.6.bb} | 4 ++--
.../{chkconfig_1.3.52.bb => chkconfig_1.3.55.bb} | 6 +++---
2 files changed, 5 insertions(+), 5 deletions(-)
rename meta/recipes-devtools/ccache/{ccache_3.1.5.bb => ccache_3.1.6.bb} (47%)
rename meta/recipes-extended/chkconfig/{chkconfig_1.3.52.bb => chkconfig_1.3.55.bb} (83%)
^ permalink raw reply
* [PATCH 2/2] chkconfig: Update to 1.3.55
From: wenzong.fan @ 2011-10-19 8:53 UTC (permalink / raw)
To: openembedded-core
In-Reply-To: <cover.1319012299.git.wenzong.fan@windriver.com>
From: Wenzong Fan <wenzong.fan@windriver.com>
Update chkconfig to 1.3.55 from 1.3.52.
Signed-off-by: Wenzong Fan <wenzong.fan@windriver.com>
---
.../{chkconfig_1.3.52.bb => chkconfig_1.3.55.bb} | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
rename meta/recipes-extended/chkconfig/{chkconfig_1.3.52.bb => chkconfig_1.3.55.bb} (83%)
diff --git a/meta/recipes-extended/chkconfig/chkconfig_1.3.52.bb b/meta/recipes-extended/chkconfig/chkconfig_1.3.55.bb
similarity index 83%
rename from meta/recipes-extended/chkconfig/chkconfig_1.3.52.bb
rename to meta/recipes-extended/chkconfig/chkconfig_1.3.55.bb
index 6dc8a0e..0e50936 100644
--- a/meta/recipes-extended/chkconfig/chkconfig_1.3.52.bb
+++ b/meta/recipes-extended/chkconfig/chkconfig_1.3.55.bb
@@ -12,12 +12,12 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=5574c6965ae5f583e55880e397fbb018"
DEPENDS = "libnewt popt"
-PR = "r1"
+PR = "r0"
SRC_URI = "http://fedorahosted.org/releases/c/h/chkconfig/${BPN}-${PV}.tar.bz2"
-SRC_URI[md5sum] = "a576808a6d66763606d750ec451bab6d"
-SRC_URI[sha256sum] = "aa36bf7fd3f7c6e3371eddd8a7846b83435c48f132cc5919d83a830504b797d6"
+SRC_URI[md5sum] = "de562d5bff5116d1acf2d3191603096b"
+SRC_URI[sha256sum] = "ac5e8f6c5ed83f5b65a3dd9187f8c534f167193446082e6a6576a0d9f72ba968"
inherit autotools gettext
--
1.7.0.4
^ permalink raw reply related
* [PATCH 1/2] ccache: update to 3.1.6
From: wenzong.fan @ 2011-10-19 8:53 UTC (permalink / raw)
To: openembedded-core
In-Reply-To: <cover.1319012299.git.wenzong.fan@windriver.com>
From: Wenzong Fan <wenzong.fan@windriver.com>
Update ccache to 3.1.6 from 3.1.5.
Signed-off-by: Wenzong Fan <wenzong.fan@windriver.com>
---
.../ccache/{ccache_3.1.5.bb => ccache_3.1.6.bb} | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-devtools/ccache/{ccache_3.1.5.bb => ccache_3.1.6.bb} (47%)
diff --git a/meta/recipes-devtools/ccache/ccache_3.1.5.bb b/meta/recipes-devtools/ccache/ccache_3.1.6.bb
similarity index 47%
rename from meta/recipes-devtools/ccache/ccache_3.1.5.bb
rename to meta/recipes-devtools/ccache/ccache_3.1.6.bb
index 9a967b2..e87468a 100644
--- a/meta/recipes-devtools/ccache/ccache_3.1.5.bb
+++ b/meta/recipes-devtools/ccache/ccache_3.1.6.bb
@@ -4,5 +4,5 @@ PR = "r0"
LICENSE = "GPLv3+"
LIC_FILES_CHKSUM = "file://LICENSE.txt;md5=80e92ec45d4fca91f127864fb9e5d932"
-SRC_URI[md5sum] = "b1a9684828eae68382d6afc98ce80d24"
-SRC_URI[sha256sum] = "54afc35c672ce451e04a478cfc0eb74c1ba184e27ef24881206602aa0eb94d63"
+SRC_URI[md5sum] = "e6565e7d6c95d1e35b7a0d67e39901e8"
+SRC_URI[sha256sum] = "59f58bb73f00db5bbff36b8eb530d3000c86b3110e34cf8dba9e2a5d19eb684f"
--
1.7.0.4
^ permalink raw reply related
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox