【已解决】libva编译出现奇怪问题,总是没法成功安装

Totem,mplayer,sopcast,realplayer,bmp
回复
tinyDevil
帖子: 17
注册时间: 2012-08-07 11:51

【已解决】libva编译出现奇怪问题,总是没法成功安装

#1

帖子 tinyDevil » 2012-08-29 11:06

代码: 全选

[root@localhost libva-1.0.15]# ./configure 
checking 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... gawk
checking whether make sets $(MAKE)... yes
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking how to print strings... printf
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 a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /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... 1966080
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 object... ok
checking for sysroot... no
checking for mt... no
checking if : is a manifest tool... no
checking how to run the C preprocessor... gcc -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 for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... no
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc 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 gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking dependency style of gcc... (cached) gcc3
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking for ld used by g++... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works... yes
checking if g++ static flag -static works... no
checking if g++ supports -c -o file.o... yes
checking if g++ supports -c -o file.o... (cached) yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... (cached) GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking for ANSI C header files... (cached) yes
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... 64
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for X11... yes
checking for XEXT... yes
checking for XFIXES... yes
checking for DRM... yes
checking GL/gl.h usability... yes
checking GL/gl.h presence... yes
checking for GL/gl.h... yes
checking GL/glx.h usability... yes
checking GL/glx.h presence... yes
checking for GL/glx.h... yes
checking for glXCreateContext in -lGL... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating debian.upstream/Makefile
config.status: creating va/Makefile
config.status: creating va/va_version.h
config.status: creating va/x11/Makefile
config.status: creating va/glx/Makefile
config.status: creating va/egl/Makefile
config.status: creating va/dummy/Makefile
config.status: creating dummy_drv_video/Makefile
config.status: creating test/Makefile
config.status: creating test/basic/Makefile
config.status: creating test/decode/Makefile
config.status: creating test/putsurface/Makefile
config.status: creating test/encode/Makefile
config.status: creating test/vainfo/Makefile
config.status: creating pkgconfig/libva-egl.pc
config.status: creating pkgconfig/libva-glx.pc
config.status: creating pkgconfig/libva-tpi.pc
config.status: creating pkgconfig/libva-x11.pc
config.status: creating pkgconfig/libva.pc
config.status: creating pkgconfig/Makefile
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands
config.status: executing libtool commands

libva - 1.0.15 (VA-API 0.32.0)

 � Global :
     Prefix: /usr/local

 � Drivers: dummy 
 � Winsys : x11 egl glx 
[root@localhost libva-1.0.15]# 
 
这样算编译成功么?
之后make和make install都是没问题的
但是用rpm -qa libva查询,却没有安装
而且安装libva-driver-intel时,也说需要先安装libva
上次由 tinyDevil 在 2012-08-30 16:57,总共编辑 2 次。
头像
lxr1234
帖子: 721
注册时间: 2009-04-10 11:15
来自: 三民主义国国民权利省我的选择市中共下台镇

Re: 【求助】libva编译出现奇怪问题

#2

帖子 lxr1234 » 2012-08-29 12:59

viewtopic.php?f=74&t=286315
你没打包而已
强烈反对M$的ARM Secure Boot 锁定要求,大家请签名反对
http://www.fsf.org/campaigns/secure-boo ... cted-boot/
tinyDevil
帖子: 17
注册时间: 2012-08-07 11:51

Re: 【求助】libva编译出现奇怪问题

#3

帖子 tinyDevil » 2012-08-29 14:25

lxr1234 写了:viewtopic.php?f=74&t=286315
你没打包而已
如何打包?
你的帖子我看过了,我用的是centos6.3的,所以好像不适用
tinyDevil
帖子: 17
注册时间: 2012-08-07 11:51

Re: 【求助】libva编译出现奇怪问题

#4

帖子 tinyDevil » 2012-08-29 14:26

lxr1234 写了:viewtopic.php?f=74&t=286315
你没打包而已
不懂。
怎么打包?
你的帖子我看过了,不过我用的是centos6.3,所以貌似不是很适用
头像
lxr1234
帖子: 721
注册时间: 2009-04-10 11:15
来自: 三民主义国国民权利省我的选择市中共下台镇

Re: 【求助】libva编译出现奇怪问题,总是没法成功安装

#5

帖子 lxr1234 » 2012-08-30 0:53

rpm包自己google,我只是给你一个思路
强烈反对M$的ARM Secure Boot 锁定要求,大家请签名反对
http://www.fsf.org/campaigns/secure-boo ... cted-boot/
头像
cuihao
帖子: 4793
注册时间: 2008-07-24 11:33
来自: 郑州
联系:

Re: 【求助】libva编译出现奇怪问题,总是没法成功安装

#6

帖子 cuihao » 2012-08-30 9:08

自己make的包管理器不认识的。

要么下载现成的rpm,要么接着自己编译(脏死了)。
求人不如求它仨: 天蓝的Wiki 屎黄的Wiki 绿
Site: CUIHAO.TK    Twitter: @cuihaoleo
Machine: Athlon64 X2 5200+ / 2x2GB DDR2-800 / GeForce GTS 450
AD: ~まだ見ぬ誰かの笑顔のために~
tinyDevil
帖子: 17
注册时间: 2012-08-07 11:51

Re: 【已解决】libva编译出现奇怪问题,总是没法成功安装

#7

帖子 tinyDevil » 2012-08-30 16:57

非常感谢。
换RPM包就没问题了
不过。mplayer又出问题了……
回复