Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/5] gcc-4.7: Update to tip of gcc-4_7-branch since 4.7.1 has been out
Date: Fri, 22 Jun 2012 15:21:29 -0700	[thread overview]
Message-ID: <4FE4EFE9.7090602@linux.intel.com> (raw)
In-Reply-To: <CAMKF1spK9RwuhfGoTSPCEGvnKRcYfYPHGo0EdktwXdthP6uncA@mail.gmail.com>

On 06/22/2012 12:20 AM, Khem Raj wrote:
> On Thu, Jun 21, 2012 at 11:37 PM, Martin Jansa<martin.jansa@gmail.com>  wrote:
>> On Wed, Jun 20, 2012 at 08:18:37AM -0700, Khem Raj wrote:
>>> Signed-off-by: Khem Raj<raj.khem@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.

Thanks
	Sau!

>>
>> And the problem with (sometimes) missing or corrupt header file is still there:
>> | /OE/shr-core/tmp-eglibc/work-shared/gcc-4.7.1+svnr188658-r2/gcc-4_7-branch/gcc/dwarf2out.c:8383:6: warning: format not a string literal and no format arguments [-Wformat-security]
>> | gcc -c   -isystem/OE/shr-core/tmp-eglibc/sysroots/x86_64-linux/usr/include -O2 -pipe -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE  -W -Wall -Wwrite-strings -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes -Wmissing-format-attribute -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Wold-style-definition -Wc++-compat   -DHAVE_CONFIG_H -I. -I. -I/OE/shr-core/tmp-eglibc/work-shared/gcc-4.7.1+svnr188658-r2/gcc-4_7-branch/gcc -I/OE/shr-core/tmp-eglibc/work-shared/gcc-4.7.1+svnr188658-r2/gcc-4_7-branch/gcc/. -I/OE/shr-core/tmp-eglibc/work-shared/gcc-4.7.1+svnr188658-r2/gcc-4_7-branch/gcc/../include -I/OE/shr-core/tmp-eglibc/work-shared/gcc-4.7.1+svnr188658-r2/gcc-4_7-branch/gcc/../libcpp/include  -I/OE/shr-core/tmp-eglibc/work-shared/gcc-4.7.1+svnr188658-r2/gcc-4_7-branch/gcc/../libdecnumber -I/OE/shr-core/tmp-eglibc/work-shared/gcc-4.7.1+svnr188658-r2/gcc-4_7-branch/gcc/../libdecnumber/dpd -I../libdecnumber    /OE/shr-core/tmp-eglibc/work-shared/gcc-4.7.1+svnr188658-r2
/gcc-4_7-branch/gcc/emit-rtl.c -o emit-rtl.o
>> | /OE/shr-core/tmp-eglibc/work-shared/gcc-4.7.1+svnr188658-r2/gcc-4_7-branch/gcc/emit-rtl.c:42:17: fatal error: rtl.h: No such file or directory
>> | compilation terminated.
>> Restarting build helps again..
>>
>
> this is intriguing we should look into it can you explain (once again
> how can I reproduce it)
>
>> Cheers,
>>
>> --
>> Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com
>>
>> _______________________________________________
>> 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



  parent reply	other threads:[~2012-06-22 22:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-20 15:18 [PATCH 0/5] Toolchain fixes and uclibc-git upgrade Khem Raj
2012-06-20 15:18 ` [PATCH 1/5] uclibc-git: Upgrade to latest tip of master Khem Raj
2012-06-20 15:18 ` [PATCH 2/5] gcc-4.7: Update to tip of gcc-4_7-branch since 4.7.1 has been out Khem Raj
2012-06-22  6:37   ` Martin Jansa
2012-06-22  7:20     ` Khem Raj
2012-06-22  7:38       ` Martin Jansa
2012-07-10  7:52         ` Martin Jansa
2012-07-10 13:38           ` Khem Raj
2012-06-22 22:21       ` Saul Wold [this message]
2012-06-22 23:50         ` Khem Raj
2012-06-20 15:18 ` [PATCH 3/5] binutils: Add with-sysroot to target binutils Khem Raj
2012-06-20 15:18 ` [PATCH 4/5] gcc: Fix a case of sysroot with trailing / and gxx-include-dir leading slash Khem Raj
2012-06-20 15:18 ` [PATCH 5/5] binutils: Enable plugins by default Khem Raj
2012-06-21 12:24 ` [PATCH 0/5] Toolchain fixes and uclibc-git upgrade Richard Purdie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4FE4EFE9.7090602@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox