On Fri, Jun 22, 2012 at 3:21 PM, Saul Wold <s...@linux.intel.com> wrote:
> On 06/22/2012 12:20 AM, Khem Raj wrote:
>>
>> On Thu, Jun 21, 2012 at 11:37 PM, Martin Jansa<martin.ja...@gmail.com>
>> wrote:
>>>
>>> On Wed, Jun 20, 2012 at 08:18:37AM -0700, Khem Raj wrote:
>>>>
>>>> Signed-off-by: Khem Raj<raj.k...@gmail.com>
>>>> ---
>>>> meta/recipes-devtools/gcc/gcc-4.7.inc | 12 ++++++------
>>>> 1 files changed, 6 insertions(+), 6 deletions(-)
>>>>
>>>> diff --git a/meta/recipes-devtools/gcc/gcc-4.7.inc
>>>> b/meta/recipes-devtools/gcc/gcc-4.7.inc
>>>> index 34a73b1..25a1088 100644
>>>> --- a/meta/recipes-devtools/gcc/gcc-4.7.inc
>>>> +++ b/meta/recipes-devtools/gcc/gcc-4.7.inc
>>>> @@ -3,12 +3,12 @@ require gcc-common.inc
>>>> PR = "r2"
>>>>
>>>> # Third digit in PV should be incremented after a minor release
>>>> -# happens from this branch on gcc e.g. currently its 4.7.0
>>>> -# when 4.7.1 is releases and we bump SRCREV beyond the release
>>>> -# on branch then PV should be incremented to 4.7.1+svnr${SRCPV}
>>>> +# happens from this branch on gcc e.g. currently its 4.7.1
>>>> +# when 4.7.2 is releases and we bump SRCREV beyond the release
>>>> +# on branch then PV should be incremented to 4.7.2+svnr${SRCPV}
>>>> # to reflect that change
>>>>
>>>> -PV = "4.7.0+svnr${SRCPV}"
>>>> +PV = "4.7.1+svnr${SRCPV}"
>>>>
>>>> # BINV should be incremented after updating to a revision
>>>> # after a minor gcc release (e.g. 4.7.1 or 4.7.2) has been made
>>>> @@ -16,9 +16,9 @@ PV = "4.7.0+svnr${SRCPV}"
>>>> # 4.7.1 then the value below will have 2 which will mean 4.7.2
>>>> # which will be next minor release and so on.
>>>>
>>>> -BINV = "4.7.1"
>>>> +BINV = "4.7.2"
>>>>
>>>> -SRCREV = "186651"
>>>> +SRCREV = "188658"
>>>> BRANCH = "gcc-4_7-branch"
>>>> FILESPATH = "${@base_set_filespath([ '${FILE_DIRNAME}/gcc-4.7' ], d)}"
>>>
>>>
>>> I'm not sure if this one is new, but libgcc now reports unpackaged
>>> file:
>>>
>>> NOTE: package libgcc-4.7.1+svnr188658-r2: task do_package: Started
>>> WARNING: For recipe libgcc, the following files/directories were
>>> installed but not shipped in any package:
>>> WARNING: /usr/lib/arm-oe-linux-gnueabi/4.7.2/include
>>> WARNING: /usr/lib/arm-oe-linux-gnueabi/4.7.2/include/unwind.h
>>
>>
>> can you see couple of things 1. if this file is being generated and
>> installed during libgcc build or if its coming from the bits that are
>> stashed away from gcc-cross build
>>
> Khem, this file seems to be set up during do_configure time
>
> config.status: linking
> /srv/ssd/sgw_ab/builds/repack/tmp/work-shared/gcc-4.7.1+svnr188658-r2/gcc-4_7-branch/libgcc/unwind-generic.h
> to unwind.h
>
>
>> this file should not be packaged with libgcc so right solution will be
>> to delete this file
>
>
> Will you provide the patch please.
>
eventually yes if no one beats me to it.
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
