From: Patrick Ohly <patrick.ohly@intel.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-devel <openembedded-devel@lists.openembedded.org>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] State of bitbake world, Failed tasks 2017-03-27
Date: Wed, 29 Mar 2017 13:19:08 +0200 [thread overview]
Message-ID: <1490786348.6396.415.camel@intel.com> (raw)
In-Reply-To: <CA+chaQcd7Pa-w7zWLLbck1Xu+r0t3udzLf0tJQqrkgSzCu+HZA@mail.gmail.com>
On Wed, 2017-03-29 at 12:14 +0200, Martin Jansa wrote:
> > Can individual recipes choose to be built using the normal ld?
>
>
>
> yes, see example in:
> meta/recipes-bsp/u-boot/u-boot.inc
>
> meta/recipes-support/libunwind/libunwind_git.bb
Thanks. I'll try to do something similar.
> but it was working with older binutils, so maybe worth tracking down
> where it got borken.
Before my OE-core fix, it was always using /usr/bin/gcc and thus ld. Now
that it actually uses the compiler intended for the target, it ends up
using gold, which fails.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
WARNING: multiple messages have this Message-ID (diff)
From: Patrick Ohly <patrick.ohly@intel.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-devel <openembedded-devel@lists.openembedded.org>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: State of bitbake world, Failed tasks 2017-03-27
Date: Wed, 29 Mar 2017 13:19:08 +0200 [thread overview]
Message-ID: <1490786348.6396.415.camel@intel.com> (raw)
In-Reply-To: <CA+chaQcd7Pa-w7zWLLbck1Xu+r0t3udzLf0tJQqrkgSzCu+HZA@mail.gmail.com>
On Wed, 2017-03-29 at 12:14 +0200, Martin Jansa wrote:
> > Can individual recipes choose to be built using the normal ld?
>
>
>
> yes, see example in:
> meta/recipes-bsp/u-boot/u-boot.inc
>
> meta/recipes-support/libunwind/libunwind_git.bb
Thanks. I'll try to do something similar.
> but it was working with older binutils, so maybe worth tracking down
> where it got borken.
Before my OE-core fix, it was always using /usr/bin/gcc and thus ld. Now
that it actually uses the compiler intended for the target, it ends up
using gold, which fails.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
next prev parent reply other threads:[~2017-03-29 11:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 7:23 State of bitbake world, Failed tasks 2017-03-27 Martin Jansa
2017-03-29 8:35 ` [OE-core] " Patrick Ohly
2017-03-29 8:35 ` Patrick Ohly
2017-03-29 9:14 ` [OE-core] " Martin Jansa
2017-03-29 9:14 ` Martin Jansa
2017-03-29 9:38 ` [OE-core] " Patrick Ohly
2017-03-29 9:38 ` Patrick Ohly
2017-03-29 10:14 ` [OE-core] " Martin Jansa
2017-03-29 10:14 ` Martin Jansa
2017-03-29 11:19 ` Patrick Ohly [this message]
2017-03-29 11:19 ` Patrick Ohly
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=1490786348.6396.415.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.