From: Martin Jansa <martin.jansa@gmail.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: openembedded-core@linuxtogo.org
Subject: Re: binutils 2.23 call for testing the recipes
Date: Thu, 9 Aug 2012 16:57:32 +0200 [thread overview]
Message-ID: <20120809145732.GD3273@jama.jama.net> (raw)
In-Reply-To: <CAMKF1sqC-_YTdwsLvVoVyz04ndMxNt6W1z__f_9nUTfb6aF8GQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2258 bytes --]
On Thu, Aug 09, 2012 at 07:53:43AM -0700, Khem Raj wrote:
> On Thu, Aug 9, 2012 at 6:10 AM, Martin Jansa <martin.jansa@gmail.com> wrote:
> > On Wed, Aug 08, 2012 at 10:45:19AM -0700, Khem Raj wrote:
> >> Hi
> >>
> >> Binutils 2.23 branch has started upstream. Given that toolchain
> >> components require a lot of soak time, I have created the recipes
> >> for binutils 2.23 and pushed it here
> >>
> >> http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/binutils-2.23
> >>
> >> If you are using angstrom set
> >>
> >> ANGSTROM_BINUTILS_VERSION = "2.23" in local.conf after pulling that branch
> >> for OE-Core it will work as it is
> >>
> >> Let me know if you see any errors.
> >
> > I was trying to build armv4t image with gold enabled again to see if
> > those issues with gold are resolved and building linux-3.2 and linux-2.6.39
> > are failing with this:
> >
> > | LD arch/arm/boot/compressed/vmlinux
> > | arm-oe-linux-gnueabi-ld: error: DIV usage mismatch between arch/arm/boot/compressed/misc.o and output
> > | arm-oe-linux-gnueabi-ld: error: DIV usage mismatch between arch/arm/boot/compressed/lib1funcs.o and output
> > | make[2]: *** [arch/arm/boot/compressed/vmlinux] Error 1
> >
> > Any hint for that?
>
> probably you need something like below
> https://lists.yoctoproject.org/pipermail/poky/2011-January/003131.html
I've used something like
https://github.com/CyanogenMod/android_kernel_samsung_tuna/commit/ec1ac589d49081286164246fbaaba0012ae7ecac
and core-image-minimal-mtdutils looks better wrt gold issues we had, now
waiting for bigger image like shr-lite-image to test it more.
Cheers,
>
> >
> > 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
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2012-08-09 15:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-08 17:45 binutils 2.23 call for testing the recipes Khem Raj
2012-08-09 13:10 ` Martin Jansa
2012-08-09 14:53 ` Khem Raj
2012-08-09 14:57 ` Martin Jansa [this message]
2012-08-11 8:04 ` Martin Jansa
2012-08-12 5:30 ` Khem Raj
2012-08-12 6:14 ` Martin Jansa
2012-08-16 10:36 ` Martin Jansa
2012-09-16 6:06 ` Martin Jansa
2012-09-17 1:22 ` Khem Raj
2012-11-16 8:07 ` Martin Jansa
2012-11-16 19:16 ` Saul Wold
2012-11-19 10:27 ` Enrico Scholz
2012-11-19 12:04 ` Marcin Juszkiewicz
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=20120809145732.GD3273@jama.jama.net \
--to=martin.jansa@gmail.com \
--cc=openembedded-core@linuxtogo.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