From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: Bruce Ashfield <bruce.ashfield@windriver.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] linux-libc-headers: exclude drm headers from sysroot
Date: Tue, 04 Aug 2015 09:52:24 -0500 [thread overview]
Message-ID: <1438699944.30526.5.camel@linuxfoundation.org> (raw)
In-Reply-To: <1438696733-234279-1-git-send-email-paul.gortmaker@windriver.com>
On Tue, 2015-08-04 at 09:58 -0400, Paul Gortmaker wrote:
> While diagnosing a problem with xf86-video-intel I noticed we had two
> copies of drm headers in the sysroot; one from here and one from
> the libdrm package. The xf86-video-intel turned out to be another
> thing, but that doesn't mean we want two copies in the sysroot with
> different content and luck of include path indicating which one we
> get.
>
> This one landed in usr/include/drm and the libdrm one put its files
> at usr/include/libdrm, so there was no obvious over-write conflict.
>
> The obvious risk here would be unearthing implicit dependencies on
> the libdrm; things trying to build before it has populated the sysroot
> but two full highly parallel builds containing a full desktop graphics
> suite did not show any issues.
>
> Cc: Bruce Ashfield <bruce.ashfield@windriver.com>
> Cc: Richard Purdie <richard.purdie@linuxfoundation.org>
> Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Is this something which should get addressed in the upstream kernel?
I agree we likely don't want two sets of those.
Cheers,
Richard
next prev parent reply other threads:[~2015-08-04 14:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-04 13:58 [PATCH] linux-libc-headers: exclude drm headers from sysroot Paul Gortmaker
2015-08-04 14:52 ` Richard Purdie [this message]
2015-08-04 15:01 ` Paul Gortmaker
2015-08-05 14:00 ` Bruce Ashfield
2015-08-06 3:26 ` Khem Raj
2015-08-04 14:52 ` Richard Purdie
2015-08-06 3:21 ` Khem Raj
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=1438699944.30526.5.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.gortmaker@windriver.com \
/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