./configure后。。。谁能帮忙看下这个。。
Tofloor
poster avatar
132******75
deepin
2013-03-30 03:30
Author
在intel开源驱动网站下载到xf86-video-intel的tar包
然后解压后准备源码安装
突然想到论坛上因为乱搞驱动挂掉的众人,于是./configure了一下
看到这么大一串。。。有点麻。。。这个。。。到底能不能装?


root@fc-HP-500-Notebook-PC:/tmp/xf86-video-intel-2.20.12# ./configurechecking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking for gcc option to accept ISO C99... -std=gnu99
checking how to run the C preprocessor... gcc -std=gnu99 -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking whether __clang__ is declared... no
checking whether __INTEL_COMPILER is declared... no
checking whether __SUNPRO_C is declared... no
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for a sed that does not truncate output... /bin/sed
checking if gcc -std=gnu99 supports -Werror=unknown-warning-option... no
checking if gcc -std=gnu99 supports -Werror=unused-command-line-argument... no
checking if gcc -std=gnu99 supports-Wall... yes
checking if gcc -std=gnu99 supports-Wpointer-arith... yes
checking if gcc -std=gnu99 supports-Wmissing-declarations... yes
checking if gcc -std=gnu99 supports-Wformat=2... yes
checking if gcc -std=gnu99 supports-Wstrict-prototypes... yes
checking if gcc -std=gnu99 supports-Wmissing-prototypes... yes
checking if gcc -std=gnu99 supports-Wnested-externs... yes
checking if gcc -std=gnu99 supports-Wbad-function-cast... yes
checking if gcc -std=gnu99 supports-Wold-style-definition... yes
checking if gcc -std=gnu99 supports-Wdeclaration-after-statement... yes
checking if gcc -std=gnu99 supports-Wunused... yes
checking if gcc -std=gnu99 supports-Wuninitialized... yes
checking if gcc -std=gnu99 supports-Wshadow... yes
checking if gcc -std=gnu99 supports-Wcast-qual... yes
checking if gcc -std=gnu99 supports-Wmissing-noreturn... yes
checking if gcc -std=gnu99 supports-Wmissing-format-attribute... yes
checking if gcc -std=gnu99 supports-Wredundant-decls... yes
checking if gcc -std=gnu99 supports-Werror=implicit... yes
checking if gcc -std=gnu99 supports-Werror=nonnull... yes
checking if gcc -std=gnu99 supports-Werror=init-self... yes
checking if gcc -std=gnu99 supports-Werror=main... yes
checking if gcc -std=gnu99 supports-Werror=missing-braces... yes
checking if gcc -std=gnu99 supports-Werror=sequence-point... yes
checking if gcc -std=gnu99 supports-Werror=return-type... yes
checking if gcc -std=gnu99 supports-Werror=trigraphs... yes
checking if gcc -std=gnu99 supports-Werror=array-bounds... yes
checking if gcc -std=gnu99 supports-Werror=write-strings... yes
checking if gcc -std=gnu99 supports-Werror=address... yes
checking if gcc -std=gnu99 supports-Werror=int-to-pointer-cast... yes
checking if gcc -std=gnu99 supports-Werror=pointer-to-int-cast... yes
checking if gcc -std=gnu99 supports-pedantic... yes
checking if gcc -std=gnu99 supports-Werror... yes
checking if gcc -std=gnu99 supports-Werror=attributes... yes
Package xorg-macros was not found in the pkg-config search path.
Perhaps you should add the directory containing `xorg-macros.pc'
to the PKG_CONFIG_PATH environment variable
No package 'xorg-macros' found
checking whether make supports nested variables... yes
checking how to print strings... printf
checking for a sed that does not truncate output... (cached) /bin/sed
checking for fgrep... /bin/grep -F
checking for ld used by gcc -std=gnu99... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking how to convert i686-pc-linux-gnu file names to i686-pc-linux-gnu format... func_convert_file_noop
checking how to convert i686-pc-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc -std=gnu99 object... ok
checking for sysroot... no
checking for mt... mt
checking if mt is a manifest tool... no
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc -std=gnu99 supports -fno-rtti -fno-exceptions... no
checking for gcc -std=gnu99 option to produce PIC... -fPIC -DPIC
checking if gcc -std=gnu99 PIC flag -fPIC -DPIC works... yes
checking if gcc -std=gnu99 static flag -static works... yes
checking if gcc -std=gnu99 supports -c -o file.o... yes
checking if gcc -std=gnu99 supports -c -o file.o... (cached) yes
checking whether the gcc -std=gnu99 linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... 64
checking for UDEV... no
checking for X11... no
checking sys/sysinfo.h usability... yes
checking sys/sysinfo.h presence... yes
checking for sys/sysinfo.h... yes
checking whether to include SNA support... auto
checking whether to include UXA support... yes
checking for DRMINTEL... no
configure: error: Package requirements (libdrm_intel >= 2.4.29) were not met:

No package 'libdrm_intel' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables DRMINTEL_CFLAGS
and DRMINTEL_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
Reply Favorite View the author
All Replies
cxbii
deepin
2013-03-30 03:45
#1
我没装过,不敢发布评论
Reply View the author
zhtengw
deepin
2013-03-30 08:39
#2
您好,首先回答一下您的问题,您的系统当然可以编译安装xf86-video-intel,configure的时候会检查您的系统环境满不满足编译需要,并根据编译选项生成一些文件,这会直接影响编译出来的软件,而您给出的错误提示只不过是说编译需要的libdrm_intel包没在您的系统安装,这个东西一般由libdrm提供,libdrm是一个直接渲染管理库,用于启用显卡的硬件加速,如果是编译需要,在一些发行版里您可能还需要安装libdrm-devel。而编译一个库,跟您的电脑有没有这个硬件,或者有没有这个特性关系不大,只要有编译环境,都可以编译安装。

接着,我想给您一些忠告:
我强烈地[color=#BF0000:9jr6rvat]不建议[/color:9jr6rvat]您自己编译这个东西。
按我的体验和理解,我说说我认为有必要自己编译的几种情况:
1、这个软件需要开启或关闭某些编译选项才能在您的机器上正常工作,而发行版默认编译出来的东西并不满足;
2、软件在您的机器上出现了bug,您得到或自己写了一些patch,想试试可不可以修复问题;
3、您给软件增加了一些新特性,想在自己的机器上试试;
4、您所用的发行版没有提供这个软件的打包;
……
如果需要自己编译东西的话,那最好还要学学自己所用发行版的打包,因为独立于包管理的文件太多的话,会导致系统文件比较乱,当您用包管理升级系统的时候,很可能会出问题。

从您的提问来看,您对编译软件还不是很熟悉,应该也不知道怎样打包软件,所以还是建议您,直接安装发行版提供的xf86-video-intel,一般发行版默认编译的包都适用于大部分硬件,出现问题很可能是因为您的配置文件没写好(比如xorg.conf),您不妨将自己遇到的问题google一下,看看有没有解决方法,也可以将问题发到论坛,大家集思广益。最好不要盲目地去编译软件,不一定能解决问题,而且浪费时间。

一家之言,仅作参考,望谅
Reply View the author
a287740928
deepin
2013-03-30 11:38
#3
您好,首先回答一下您的问题,您的系统当然可以编译安装xf86-video-intel,configure的时候会检查您的系统环境满不满足编译需要,并根据编译选项生成一些文件,这会直接影响编译出来的软件,而您给出的错误提示只不过是说编译需要的libdrm_intel包没在您的系统安装,这个东西一般由libdrm提供,libdrm是一个直接渲染管理库,用于启用显卡的硬件加速,如果是编译需要,在一些发行版里您可能还需要安装libdrm-devel。而编译一个库,跟您的电脑有没有这个硬件,或者有没有这个特性关系不大,只要有编译环境,都可以编译安装。

接着,我想给您一些忠告:
我强烈地[color=#BF0000:1xvw5mpe]不建议[/color:1xvw5mpe]您自己编译这个东西。
按我的体验和理解,我说说我认为有必要自己编译的几种情况:
1、这个软件需要开启或关闭某些编译选项才能在您的机器上正常工作,而发行版默认编译出来的东西并不满足;
2、软件在您的机器上出现了bug,您得到或自己写了一些patch,想试试可不可以修复问题;
3、您给软件增加了一些新特性,想在自己的机器上试试;
……
如果需要自己编译东西的话,那最好还要学学自己所用发行版的打包,因为独立于包管理的文件太多的话,会导致系统文件比较乱,当您用包管理升级系统的时候,很可能会出问题。

从您的提问来看,您对编译软件还不是很熟悉,应该也不知道怎样打包软件,所以还是建议您,直接安装发行版提供的xf86-video-intel,一般发行版默认编译的包都适用于大部分硬件,出现问题很可能是因为您的配置文件没写好(比如xorg.conf),您不妨将自己遇到的问题google一下,看看有没有解决方法,也可以将问题发到论坛,大家集思广益。最好不要盲目地去编译软件,不一定能解决问题,而且浪费时间。

一家之言,仅作参考,望谅
好牛擦,学习了!
Reply View the author
cxbii
deepin
2013-03-30 16:41
#4
这帖子。。会移动到系统讨论
本板块只讨论安装系统。。。请见谅
Reply View the author