From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] directfb: Fix RPATH warnings
Date: Fri, 16 Mar 2012 10:23:19 -0500 [thread overview]
Message-ID: <4F635AE7.50602@windriver.com> (raw)
In-Reply-To: <1331905468.18586.182.camel@ted>
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.)
--Mark
> diff --git a/meta/recipes-graphics/directfb/directfb.inc b/meta/recipes-graphics/directfb/directfb.inc
> index 9061ac1..515d19f 100644
> --- a/meta/recipes-graphics/directfb/directfb.inc
> +++ b/meta/recipes-graphics/directfb/directfb.inc
> @@ -11,11 +11,9 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=dcf3c825659e82539645da41a7908589"
> HOMEPAGE = "http://directfb.org"
> DEPENDS = "jpeg libpng freetype zlib tslib"
>
> -SRC_URI = " \
> - http://directfb.org/downloads/Core/DirectFB-1.4/DirectFB-${PV}.tar.gz \
> - file://directfb-1.2.x-fix-pkgconfig-cflags.patch \
> - file://dont-use-linux-config.patch \
> - "
> +SRC_URI = "http://directfb.org/downloads/Core/DirectFB-1.4/DirectFB-${PV}.tar.gz \
> + file://directfb-1.2.x-fix-pkgconfig-cflags.patch \
> + file://configurefix.patch"
...
> diff --git a/meta/recipes-graphics/directfb/files/dont-use-linux-config.patch b/meta/recipes-graphics/directfb/files/dont-use-linux-config.patch
> deleted file mode 100644
> index ba8ead8..0000000
> --- a/meta/recipes-graphics/directfb/files/dont-use-linux-config.patch
> +++ b/dev/null
> @@ -1,23 +0,0 @@
> -
> -directfb: don't use linux/config.h in powerpc assembly
> -
> -Author: jeremy_laine at openembedded.org
> -Branch: org.openembedded.dev
> -Revision: 73964f8e6912f066c224fed54daeeb44836d9cdf
> -ViewMTN: http://monotone.openembedded.org/revision/info/73964f8e6912f066c224fed54daeeb44836d9cdf
> -
> -Upstream-Status: Inappropriate [configuration]
> -Signed-off-by: Saul Wold<sgw@linux.intel.com>
> -
> -diff -urN DirectFB-1.1.0.orig/lib/direct/ppcasm_memcpy_cachable.S DirectFB-1.1.0/lib/direct/ppcasm_memcpy_cachable.S
> ---- DirectFB-1.1.0.orig/lib/direct/ppcasm_memcpy_cachable.S 2007-08-07 21:43:00.000000000 +0200
> -+++ DirectFB-1.1.0/lib/direct/ppcasm_memcpy_cachable.S 2008-06-07 04:14:26.000000000 +0200
> -@@ -34,8 +34,6 @@
> -
> - #define __ASSEMBLY__
> -
> --#include<linux/config.h>
> --
> - #if defined(CONFIG_8xx) || defined(CONFIG_403GCX)
> - #define L1_CACHE_LINE_SIZE 16
> - #define LG_L1_CACHE_LINE_SIZE 4
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2012-03-16 15:32 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 [this message]
2012-03-16 16:29 ` Richard Purdie
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=4F635AE7.50602@windriver.com \
--to=mark.hatle@windriver.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