From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] gcc5: Add PR65779 patch to fix powerpc compile issues
Date: Tue, 12 May 2015 08:28:00 +0100 [thread overview]
Message-ID: <1431415680.30971.114.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAMKF1srBkzXSiVyo27LbF0TYb6AjxB_Z++no3QyJ9VJwJHFFWw@mail.gmail.com>
On Mon, 2015-05-11 at 17:24 -0700, Khem Raj wrote:
> On Mon, May 11, 2015 at 4:20 PM, akuster808 <akuster808@gmail.com> wrote:
> >
> >
> > On 05/11/2015 09:54 AM, Richard Purdie wrote:
> >>
> >> This fixes compile issues on powerpc with gcc 5 which show up with
> >> errors like:
> >>
> >> | make[2]: Entering directory
> >> '/media/build1/poky/build/tmp/work/ppc7400-poky-linux/xprop/1_1.2.2-r0/build'
> >> | powerpc-poky-linux-gcc -m32 -mhard-float -mcpu=7400
> >> --sysroot=/media/build1/poky/build/tmp/sysroots/qemuppc -Wall
> >> -Wpointer-arith -Wmissing-declarations -Wformat=2 -Wstrict-prototypes
> >> -Wmissing-prototypes -Wnested-externs -Wbad-function-cast
> >> -Wold-style-definition -Wdeclaration-after-statement -Wunused
> >> -Wuninitialized -Wshadow -Wmissing-noreturn -Wmissing-format-attribute
> >> -Wredundant-decls -Wlogical-op -Werror=implicit -Werror=nonnull
> >> -Werror=init-self -Werror=main -Werror=missing-braces -Werror=sequence-point
> >> -Werror=return-type -Werror=trigraphs -Werror=array-bounds
> >> -Werror=write-strings -Werror=address -Werror=int-to-pointer-cast
> >> -Werror=pointer-to-int-cast -fno-strict-aliasing -O2 -pipe -g
> >> -feliminate-unused-debug-types -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed
> >> -o xprop dsimple.o clientwin.o xprop.o -lX11
> >> | /media/build1/poky/build/tmp/sysroots/qemuppc/usr/lib/../lib/libX11.so:
> >> undefined reference to `.LCL2'
> >> | collect2: error: ld returned 1 exit status
> >>
> >> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> >
> >
> > Acked-by: Armin Kuster <Akuster808@gmail.com>
> >
> >
> > this fixes all but one package(lzop) failure on qemuppc base yocto world
> > build.
> >
>
> I am fine witj this patch for now, since we are mostly build testing,
> we have to keep in mind
> its a codegen bug and can bite us at runtime. I am just hoping for an
> update to this patch and that will eliminate
> that doubt.
Agreed, an update upstream would obviously help. FWIW the automated
runtime tests did look reasonable on the autobuilder apart from:
core-image-sato-sdk has a problem with the C++ toolchain not finding
limits (all arches).
qemuarm is not booting (minimal, sato or sato-sdk).
However these issues were present before the patch so I don't think its
related.
Since the failures list is better with the patch I'll merge it until
something better comes along.
Cheers,
Richard
next prev parent reply other threads:[~2015-05-12 7:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 16:54 [PATCH] gcc5: Add PR65779 patch to fix powerpc compile issues Richard Purdie
2015-05-11 17:28 ` akuster808
2015-05-11 23:20 ` akuster808
2015-05-12 0:24 ` Khem Raj
2015-05-12 7:28 ` Richard Purdie [this message]
2015-05-12 16:03 ` Khem Raj
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=1431415680.30971.114.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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