Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] gcc-configure-common.inc: Stop gcc looking at build system paths
Date: Mon, 16 Apr 2012 09:23:10 +0100	[thread overview]
Message-ID: <1334564590.16992.63.camel@ted> (raw)
In-Reply-To: <CAMKF1srUybfieu7yw8NGy5b9myojC=KZXRuue7xB0ELZObgHHQ@mail.gmail.com>

On Sun, 2012-04-15 at 16:42 -0700, Khem Raj wrote:
> On Sun, Apr 15, 2012 at 10:05 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > gcc_cv_collect2_libs
> 
> is it the /usr/lib/cmplrs/cc2.11 access issue ?

It is.

> in that case the fix it fine. However if its something in LTO
> then we need to dig deeper

Its not lto related.

Cheers,

Richard




      reply	other threads:[~2012-04-16  8:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-15 17:05 [PATCH] gcc-configure-common.inc: Stop gcc looking at build system paths Richard Purdie
2012-04-15 23:42 ` Khem Raj
2012-04-16  8:23   ` Richard Purdie [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=1334564590.16992.63.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