Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] bug in xserver compilation?
Date: Thu, 28 Jul 2016 23:30:03 +0200	[thread overview]
Message-ID: <20160728233003.4ce258a7@free-electrons.com> (raw)
In-Reply-To: <trinity-5c752dae-1ff7-4dbc-8baa-935b9342af4a-1469739383586@3capp-mailcom-bs07>

Hello,

On Thu, 28 Jul 2016 22:56:23 +0200, daggs wrote:

> I'm trying to add a new ddx driver to buildroot from aarch64 and I've encountered a strange issue.
> so I've decided to try and reproduce it with are more stable env, Iv'e ran make pc_x86_64_bios_defconfig, then entered menuconfig.
> in it I've enable c++ support, modular xserver and finally the intel xf86 video.
> I've hit make and waited, when buildroot got to xserver. it failed with the following error more than once:
> /home/dagg/workspace/buildroots/buildroot-master3/output/host/usr/x86_64-buildroot-linux-gnu/sysroot/usr/include/xf86drm.h:40:17: fatal error: drm.h: No such file or directory
>  #include <drm.h>

This is a known issue. Bernd posted a patch to fix it "[PATCH 1/2]
package/x11r7/xserver_xorg-server: add libdrm-specific cflags" but I
wasn't happy with it. You can see my reply from this Monday in the
mailing list archives.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  parent reply	other threads:[~2016-07-28 21:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-28 20:56 [Buildroot] bug in xserver compilation? daggs
2016-07-28 21:04 ` Yann E. MORIN
2016-07-29 14:23   ` daggs
2016-07-28 21:30 ` Thomas Petazzoni [this message]
2016-07-29 14:25   ` daggs
2016-07-30 13:52     ` Thomas Petazzoni

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=20160728233003.4ce258a7@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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