All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephan Raue <stephan.raue@gmx.net>
To: dri-devel@lists.sf.net
Subject: missing file libkms/internal.h in libdrm-2.4.18
Date: Wed, 17 Feb 2010 17:45:33 +0100	[thread overview]
Message-ID: <4B7C1D2D.2070209@gmx.net> (raw)

libdrm-2.4.18.tar.bz2 from http://dri.freedesktop.org/libdrm is missing 
file libkms/internal.h:

in git it exist.

libtool: compile: 
/home/stephan/projects/openelec/build.OpenELEC-intel.i386.devel/toolchain/bin/i686-openelec-linux-gnu-gcc 
-DHAVE_CONFIG_H -I. -I.. -Wall -Wextra -Wsign-compare 
-Werror-implicit-function-declaration -Wpointer-arith -Wwrite-strings 
-Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations 
-Wnested-externs -Wpacked -Wswitch-enum -Wmissing-format-attribute 
-Wstrict-aliasing=2 -Winit-self -Wunsafe-loop-optimizations 
-Wdeclaration-after-statement -Wold-style-definition 
-Wno-missing-field-initializers -Wno-unused-parameter -Wno-attributes 
-Wno-long-long -Winline -I../include/drm -O3 -mmmx -msse -msse2 -msse3 
-mssse3 -mfpmath=sse -Wall -pipe -D_FILE_OFFSET_BITS=64 
-D_LARGEFILE_SOURCE -mtune=core2 -march=i686 -s -fomit-frame-pointer -MT 
linux.lo -MD -MP -MF .deps/linux.Tpo -c linux.c  -fPIC -DPIC -o 
.libs/linux.o
linux.c:43:22: error: internal.h: No such file or directory
linux.c:95: warning: 'struct kms_driver' declared inside parameter list
linux.c:95: warning: its scope is only this definition or declaration, 
which is probably not what you want
linux.c: In function 'linux_from_sysfs':
linux.c:105: error: implicit declaration of function 'intel_create'
linux.c:105: warning: nested extern declaration of 'intel_create'
linux.c: At top level:
linux.c:202: warning: 'struct kms_driver' declared inside parameter list
linux.c:209: warning: 'struct kms_driver' declared inside parameter list
linux.c:209: warning: no previous prototype for 'linux_create'
linux.c: In function 'linux_create':
linux.c:211: warning: passing argument 2 of 'linux_from_udev' from 
incompatible pointer type
linux.c:202: note: expected 'struct kms_driver **' but argument is of 
type 'struct kms_driver **'
linux.c:214: warning: passing argument 2 of 'linux_from_sysfs' from 
incompatible pointer type
linux.c:95: note: expected 'struct kms_driver **' but argument is of 
type 'struct kms_driver **'
make[2]: *** [linux.lo] Error 1
make[2]: Leaving directory 
`/home/stephan/projects/openelec/build.OpenELEC-intel.i386.devel/libdrm-2.4.18/libkms'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory 
`/home/stephan/projects/openelec/build.OpenELEC-intel.i386.devel/libdrm-2.4.18'
make: *** [all] Error 2
make: Leaving directory 
`/home/stephan/projects/openelec/build.OpenELEC-intel.i386.devel/libdrm-2.4.18'


------------------------------------------------------------------------------
Download Intel&reg; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs 
proactively, and fine-tune applications for parallel performance. 
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--

             reply	other threads:[~2010-02-17 16:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-17 16:45 Stephan Raue [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-02-17 14:37 missing file libkms/internal.h in libdrm-2.4.18 Stephan Raue

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=4B7C1D2D.2070209@gmx.net \
    --to=stephan.raue@gmx.net \
    --cc=dri-devel@lists.sf.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 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.