On Thu, Feb 11, 2016 at 12:25:12PM -0500, Trevor Woerner wrote:
> On 02/09/16 23:37, Khem Raj wrote:
> > IIRC gold has its own notions to enable gold
> > so you need to enable that
> >
> >> On Feb 9, 2016, at 8:18 PM, Trevor Woerner wrote:
> >>
> >> I've tried every
On 02/11/16 14:20, Martin Jansa wrote:
Did you add ld-is-gold to DISTRO_FEATURES?
Yes, it's the only way I know of to build an image with gold instead of
bfd. And no other thing that gets built has any problems finding and
running the linker.
I'll post my chromium recipe shortly, although
On 02/09/16 23:37, Khem Raj wrote:
IIRC gold has its own notions to enable gold
so you need to enable that
On Feb 9, 2016, at 8:18 PM, Trevor Woerner wrote:
I've tried every combination I can think of and no matter what I try, if gold
is the linker the chromium build
> On Feb 11, 2016, at 9:25 AM, Trevor Woerner wrote:
>
> On 02/09/16 23:37, Khem Raj wrote:
>> IIRC gold has its own notions to enable gold
>> so you need to enable that
>>
>>> On Feb 9, 2016, at 8:18 PM, Trevor Woerner wrote:
>>>
>>> I've tried every
On 9 February 2016 at 02:56, Trevor Woerner wrote:
> MACHINE = "qemux86-64"
>
> Essentially: minnowboard max (turbot, specifically)
>
As an aside, if you're actually building for the MinnowMax then the
meta-intel BSP will be a lot better.
Ross
--
On 02/09/16 05:00, Burton, Ross wrote:
On 9 February 2016 at 02:56, Trevor Woerner > wrote:
MACHINE = "qemux86-64"
Essentially: minnowboard max (turbot, specifically)
As an aside, if you're actually building for the MinnowMax
I've tried every combination I can think of and no matter what I try, if
gold is the linker the chromium build always errors out with:
collect2: fatal error: cannot find 'ld'
--
___
Openembedded-core mailing list
IIRC gold has its own notions to enable gold
so you need to enable that
> On Feb 9, 2016, at 8:18 PM, Trevor Woerner wrote:
>
> I've tried every combination I can think of and no matter what I try, if gold
> is the linker the chromium build always errors out with:
>
>
On 02/08/16 19:25, Mark Hatle wrote:
Which arch/tune are you targeting?
Build Configuration:
BB_VERSION= "1.28.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "openSUSE-project-13.2"
TARGET_SYS= "x86_64-poky-linux"
MACHINE = "qemux86-64"
DISTRO=
> On Feb 8, 2016, at 7:03 PM, Trevor Woerner wrote:
>
> On 02/08/16 21:25, Khem Raj wrote:
>> On Mon, Feb 8, 2016 at 3:20 PM, Trevor Woerner wrote:
>>> This is more of a "FYI", but I've noticed that the build time of my chromium
>>> recipe has gone from
On 02/08/16 21:25, Khem Raj wrote:
On Mon, Feb 8, 2016 at 3:20 PM, Trevor Woerner wrote:
This is more of a "FYI", but I've noticed that the build time of my chromium
recipe has gone from ~45 minutes to ~2h15m when the only thing that changes
is to move openembedded-core
On Mon, Feb 8, 2016 at 3:20 PM, Trevor Woerner wrote:
> This is more of a "FYI", but I've noticed that the build time of my chromium
> recipe has gone from ~45 minutes to ~2h15m when the only thing that changes
> is to move openembedded-core from the commit just before
Which arch/tune are you targeting? I know that on a few processors 2.26 has
added "link time optimization" (i.e. our processor is broken and we're working
around problems in the linker.)
It's possible you hit one of those cases, or it may simply be that much slower
for some reason. But worse
This is more of a "FYI", but I've noticed that the build time of my
chromium recipe has gone from ~45 minutes to ~2h15m when the only thing
that changes is to move openembedded-core from the commit just before
upgrading binutils to version 2.26 ([fd75637] native.bbclass: Set
CXXFLAGS from
14 matches
Mail list logo