请问源码包的软件怎样安装?我几乎全部装不了。
大家好，我实在不知在哪个版块提问好，只好发到这里来了。我用linux的日子也不短了，但一直困惑源码包的软件怎样安装,安装不只是先后输入"./configure"、"make"、"make install"那么简单，按这样做，我十有九十安装不了，最多是能通过./configure,make这步就过不了，请教教我该怎么做。 1。最好把系统盘上的开发工具装完整。2。开始编译前最好看看他的INSTALL和readme。
3。编译不过，都会有提示，根据提示解决问题。 我已经安装完整了,也有看软件的INSTALL和readme,但用"readme"中介绍的"./configure"、"make"、"make install"都是装不了的，"readme"也说了其他情况，我看不懂怎样用，请教各位，能介绍正确的操作方法吗？有没有通用可行的操作方法？ ./configure主要工作是检测你的软件系统是否有软件编译和运行所需要的环境，如果检测通过，会根据检测的情况进行配置，生成makefile等文件以提供后一步make时调用。所以源码编译最重要的一步是configure，无法正确编译大都是在这一步挂了。这一步能通过，基本问题不大了。
configure这一步过不了的，中间肯定会有一些错误提示，如xxxx不存在、xxxx失败之类的。根据这些提示解决问题先。
make install这一步一般需要root权限，它会cp编译好的软件到相关的目录中去。如/usr。/usr等这些目录里写目录和文件，普通用户是无法操作的。 我不知道是不是这个情况，我只是说一下我的情况。
我一开始以为，只要在社shell下输入./configure
就可以编译了。可是不行。
原来是要用cd 命令，先进入到你需要编译的目录下，然后再执行编译的命令。
我只是说说，可能你不是这个问题。见笑了。 “make"这步通不过呢？该怎样做？”./configure“也没"make"这步难通过。 make大都是configure没过造成的。
看清configure每一行提示。。。 ....这家伙也发了60多帖子了。
应该知道软件包的依赖问题啊。也应该明白编译工具的依赖问题。。。 积木,你好，我确实不懂编译。rpm包有倚赖问题，我还可以上网找所需的文件和软件包。但源码安装，我碰到问题实在不知怎么办。我也很想尽快从提问人成为解答人，这需要大家帮忙。我现在问./configure这步没通过吗？已经提示”start make now"了，make过不了怎么办？ 嗯，首先你要知道你在编译什么。
然后你要通过readme得到你需要的编译依赖信息--英文是必需的。
然后你要知道编译的路径--有可能是/usr/local/有可能是/usr
还有可能是别的。
编译的时候，因为你可能用到其他的头文件，而这些东西还有可能定义在
pkgconfig 里面，总之你需要确定你的编译器能找到这些东西。
至于编译工具
make
gcc
m4
pkgconfig
等等都是必需的东西了，
./configure 以后，你需要仔细看configure 给出的信息，看看有没有错误和警告。然后解决好相关问题以后再安装。
如果是rpm或者deb的操作系统，
尽量把你自己编译的包安装到
/usr/local下面，这样就可以把对系统的影响降低到最小。
如果出了问题，把编译工具的版本，出错信息，软件包信息都贴出来，基本都应该能解决了。
还有可能是缺少patch的问题。
建议你自己玩儿一把LFS ，这样你会明白的多一点。
嗯，编译安装确实能看出一个人的一些基本功。 编译什么软件?configure文件如果没有做好，make可能也会出问题的。具体要看make给出的错误信息 zhcon的configure就写得很糟糕:evil::evil: 真的出现了依靠包管理系统之后连编译都不会的人了。。。。 还是用例子来说明问题吧。请教cpuinfo 0.4.3怎样安装。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 a while.While running, it prints some
messages telling which features it is checking for.
2. Type `make' to compile the package.
3. Type `make install' to install the programs and any data files and
documentation.
4. You can remove the program binaries and object files from the
source code directory by typing `make clean'.
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.
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.
`--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.
我在安装时，./cofigure完后，make时出现“***warning:linking the shared library libcpuinfo.la against the
***static library ../src/sources/libsources.a is not protable!
make:Leaving directory '/mnt/WinF/lindatabak/down/cpuinfo/src'
make:Leaving directory '/mnt/WinF/lindatabak/down/cpuinfo/src'
make:Entering directory '/mnt/WinF/lindatabak/down/cpuinfo'
make:Leaving directory '/mnt/WinF/lindatabak/down/cpuinfo'
make:Leaving directory '/mnt/WinF/lindatabak/down/cpuinfo'
接着是停止 好长...好头晕..
编译感觉很麻烦的..以前编译过一个EVA的linuxQQ~等了有快半个小时左右才好..等的急死了.现在都是下别人的RPM包..安装快~(.机器配置老菜..)
页:
[1]
2