Home > No Such > Gentoo Libdrm Error

Gentoo Libdrm Error

Contents

I'll repeat my request - please update documentation, provide warnings and deprecation _period_. Unfortunately, the same ebuild depends on >=x11-libs/libdrm-2.4.19. defining _BSD_SOURCE gives you a pure BSD environment without some of the features enabled by, e.g., _XOPEN_SOURCE). x86_64-pc-linux-gnu-ar checking for x86_64-pc-linux-gnu-strip...

i686-pc-linux-gnu
checking for a sed that does not truncate output... /bin/sed /> checking for a BSD-compatible install... /usr/lib/portage/python3.4/ebuild-helpers/xattr/install -c
checking whether build environment is sane... done! >>> Verifying ebuild manifests >>> Emerging (1 of 1) x11-libs/libdrm-2.4.6 * libdrm-2.4.6.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] Compile, install and qmerge $ sudo ebuild/usr/portage/x11-libs/libdrm/libdrm-2.4.31.ebuild compile $ sudo ebuild/usr/portage/x11-libs/libdrm/libdrm-2.4.31.ebuild install $ sudo ebuild/usr/portage/x11-libs/libdrm/libdrm-2.4.31.ebuild qmerge The generated executable file will replace the original ones. If you want any kind of acceleration with nouveau, emerge x11-base/nouveau-drm or enable CONFIG_DRM_NOUVEAU in the kernel. check these guys out

Fatal Error: Drm.h: No Such File Or Directory

This > driver is now in the kernel itself. wait what ? This > driver is now in the kernel itself. yes checking whether x86_64-pc-linux-gnu-gcc supports -Wold-style-definition...

yes checking whether x86_64-pc-linux-gnu-gcc supports -Wwrite-strings... yes checking for x86_64-pc-linux-gnu-gcc option to accept ISO C89... Comment 21 Emil Velikov 2016-04-30 19:59:54 UTC Should have mentioned it earlier - I thought the more portable thing was to use AC_HEADER_MAJOR. yes checking for sys/stat.h...

Thanks ! Usr Include Xf86drm H 40 17 Fatal Error Drm H No Such File Or Directory yes checking whether x86_64-pc-linux-gnu-gcc supports -Wpointer-arith... displaylink-mlukaszek commented Jan 13, 2016 Hi Adam, Check where your drm.h from libdrm is installed. http://gentoobrowse.randomdan.homeip.net/package/x11-drivers/xf86-video-qxl checking for suffix of object files...

or do you want me to send it to the list? yes checking whether x86_64-pc-linux-gnu-gcc accepts -g... so I guess that narrows down the culprit. yes checking whether x86_64-pc-linux-gnu-gcc supports -Wstrict-prototypes...

Usr Include Xf86drm H 40 17 Fatal Error Drm H No Such File Or Directory

yes
checking whether make supports nested variables... https://github.com/DisplayLink/evdi/issues/6 Do you want to commit it... Fatal Error: Drm.h: No Such File Or Directory ok checking how to run the C preprocessor... Uapi/drm/drm.h: No Such File Or Directory Can anyone share a link with discussion behind this decision ?

the Gentoo changes are only in an opt-in dev-only build, so it too isn't hitting people randomly. Contact Gossamer Threads Web Applications & Managed Hosting Powered by Gossamer Threads Inc. The unpacked source file would be in the /tmp folder. Obviously waiting for a man-pages release would be a serious overkill (afaict it will be within ~4 months).

This driver is now in the kernel itself. Comment 18 Matt Turner 2016-04-21 05:10:12 UTC I guess you can think of this as the deprecation period. MODPOST 1 modules CC /home/nuclear/evdi/module/evdi.mod.o LD [M] /home/nuclear/evdi/module/evdi.ko make[2]: Leaving directory '/usr/src/linux-4.2.1' make[1]: Leaving directory '/home/nuclear/evdi/module' make -C library make[1]: Entering directory '/home/nuclear/evdi/library' cc -std=gnu99 -fPIC -I../module -c -o evdi_lib.o evdi_lib.c kshade 2016-01-17 08:15:23 UTC #27 Installed Steam in a basic Debian stable chroot on my Void laptop, Steam can log in when running in it.

yes checking if libtool supports shared libraries... Check to see what those simlinks are actually pointing to. emailgrant at gmail May21,2010,4:42PM Post #14 of 16 (6058 views) Permalink Re: Re: nouveau-drm compile failure [In reply to] >>>> Google says the yes checking whether the shell understands "+="...

yes checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B checking the name lister (/usr/bin/nm -B) interface...

I've pushed the AC_HEADER_MAJOR patch to master. o checking whether we are using the GNU C compiler... yes checking whether x86_64-pc-linux-gnu-gcc supports -Werror-implicit-function-declaration... Digest, fetch, unpack $ sudo ebuild/usr/portage/x11-libs/libdrm/libdrm-2.4.31.ebuild digest $ sudo ebuild/usr/portage/x11-libs/libdrm/libdrm-2.4.31.ebuild fetch $ sudo ebuild/usr/portage/x11-libs/libdrm/libdrm-2.4.31.ebuild unpack 3.

It might be in /usr/include/libdrm, in which case you should probably edit the header files that include drm.h - for userspace library code only. codifies 2016-01-16 12:10:40 UTC #24 I tried copying across the firmware that gentoo was using for the wifi, after starting from cold I verified that the firmware was in use, and..... I had to switch back to nvidia proprietary as mouveau had every imaginable feature I want (especially how to deal with two monitors in a sane way) and the features functioned nouveau-drm was used before that > driver moved into the Linux kernel together with the other DRM drivers. > > Also, as a consequence, trying to use nouveau-drm means you're getting

yes checking for inttypes.h... Can I > specify a path in xorg.conf, or does anyone know what the problem > might be? Are those options the reason for the compile failure? - Grant realnc at arcor May20,2010,10:32AM Post #2 of 16 (6069 views) Permalink Re: nouveau-drm compile failure [In reply to] On 05/20/2010 07:56 PM, Running Steam with LD_LIBRARY_PATH=/opt/debian/usr/lib/i386-linux-gnu/ makes it work though, so the culprit has to be the Void equivalent of one of those: libGL.so.1.2.0 libLLVM-3.5.so.1 libX11-xcb.so.1.0.0 libX11.so.6.3.0 libXau.so.6.0.0 libXdamage.so.1.1.0 libXdmcp.so.6.0.0 libXext.so.6.4.0 libXfixes.so.3.1.0 libXinerama.so.1.0.0

Maybe someone else knows? emailgrant at gmail May22,2010,1:42PM Post #16 of 16 (6044 views) Permalink Re: Re: nouveau-drm compile failure [In reply to] >> I can now start X via the >> nouveau

© 2017 imagextension.com