免费注册 查看新帖 |

Chinaunix

  平台 论坛 博客 文库
12下一页
最近访问板块 发新帖
查看: 5974 | 回复: 14
打印 上一主题 下一主题

[系统安装] 安装tar压缩包按流程走下来没提示操作没出现compelet,求救! [复制链接]

论坛徽章:
0
跳转到指定楼层
1 [收藏(0)] [报告]
发表于 2012-06-09 11:06 |只看该作者 |倒序浏览
连续装了两个包都没成功。
我先说下我的操作流程:
  1. tar zvxf yasm*.tar.gz
  2. cd yasm*
  3. ./configure --prefix=/opt/yasm
复制代码
之后提示了几个依赖关系,都解决后,继续
  1. ./configure --prefix=/opt/yasm
复制代码
之后没有再提示依赖,直到直接跳出命令,也没有显示comptlet
继续
  1. make
复制代码
运行一段时间后,直接跳出命令,没有显示comptlet
继续
  1. make install
复制代码
运行一段时间后,直接跳出命令,没有显示comptlet
但却用不了yasm(我安装这个是为了装mplayer的,之后又重新运行安装mplayer,但仍提示yasm没有安装)
而之前指定的安装yasm的目录 /opt/yasm已经存在,而且里面的目录结构什么的也都齐全
我就纳闷了,又重启了一遍还是不行。。。
求救!

论坛徽章:
13
15-16赛季CBA联赛之同曦
日期:2016-01-28 19:52:032015亚冠之北京国安
日期:2015-10-07 14:28:19NBA常规赛纪念章
日期:2015-05-04 22:32:03处女座
日期:2015-01-15 19:45:44卯兔
日期:2014-10-28 16:17:14白羊座
日期:2014-05-24 15:10:46寅虎
日期:2014-05-10 09:50:35白羊座
日期:2014-03-12 20:52:17午马
日期:2014-03-01 08:37:27射手座
日期:2014-02-19 19:26:54子鼠
日期:2013-11-30 09:03:56狮子座
日期:2013-09-08 08:37:52
2 [报告]
发表于 2012-06-09 11:13 |只看该作者
本帖最后由 ulovko 于 2012-06-09 11:13 编辑

为什么要显示 comptlet ?
把说明书贴上来看看!

论坛徽章:
13
15-16赛季CBA联赛之同曦
日期:2016-01-28 19:52:032015亚冠之北京国安
日期:2015-10-07 14:28:19NBA常规赛纪念章
日期:2015-05-04 22:32:03处女座
日期:2015-01-15 19:45:44卯兔
日期:2014-10-28 16:17:14白羊座
日期:2014-05-24 15:10:46寅虎
日期:2014-05-10 09:50:35白羊座
日期:2014-03-12 20:52:17午马
日期:2014-03-01 08:37:27射手座
日期:2014-02-19 19:26:54子鼠
日期:2013-11-30 09:03:56狮子座
日期:2013-09-08 08:37:52
3 [报告]
发表于 2012-06-09 11:14 |只看该作者
本帖最后由 ulovko 于 2012-06-09 11:15 编辑

FROM: http://blog.chinaunix.net/uid-25256412-id-91403.html
这是以前在centos安装mplayer 的过程!
  1. #
  2. # The Movie Player and front-end for MPlayer HowTo..
  3. #
  4. # http://www.mplayerhq.hu                (Official)
  5. #
  6. # http://www.mplayerhq.hu/MPlayer        (MPlayer)
  7. #
  8. # http://smplayer.sourceforge.net        (SMPlayer)
  9. #

  10. #
  11. # Required Packages
  12. #
  13. # ---[ MPlayer ]---:
  14. #
  15. # all-20071007.tar.bz2        (Binary Codec Packages)
  16. # essential-amd64-20071007.tar.bz2        (For 64-bit OS Codec)
  17. # Abyss-1.7.tar.bz2                (Skin)
  18. # font-arial-iso-8859-1.tar.bz2        (Font)
  19. # mplayer-checkout-snapshot.tar.bz2        (Source Code)
  20. #
  21. # ---[ SMPlayer ]---:
  22. #
  23. # smplayer-0.6.9.tar.bz2        (Source Code)
  24. # smplayer-themes-0.1.20.tar.bz2(Themes Packages)
  25. #

  26. #
  27. # MPlayer Installation
  28. #
  29. # yum install -y gtk+*
  30. #
  31. # mkdir -p ~/.mplayer/
  32. # tar -jxvf mplayer-checkout-snapshot.tar.bz2 -C /usr/local/src/
  33. #
  34. _______________________________
  35. STEP1: Installing Binary Codecs
  36. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  37. #
  38. # mkdir -p /usr/local/lib/codecs
  39. #
  40. # tar -jxvf all-20071007.tar.bz2 -C /usr/local/lib/codecs/
  41. #
  42. # If you are running a 64-bit OS, then this step is must be done:
  43. # tar -jxvf essential-amd64-20071007.tar.bz2 -C /usr/local/lib/codecs
  44. #
  45. __________________________
  46. STEP2: Configuring MPlayer
  47. ~~~~~~~~~~~~~~~~~~~~~~~~~~
  48. #
  49. # ./configure --enable-gui
  50. #
  51. ________________________
  52. STEP3: Compiling MPlayer
  53. ~~~~~~~~~~~~~~~~~~~~~~~~
  54. #
  55. # make; make install
  56. #
  57. ______________________________________
  58. STEP4: Choose an onscreen display font
  59. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  60. #
  61. # cp /usr/share/fonts/chinese/TrueType/uming.ttf ~/.mplayer/subfont.ttf
  62. #or:
  63. # tar -jxvf font-arial-iso-8859-1.tar.bz2 -C ~/.mplayer/font/
  64. #
  65. ____________________________
  66. STEP5: Installing a GUI skin
  67. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  68. #
  69. # tar -jxvf Abyss-1.7.tar.bz2 -C /usr/local/share/mplayer/skins
  70. # cd /usr/local/share/mplayer/skins/; mv Abyss default(ln -s Abyss default)
  71. #or:
  72. # tar -jxvf Abyss-1.7.tar.bz2 -C ~/.mplayer/skins/
  73. # cd ~/.mplayer/skins/ ;mv Abyss default
  74. #

  75. __________________
  76. STEP6: Let's play!
  77. ~~~~~~~~~~~~~~~~~~

  78. That's it for the moment. To start playing movies, open a command line and try

  79.   mplayer <moviefile>
  80. mplayer -playlist ~/Desktop/music.lst -loop 0
  81. or for the GUI

  82.   gmplayer <moviefile>
  83. <SELinux : chcon -Rvt textrel_shlib_t /usr/local/lib/codecs/>
  84. #
  85. # SMPlayer Installation
  86. #

  87. #
  88. # yum install -y qt4 qt4-devel
  89. #

  90. #
  91. # rpmbuild -tb smplayer-0.6.9.tar.bz2
  92. # rpm -ivh /usr/src/redhat/RPMS/ ...omit
  93. #
  94. #
复制代码

论坛徽章:
0
4 [报告]
发表于 2012-06-09 11:21 |只看该作者
回复 2# ulovko


    我就猜到了,第一个回复的肯定是您!
您应该是管理员级别的吧~
言归正传,不是一定要compelet 只是这样起码能让俺们新手知道他安装成功了,呵呵,可我这几次就是楞没成功安装,,,
代码好长,我好好看看

论坛徽章:
13
15-16赛季CBA联赛之同曦
日期:2016-01-28 19:52:032015亚冠之北京国安
日期:2015-10-07 14:28:19NBA常规赛纪念章
日期:2015-05-04 22:32:03处女座
日期:2015-01-15 19:45:44卯兔
日期:2014-10-28 16:17:14白羊座
日期:2014-05-24 15:10:46寅虎
日期:2014-05-10 09:50:35白羊座
日期:2014-03-12 20:52:17午马
日期:2014-03-01 08:37:27射手座
日期:2014-02-19 19:26:54子鼠
日期:2013-11-30 09:03:56狮子座
日期:2013-09-08 08:37:52
5 [报告]
发表于 2012-06-09 11:22 |只看该作者
回复 4# sheldonnerd


    我看你想说 complete 是真。。拼写错误,把README/INSTALL 贴来看看!

论坛徽章:
0
6 [报告]
发表于 2012-06-09 11:24 |只看该作者
回复 2# ulovko


    说明书是指reademe吗?
如果是的话,传不了,这个文件为0字节,,,

论坛徽章:
0
7 [报告]
发表于 2012-06-09 11:27 |只看该作者
回复 5# ulovko


    不好意思,英文着实差劲,,
下面是install文件内容:
==================================
Basic Installation
==================

   These are generic installation instructions.

   The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation.  It uses
those values to create a `Makefile' in each directory of the package.
It may also create one or more `.h' files containing system-dependent
definitions.  Finally, it creates a shell script `config.status' that
you can run in the future to recreate the current configuration, a file
`config.cache' that saves the results of its tests to speed up
reconfiguring, and a file `config.log' containing compiler output
(useful mainly for debugging `configure').

   If you need to do unusual things to compile the package, please try
to figure out how `configure' could check whether to do them, and mail
diffs or instructions to the address given in the `README' so they can
be considered for the next release.  If at some point `config.cache'
contains results you don't want to keep, you may remove or edit it.

   The file `configure.in' is used to create `configure' by a program
called `autoconf'.  You only need `configure.in' if you want to change
it or regenerate `configure' using a newer version of `autoconf'.

The simplest way to compile this package is:

  1. `cd' to the directory containing the package's source code and type
     `./configure' to configure the package for your system.  If you're
     using `csh' on an old version of System V, you might need to type
     `sh ./configure' instead to prevent `csh' from trying to execute
     `configure' itself.

     Running `configure' takes awhile.  While running, it prints some
     messages telling which features it is checking for.

  2. Type `make' to compile the package.

  3. Optionally, type `make check' to run any self-tests that come with
     the package.

  4. Type `make install' to install the programs and any data files and
     documentation.

  5. You can remove the program binaries and object files from the
     source code directory by typing `make clean'.  To also remove the
     files that `configure' created (so you can compile the package for
     a different kind of computer), type `make distclean'.  There is
     also a `make maintainer-clean' target, but that is intended mainly
     for the package's developers.  If you use it, you may have to get
     all sorts of other programs in order to regenerate files that came
     with the distribution.

Compilers and Options
=====================

   Some systems require unusual options for compilation or linking that
the `configure' script does not know about.  You can give `configure'
initial values for variables by setting them in the environment.  Using
a Bourne-compatible shell, you can do that on the command line like
this:
     CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure

Or on systems that have the `env' program, you can do it like this:
     env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure

Compiling For Multiple Architectures
====================================

   You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory.  To do this, you must use a version of `make' that
supports the `VPATH' variable, such as GNU `make'.  `cd' to the
directory where you want the object files and executables to go and run
the `configure' script.  `configure' automatically checks for the
source code in the directory that `configure' is in and in `..'.

   If you have to use a `make' that does not supports the `VPATH'
variable, you have to compile the package for one architecture at a time
in the source code directory.  After you have installed the package for
one architecture, use `make distclean' before reconfiguring for another
architecture.

Installation Names
==================

   By default, `make install' will install the package's files in
`/usr/local/bin', `/usr/local/man', etc.  You can specify an
installation prefix other than `/usr/local' by giving `configure' the
option `--prefix=PATH'.

   You can specify separate installation prefixes for
architecture-specific files and architecture-independent files.  If you
give `configure' the option `--exec-prefix=PATH', the package will use
PATH as the prefix for installing programs and libraries.
Documentation and other data files will still use the regular prefix.

   In addition, if you use an unusual directory layout you can give
options like `--bindir=PATH' to specify different values for particular
kinds of files.  Run `configure --help' for a list of the directories
you can set and what kinds of files go in them.

   If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving `configure' the
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.

Optional Features
=================

   Some packages pay attention to `--enable-FEATURE' options to
`configure', where FEATURE indicates an optional part of the package.
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
is something like `gnu-as' or `x' (for the X Window System).  The
`README' should mention any `--enable-' and `--with-' options that the
package recognizes.

   For packages that use the X Window System, `configure' can usually
find the X include and library files automatically, but if it doesn't,
you can use the `configure' options `--x-includes=DIR' and
`--x-libraries=DIR' to specify their locations.

Specifying the System Type
==========================

   There may be some features `configure' can not figure out
automatically, but needs to determine by the type of host the package
will run on.  Usually `configure' can figure that out, but if it prints
a message saying it can not guess the host type, give it the
`--host=TYPE' option.  TYPE can either be a short name for the system
type, such as `sun4', or a canonical name with three fields:
     CPU-COMPANY-SYSTEM

See the file `config.sub' for the possible values of each field.  If
`config.sub' isn't included in this package, then this package doesn't
need to know the host type.

   If you are building compiler tools for cross-compiling, you can also
use the `--target=TYPE' option to select the type of system they will
produce code for and the `--build=TYPE' option to select the type of
system on which you are compiling the package.

Sharing Defaults
================

   If you want to set default values for `configure' scripts to share,
you can create a site shell script called `config.site' that gives
default values for variables like `CC', `cache_file', and `prefix'.
`configure' looks for `PREFIX/share/config.site' if it exists, then
`PREFIX/etc/config.site' if it exists.  Or, you can set the
`CONFIG_SITE' environment variable to the location of the site script.
A warning: not all `configure' scripts look for a site script.

Operation Controls
==================

   `configure' recognizes the following options to control how it
operates.

`--cache-file=FILE'
     Use and save the results of the tests in FILE instead of
     `./config.cache'.  Set FILE to `/dev/null' to disable caching, for
     debugging `configure'.

`--help'
     Print a summary of the options to `configure', and exit.

`--quiet'
`--silent'
`-q'
     Do not print messages saying which checks are being made.  To
     suppress all normal output, redirect it to `/dev/null' (any error
     messages will still be shown).

`--srcdir=DIR'
     Look for the package's source code in directory DIR.  Usually
     `configure' can determine that directory automatically.

`--version'
     Print the version of Autoconf used to generate the `configure'
     script, and exit.

`configure' also accepts some other, not widely useful, options.

论坛徽章:
0
8 [报告]
发表于 2012-06-09 11:32 |只看该作者
回复 5# ulovko


    3Q,又学到了一招,安装程序看install
不过看这个install 发现我的安装过程是对的啊,可怎么结果就是不对呢?

论坛徽章:
4
CU大牛徽章
日期:2013-03-13 15:29:07CU大牛徽章
日期:2013-03-13 15:29:49CU大牛徽章
日期:2013-03-13 15:30:192015年迎新春徽章
日期:2015-03-04 09:57:09
9 [报告]
发表于 2012-06-10 12:05 |只看该作者
楼主安装成功了没?
whereis yasm看看能找到不

论坛徽章:
0
10 [报告]
发表于 2012-06-10 14:15 |只看该作者
本帖最后由 sheldonnerd 于 2012-06-10 14:16 编辑

回复 9# dooros


    嗯,成功了。不知道原因,今天按昨天的步骤重装了一遍居然成功了。。。
谢谢关注哈~
问个另外问题,为什么我安装的deadbeef不能播放音乐呢?连mp3都读取不了。如果要下载插件的话,要下载哪些呢?我看官网上有好多,下了几个都不管用。不知为何,系统自带的音视频播放器也无法播放任何音视频,也无法下载插件。
求救!谢谢!
我的系统是CENTOS 6.2
您需要登录后才可以回帖 登录 | 注册

本版积分规则 发表回复

  

北京盛拓优讯信息技术有限公司. 版权所有 京ICP备16024965号-6 北京市公安局海淀分局网监中心备案编号:11010802020122 niuxiaotong@pcpop.com 17352615567
未成年举报专区
中国互联网协会会员  联系我们:huangweiwei@itpub.net
感谢所有关心和支持过ChinaUnix的朋友们 转载本站内容请注明原作者名及出处

清除 Cookies - ChinaUnix - Archiver - WAP - TOP