From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] directfb: Fix RPATH warnings
Date: Fri, 16 Mar 2012 16:29:25 +0000 [thread overview]
Message-ID: <1331915365.18586.203.camel@ted> (raw)
In-Reply-To: <4F635AE7.50602@windriver.com>
On Fri, 2012-03-16 at 10:23 -0500, Mark Hatle wrote:
> On 3/16/12 8:44 AM, Richard Purdie wrote:
> > Fix configure not to remove variables which trigger the unneccessary rpaths to get
> > encoded. Also take the opportunity to clean up the patches directory.
>
> ...
>
> Was the dont-use-linux-config.patch not being used or something? I'm a bit
> confused as to why it was removed. It appears from the contents that it is
> still relevant for 8xx and 403GCX processors. (Mind you, we don't actually
> support either of these in oe-core currently.. the 403GCX is likely completely
> dead, from a historical perspective, but I still see the occasionaly 8xx part.)
The patch was not being applied by the recipe and was unused.
Cheers,
Richard
prev parent reply other threads:[~2012-03-16 16:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 13:44 [PATCH] directfb: Fix RPATH warnings Richard Purdie
2012-03-16 15:23 ` Mark Hatle
2012-03-16 16:29 ` 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=1331915365.18586.203.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 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.