From: Tom Zanussi <tom.zanussi@intel.com>
To: "Kamble, Nitin A" <nitin.a.kamble@intel.com>
Cc: "Hart, Darren" <darren.hart@intel.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] gcc: Add recipes for 4.6.0
Date: Sat, 23 Apr 2011 20:01:07 -0500 [thread overview]
Message-ID: <1303606867.29588.196.camel@elmorro> (raw)
In-Reply-To: <9DA5872FEF993D41B7173F58FCF6BE9451635064@orsmsx504.amr.corp.intel.com>
On Wed, 2011-04-20 at 17:18 -0700, Kamble, Nitin A wrote:
> Met 1st build failure with gcc4.6.6. I think it is not a gcc issue, but the recipe code issue; And Tom/Darren can take care of it.
>
Hi,
The patchset applied fine for me, but I'm getting do_patch errors when building:
*** Manual patch resolution mode ***
Dropping to a shell, so patch rejects can be fixed manually.
Run "quilt refresh" when patch is corrected, press CTRL+D to exit.
Applying patch gcc-uclibc-locale-ctype_touplow_t.patch
patching file libstdc++-v3/config/locale/generic/c_locale.h
Hunk #1 FAILED at 41.
1 out of 1 hunk FAILED -- saving rejects to file libstdc++-v3/config/locale/generic/c_locale.h.rej
patching file libstdc++-v3/config/os/gnu-linux/ctype_base.h
Hunk #2 FAILED at 47.
1 out of 2 hunks FAILED -- saving rejects to file libstdc++-v3/config/os/gnu-linux/ctype_base.h.rej
patching file libstdc++-v3/config/locale/generic/c_locale.cc
Applied patch gcc-uclibc-locale-ctype_touplow_t.patch (forced; needs refresh)
trz@elmorro:/usr/local/src/yocto/test/build/tmp/work/x86_64-poky-linux/gcc-cross-intermediate-4.6.0-r0/gcc-4.6.0$
I actually fixed a couple of these up, but they keep coming...
So is there anything special I need to do to get this building cleanly?
I'm using master, and added the following to my local.conf:
GCCVERSION = "4.6.0"
SDKGCCVERSION = "4.6.0"
and did bitbake linux-yocto.
Once I have it working and can fix compile errors, I can send a patch to
fix it up if necessary, but note that this particular gcc warning
(unused-but-set-variable) is on its way to being disabled in the
upstream kernel. See the lkml thread, "Re: annoying new gcc 4.6.0
warnings.":
https://lkml.org/lkml/2011/4/21/325
Tom
> Thanks,
> Nitin
>
>
> | PERF_VERSION = 2.6.37.5.308.g69cfbd^M
> | make: Leaving directory `/build_disk/poky_build/build_gcc_4.6.0/tmp/work/qemux86_64-poky-linux/linux-yocto-2.6.37+git1+727fc4769aa920fc5bb3eb9a81bf92d0e6340903_1+69cfbdf9f1ff461a75e5b77d6d7ba35e97db4cc3-r16/linux/tools/perf'^M
> | make: Entering directory `/build_disk/poky_build/build_gcc_4.6.0/tmp/work/qemux86_64-poky-linux/linux-yocto-2.6.37+git1+727fc4769aa920fc5bb3eb9a81bf92d0e6340903_1+69cfbdf9f1ff461a75e5b77d6d7ba35e97db4cc3-r16/linux/tools/perf'^M
> | Makefile:512: No libdw.h found or old libdw.h found or elfutils is older than 0.138, disables dwarf support. Please install new elfutils-devel/libdw-dev^M
> | Makefile:568: newt not found, disables TUI support. Please install newt-devel or libnewt-dev^M
> | GEN common-cmds.h^M
> | * new build flags or prefix^M
> | CC perf.o^M
> | CC builtin-annotate.o^M
> | CC builtin-bench.o^M
> | CC bench/sched-messaging.o^M
> | CC bench/sched-pipe.o^M
> | bench/sched-pipe.c: In function 'bench_sched_pipe':^M
> | bench/sched-pipe.c:58:6: error: variable 'ret' set but not used [-Werror=unused-but-set-variable]^M
> | cc1: all warnings being treated as errors^M
> | ^M
> | make: *** [bench/sched-pipe.o] Error 1^M
> | ERROR: Function 'do_compile_perf' failed (see /build_disk/poky_build/build_gcc_4.6.0/tmp/work/qemux86_64-poky-linux/linux-yocto-2.6.37+git1+727fc4769aa920fc5bb3eb9a81bf92d0e6340903_1+69cfbdf9f1ff461a75e5b77d6d7ba35e97db4cc3-r16/temp/log.do_compile_perf.24035 for further information)^M
> | make:^M
> NOTE: package linux-yocto-2.6.37+git1+727fc4769aa920fc5bb3eb9a81bf92d0e6340903_1+69cfbdf9f1ff461a75e5b77d6d7ba35e97db4cc3-r16: task do_compile_perf: Failed
>
>
> > -----Original Message-----
> > From: openembedded-core-bounces@lists.openembedded.org
> > [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf Of
> > Kamble, Nitin A
> > Sent: Wednesday, April 20, 2011 2:58 PM
> > To: Patches and discussions about the oe-core layer
> > Subject: Re: [OE-core] [PATCH] gcc: Add recipes for 4.6.0
> >
> > Khem,
> > Good news. All the gcc recipes built without any errors for arm, ppc,
> > mips, x86, x86-64. Now I am trying to build the poky-image-sato-sdk
> > image for each architecture. Will keep you posted.
> >
> > Thanks & Regards,
> > Nitin
> >
> > _______________________________________________
> > Openembedded-core mailing list
> > Openembedded-core@lists.openembedded.org
> > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2011-04-24 1:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 4:27 [PATCH] gcc: Add recipes for 4.6.0 Khem Raj
2011-04-20 15:42 ` Kamble, Nitin A
2011-04-20 16:48 ` Saul Wold
2011-04-20 16:51 ` Koen Kooi
2011-04-20 16:56 ` Kamble, Nitin A
2011-04-20 17:04 ` Khem Raj
2011-04-20 21:57 ` Kamble, Nitin A
2011-04-21 0:18 ` Kamble, Nitin A
2011-04-24 1:01 ` Tom Zanussi [this message]
2011-04-24 1:11 ` Khem Raj
2011-04-24 18:41 ` Khem Raj
2011-04-24 20:59 ` Tom Zanussi
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=1303606867.29588.196.camel@elmorro \
--to=tom.zanussi@intel.com \
--cc=darren.hart@intel.com \
--cc=nitin.a.kamble@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