From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: gcc 4.7 + mips64 architecture support
Date: Thu, 26 Apr 2012 15:47:19 +0100 [thread overview]
Message-ID: <1335451639.20130.18.camel@ted> (raw)
In-Reply-To: <CAMKF1sq94g5aaYPQZ=UZtBT6iBxCMJ7ZrKer=gaCVoEjV=eWKA@mail.gmail.com>
On Wed, 2012-04-25 at 16:31 -0700, Khem Raj wrote:
> Hello
>
> Now that release is almost out of door. I would like some eyes on the
> gcc-4.7 work
> and mips64 architecture support that I have done meanwhile
>
> I have made sure that gcc-4.6 still keeps working and I have patches
> for gcc-4.5 too
> for meta-oe too. I have repeatedly built core-image-sato and
> core-image-minimal for uclibc/eglibc
> but more coverage would be nicer.
>
> The patches are posted here
>
> http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/misc
>
> I would appreciate any feedback or testing on this
I had a look through the patch series. I've posted an altered version of
the class override patch. I've pulled the gcc 4.7 part into master-next,
have get gcc 4.7 as the default and am running it though the
autobuilder. That should see how we stand with our usual regression
tests.
I didn't add in the kmod or mips64 bits yet as I wanted to test one
thing at a time.
Cheers,
Richard
next prev parent reply other threads:[~2012-04-26 14:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-25 23:31 gcc 4.7 + mips64 architecture support Khem Raj
2012-04-26 14:47 ` Richard Purdie [this message]
2012-04-26 19:30 ` Richard Purdie
2012-04-26 21:06 ` Richard Purdie
2012-04-26 21:35 ` Khem Raj
2012-04-29 17:23 ` Khem Raj
2012-04-30 14:41 ` Richard Purdie
2012-04-30 14:47 ` Khem Raj
2012-04-30 14:53 ` Richard Purdie
2012-04-30 14:59 ` Khem Raj
2012-04-30 15:20 ` Mark Hatle
2012-04-30 15:39 ` Richard Purdie
2012-04-30 16:25 ` Khem Raj
2012-04-29 9:12 ` Martin Jansa
2012-04-29 15:36 ` Khem Raj
2012-04-30 11:07 ` Martin Jansa
2012-04-30 10:43 ` Martin Jansa
2012-04-30 14:15 ` Khem Raj
2012-04-30 14:31 ` Martin Jansa
2012-05-01 11:29 ` Martin Jansa
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=1335451639.20130.18.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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