From: "Søren Holm" <sgh@sgh.dk>
To: openembedded-devel@lists.openembedded.org
Subject: Re: xf86-video-intel compilation failure
Date: Tue, 11 Jun 2013 15:49:21 +0200 [thread overview]
Message-ID: <7063136.DAg8vKBVKy@koontz> (raw)
In-Reply-To: <2472586.UfWZc5OvGZ@koontz>
Copying my local dri2.h into the sysroot like this makes the driver compile.
cp /usr/include/xorg/dri2.h tmp-eglibc/sysroots/vmc16/usr/include/xorg/
Any hint on where that files is.
Søren HolmTirsdag den 11. juni 2013 00:10:34 skrev :
> Hi
>
> When compiling xf86-video-intel I get the following compilation error. Do
> you have any ideas - I have looked everywhere for xorg/dri2.h
>
> | /home/sgh/git/openembedded/build/tmp-
>
> eglibc/sysroots/vmc16/usr/include/xorg/xf86.h:202:33: note: previous
> declaration of 'xf86CVTMode' was here
>
> | In file included from i830_3d.c:33:0:
> | intel.h:66:18: fatal error: dri2.h: No such file or directory
> | compilation terminated.
> | make[3]: *** [i830_3d.lo] Error 1
> | make[3]: Leaving directory `/home/sgh/git/openembedded/build/tmp-
>
> eglibc/work/prescott-oe-linux/xf86-video-intel/2_2.21.6-r0/xf86-video-
> intel-2.21.6/src'
>
> | make[2]: *** [all-recursive] Error 1
> | make[2]: Leaving directory `/home/sgh/git/openembedded/build/tmp-
>
> eglibc/work/prescott-oe-linux/xf86-video-intel/2_2.21.6-r0/xf86-video-
> intel-2.21.6/src'
>
> | make[1]: *** [all-recursive] Error 1
> | make[1]: Leaving directory `/home/sgh/git/openembedded/build/tmp-
>
> eglibc/work/prescott-oe-linux/xf86-video-intel/2_2.21.6-r0/xf86-video-
> intel-2.21.6'
>
> | make: *** [all] Error 2
> | ERROR: oe_runmake failed
--
Søren Holm
next prev parent reply other threads:[~2013-06-11 13:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-10 22:10 xf86-video-intel compilation failure Søren Holm
2013-06-11 13:49 ` Søren Holm [this message]
2013-06-11 15:09 ` Khem Raj
2013-06-11 15:12 ` Martin Jansa
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=7063136.DAg8vKBVKy@koontz \
--to=sgh@sgh.dk \
--cc=openembedded-devel@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