安装个软件又有问题了~请教老大经验！先拜了！有截图~
如图： 附带个问题~gnome和Nautilus的关系是什么？Nautilus是集成在gnome桌面管理器里面的文件管理器？我这样说对吗？ :oops: 试试 ./install-sh Nautilus是集成在gnome桌面管理器里面的文件管理器 :P 老大~~~~~~你来我就有希望了~~~~我试去~~~~~（之前我看了install，里面说./configure或者sh ./configure）~马上回来 # lsABOUT-NLS config.sub gaim.spec news
acinclude.m4 configure gaim.spec.in pixmaps
aclocal.m4 configure.ac hacking plugins
authors copying install po
ChangeLog COPYRIGHT install-sh PROGRAMMING_NOTES
ChangeLog.win32depcomp intl readme
compile doc licq2gaim.pl README.mingw
confdefs.h Doxyfile.in ltmain.sh setup-gettext
config.guess gaim2blt.pl Makefile.am sounds
config.h gaim.apspec.in Makefile.in src
config.h.in gaim.desktop Makefile.mingwversion
config.h.mingw gaim-installer.nsimissing VERSION.in
config.log gaim.pc.in mkinstalldirs
# ./install-sh
./install-sh: no input file specified.
不行~ 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.ac' is used to create `configure' by a program
called `autoconf'.You only need `configure.ac' 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. up ./configure 刀老大~~你没看我的图挖~~~~ :evil::evil: 刀老大~~你没看我的图挖~~~~ :evil::evil:
:oops::oops:
重下一个其他版本的试试 :P:P 刀老大~~你没看我的图挖~~~~ :evil::evil:
:oops::oops:
重下一个其他版本的试试 :P:P
8O8O ~~没有其他办法了？这个是什么原因出的错呢？渴求知识啊~ 刀老大~~你没看我的图挖~~~~ :evil::evil:
:oops::oops:
重下一个其他版本的试试 :P:P
8O8O ~~没有其他办法了？这个是什么原因出的错呢？渴求知识啊~
下载之后是否校验过MD5码？？
有可能下载过程中出错！
还有他的输出在config.log文件里面，到那里看看有什么问题说明。
还有可以试试CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure 看看是否有用！ config.log
=============
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by gaim configure 1.1.1, which was
generated by GNU Autoconf 2.59.Invocation command line was
$ ./configure
## --------- ##
## Platform. ##
## --------- ##
hostname = localhost.localdomain
uname -m = i686
uname -r = 2.4.20-8
uname -s = Linux
uname -v = #1 Thu Mar 13 17:18:24 EST 2003
/usr/bin/uname -p = unknown
/bin/uname -X = unknown
/bin/arch = i686
/usr/bin/arch -k = unknown
/usr/convex/getsysinfo = unknown
hostinfo = unknown
/bin/machine = unknown
/usr/bin/oslevel = unknown
/bin/universe = unknown
PATH: /usr/local/sbin
PATH: /usr/local/bin
PATH: /sbin
PATH: /bin
PATH: /usr/sbin
PATH: /usr/bin
PATH: /usr/X11R6/bin
PATH: /root/bin
## ----------- ##
## Core tests. ##
## ----------- ##
configure:1587: error: cannot find install-sh or install.sh in .. ../.. ../../..
## ---------------- ##
## Cache variables. ##
## ---------------- ##
ac_cv_env_CC_set=
ac_cv_env_CC_value=
ac_cv_env_CFLAGS_set=
ac_cv_env_CFLAGS_value=
ac_cv_env_CPPFLAGS_set=
ac_cv_env_CPPFLAGS_value=
ac_cv_env_CPP_set=
ac_cv_env_CPP_value=
ac_cv_env_CXXCPP_set=
ac_cv_env_CXXCPP_value=
ac_cv_env_CXXFLAGS_set=
ac_cv_env_CXXFLAGS_value=
ac_cv_env_CXX_set=
ac_cv_env_CXX_value=
ac_cv_env_F77_set=
ac_cv_env_F77_value=
ac_cv_env_FFLAGS_set=
ac_cv_env_FFLAGS_value=
ac_cv_env_LDFLAGS_set=
ac_cv_env_LDFLAGS_value=
ac_cv_env_build_alias_set=
ac_cv_env_build_alias_value=
ac_cv_env_host_alias_set=
ac_cv_env_host_alias_value=
ac_cv_env_target_alias_set=
ac_cv_env_target_alias_value=
## ----------------- ##
## Output variables. ##
## ----------------- ##
ACLOCAL=''
ALLOCA=''
AMDEPBACKSLASH=''
AMDEP_FALSE=''
AMDEP_TRUE=''
AMTAR=''
AO_CFLAGS=''
AO_LIBS=''
AR=''
AUDIOFILE_CFLAGS=''
AUDIOFILE_CONFIG=''
AUDIOFILE_LIBS=''
AUTOCONF=''
AUTOHEADER=''
AUTOMAKE=''
AWK=''
BINRELOC_CFLAGS=''
BINRELOC_LIBS=''
BUILD_GEVOLUTION_FALSE=''
BUILD_GEVOLUTION_TRUE=''
BUILD_INCLUDED_LIBINTL=''
CATOBJEXT=''
CC=''
CCDEPMODE=''
CFLAGS=''
CPP=''
CPPFLAGS=''
CXX=''
CXXCPP=''
CXXDEPMODE=''
CXXFLAGS=''
CYGPATH_W=''
DATADIRNAME=''
DEBUG_CFLAGS=''
DEFS=''
DEPDIR=''
DISTRIB_FALSE=''
DISTRIB_TRUE=''
DYNALOADER_A=''
DYNAMIC_GG_FALSE=''
DYNAMIC_GG_TRUE=''
DYNAMIC_IRC_FALSE=''
DYNAMIC_IRC_TRUE=''
DYNAMIC_JABBER_FALSE=''
DYNAMIC_JABBER_TRUE=''
DYNAMIC_MSN_FALSE=''
DYNAMIC_MSN_TRUE=''
DYNAMIC_NAPSTER_FALSE=''
DYNAMIC_NAPSTER_TRUE=''
DYNAMIC_NOVELL_FALSE=''
DYNAMIC_NOVELL_TRUE=''
DYNAMIC_OSCAR_FALSE=''
DYNAMIC_OSCAR_TRUE=''
DYNAMIC_PRPLS=''
DYNAMIC_RENDEZVOUS_FALSE=''
DYNAMIC_RENDEZVOUS_TRUE=''
DYNAMIC_SILC_FALSE=''
DYNAMIC_SILC_TRUE=''
DYNAMIC_TOC_FALSE=''
DYNAMIC_TOC_TRUE=''
DYNAMIC_TREPIA_FALSE=''
DYNAMIC_TREPIA_TRUE=''
DYNAMIC_YAHOO_FALSE=''
DYNAMIC_YAHOO_TRUE=''
DYNAMIC_ZEPHYR_FALSE=''
DYNAMIC_ZEPHYR_TRUE=''
ECHO='echo'
ECHO_C=''
ECHO_N='-n'
ECHO_T=''
EGREP=''
EVOLUTION_ADDRESSBOOK_CFLAGS=''
EVOLUTION_ADDRESSBOOK_LIBS=''
EXEEXT=''
EXTERNAL_LIBZEPHYR_FALSE=''
EXTERNAL_LIBZEPHYR_TRUE=''
F77=''
FFLAGS=''
GENCAT=''
GLIBC21=''
GLIB_CFLAGS=''
GLIB_GENMARSHAL=''
GLIB_LIBS=''
GLIB_MKENUMS=''
GMSGFMT=''
GNUTLS_CFLAGS=''
GNUTLS_LIBS=''
GOBJECT_QUERY=''
GTKSPELL_CFLAGS=''
GTKSPELL_LIBS=''
GTK_CFLAGS=''
GTK_LIBS=''
HAVE_ASPRINTF=''
HAVE_POSIX_PRINTF=''
HAVE_SNPRINTF=''
HAVE_WPRINTF=''
INSTALL_DATA=''
INSTALL_PROGRAM=''
INSTALL_SCRIPT=''
INSTALL_STRIP_PROGRAM=''
INSTOBJEXT=''
INTLBISON=''
INTLLIBS=''
INTLOBJS=''
INTL_LIBTOOL_SUFFIX_PREFIX=''
KRB4_CFLAGS=''
KRB4_LDFLAGS=''
KRB4_LIBS=''
LDADD=''
LDFLAGS=''
LIBICONV=''
LIBINTL=''
LIBOBJS=''
LIBPERL_A=''
LIBS=''
LIBTOOL=''
LN_S=''
LTLIBICONV=''
LTLIBINTL=''
LTLIBOBJS=''
MAKEINFO=''
MKINSTALLDIRS=''
MSGFMT=''
MSGMERGE=''
NSS_CFLAGS=''
NSS_LIBS=''
OBJEXT=''
PACKAGE=''
PACKAGE_BUGREPORT='[email protected]'
PACKAGE_NAME='gaim'
PACKAGE_STRING='gaim 1.1.1'
PACKAGE_TARNAME='gaim'
PACKAGE_VERSION='1.1.1'
PATH_SEPARATOR=':'
PERL=''
PERL_CFLAGS=''
PERL_LIBS=''
PERL_MM_PARAMS=''
PKG_CONFIG=''
PLUGINS_FALSE=''
PLUGINS_TRUE=''
POSUB=''
PRPLS_FALSE=''
PRPLS_TRUE=''
RANLIB=''
SET_MAKE=''
SHELL='/bin/sh'
SILC_CFLAGS=''
SILC_LIBS=''
SM_LIBS=''
SOUND_LIBS=''
STARTUP_NOTIFICATION_CFLAGS=''
STARTUP_NOTIFICATION_LIBS=''
STATIC_GG_FALSE=''
STATIC_GG_TRUE=''
STATIC_IRC_FALSE=''
STATIC_IRC_TRUE=''
STATIC_JABBER_FALSE=''
STATIC_JABBER_TRUE=''
STATIC_LINK_LIBS=''
STATIC_MSN_FALSE=''
STATIC_MSN_TRUE=''
STATIC_NAPSTER_FALSE=''
STATIC_NAPSTER_TRUE=''
STATIC_NOVELL_FALSE=''
STATIC_NOVELL_TRUE=''
STATIC_OSCAR_FALSE=''
STATIC_OSCAR_TRUE=''
STATIC_PRPLS=''
STATIC_RENDEZVOUS_FALSE=''
STATIC_RENDEZVOUS_TRUE=''
STATIC_SILC_FALSE=''
STATIC_SILC_TRUE=''
STATIC_TOC_FALSE=''
STATIC_TOC_TRUE=''
STATIC_TREPIA_FALSE=''
STATIC_TREPIA_TRUE=''
STATIC_YAHOO_FALSE=''
STATIC_YAHOO_TRUE=''
STATIC_ZEPHYR_FALSE=''
STATIC_ZEPHYR_TRUE=''
STRIP=''
TCL_CFLAGS=''
TCL_LIBS=''
TK_LIBS=''
USE_GNUTLS_FALSE=''
USE_GNUTLS_TRUE=''
USE_INCLUDED_LIBINTL=''
USE_NLS=''
USE_NSS_FALSE=''
USE_NSS_TRUE=''
USE_PERL_FALSE=''
USE_PERL_TRUE=''
USE_TCL_FALSE=''
USE_TCL_TRUE=''
USE_TK_FALSE=''
USE_TK_TRUE=''
VERSION=''
XGETTEXT=''
XSS_LIBS=''
X_CFLAGS=''
X_EXTRA_LIBS=''
X_LIBS=''
X_PRE_LIBS=''
ZEPHYR_CFLAGS=''
ZEPHYR_LDFLAGS=''
ZEPHYR_LIBS=''
ac_ct_AR=''
ac_ct_CC=''
ac_ct_CXX=''
ac_ct_F77=''
ac_ct_RANLIB=''
ac_ct_STRIP=''
am__fastdepCC_FALSE=''
am__fastdepCC_TRUE=''
am__fastdepCXX_FALSE=''
am__fastdepCXX_TRUE=''
am__include=''
am__leading_dot=''
am__quote=''
am__tar=''
am__untar=''
bindir='${exec_prefix}/bin'
build=''
build_alias=''
build_cpu=''
build_os=''
build_vendor=''
datadir='${prefix}/share'
exec_prefix='NONE'
gaimpath=''
host=''
host_alias=''
host_cpu=''
host_os=''
host_vendor=''
includedir='${prefix}/include'
infodir='${prefix}/info'
install_sh=''
libdir='${exec_prefix}/lib'
libexecdir='${exec_prefix}/libexec'
localstatedir='${prefix}/var'
mandir='${prefix}/man'
mkdir_p=''
oldincludedir='/usr/include'
perlpath=''
prefix='NONE'
program_transform_name='s,x,x,'
sbindir='${exec_prefix}/sbin'
sedpath=''
sharedstatedir='${prefix}/com'
sysconfdir='${prefix}/etc'
target=''
target_alias=''
target_cpu=''
target_os=''
target_vendor=''
## ----------- ##
## confdefs.h. ##
## ----------- ##
#define PACKAGE_BUGREPORT "[email protected]"
#define PACKAGE_NAME "gaim"
#define PACKAGE_STRING "gaim 1.1.1"
#define PACKAGE_TARNAME "gaim"
#define PACKAGE_VERSION "1.1.1"
configure: exit 1
看不懂~哦对了~没有校验MD5 :oops: 在linux下面要习惯校验MD5码，这个东西是不会骗人的！
我主要是从你贴的红色后面那部分看到的！也许是这个问题！
你试试！
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
页:
[1]
2