Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] gcc-package-cross: also install the symlinks in libexec with target prefix
Date: Mon, 06 Jun 2011 10:09:23 -0700	[thread overview]
Message-ID: <4DED09C3.1010103@linux.intel.com> (raw)
In-Reply-To: <1307100611.2529.256.camel@phil-desktop>

On 06/03/2011 04:30 AM, Phil Blundell wrote:
> ... since this is where collect2 seems to look for them.  This seems like
> it is really a bug in collect2, but installing the symlinks is an easy
> workaround.  Without this you get "could not find ld" errors when using -flto.
>
> Signed-off-by: Phil Blundell<philb@gnu.org>
> ---
>   meta/recipes-devtools/gcc/gcc-package-cross.inc |    1 +
>   1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/meta/recipes-devtools/gcc/gcc-package-cross.inc b/meta/recipes-devtools/gcc/gcc-package-cross.inc
> index 04c8101..b51336b 100644
> --- a/meta/recipes-devtools/gcc/gcc-package-cross.inc
> +++ b/meta/recipes-devtools/gcc/gcc-package-cross.inc
> @@ -20,6 +20,7 @@ do_install () {
>   	install -d $dest
>   	for t in ar as ld nm objcopy objdump ranlib strip g77 gcc cpp gfortran; do
>   		ln -sf ${BINRELPATH}/${TARGET_PREFIX}$t $dest$t
> +		ln -sf ${BINRELPATH}/${TARGET_PREFIX}$t ${dest}${TARGET_PREFIX}$t
>   	done
>
>   	# Remove things we don't need but keep share/java


Merged into OE-Core

Thanks
	Sau!



      reply	other threads:[~2011-06-06 17:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-03 11:30 [PATCH] gcc-package-cross: also install the symlinks in libexec with target prefix Phil Blundell
2011-06-06 17:09 ` Saul Wold [this message]

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=4DED09C3.1010103@linux.intel.com \
    --to=sgw@linux.intel.com \
    --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