کمک در نسب برنامه هایی که سورس و shellScript هستند

[whitehat0o]

سلام به همگی.
می خواستم بدونم وقتی بعضی فایلهای tar.gz یا مثل اینا بعد از خارج کردنشون از حالت فشرده یه فولدر به ما میدن که توش اثری از فایل executable یا deb نیستش.
فقط تعداد زیادی shell script داره.
مثلا فایل install (به صورت text ) یکی از اونا اینه:

Installation Instructions
*************************

Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005,
2006, 2007 Free Software Foundation, Inc.

This file is free documentation; the Free Software Foundation gives
unlimited permission to copy, distribute and modify it.

Basic Installation
==================

Briefly, the shell commands `./configure; make; make install' should
configure, build, and install this package.  The following
more-detailed instructions are generic; see the `README' file for
instructions specific to this package.

   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, and a
file `config.log' containing compiler output (useful mainly for
debugging `configure').

   It can also use an optional file (typically called `config.cache'
and enabled with `--cache-file=config.cache' or simply `-C') that saves
the results of its tests to speed up reconfiguring.  Caching is
disabled by default to prevent problems with accidental use of stale
cache files.

   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 you are using the cache, and at
some point `config.cache' contains results you don't want to keep, you
may remove or edit it.

   The file `configure.ac' (or `configure.in') is used to create
`configure' by a program called `autoconf'.  You 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.

     Running `configure' might take a while.  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.

  6. Often, you can also type `make uninstall' to remove the installed
     files again.

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

Some systems require unusual options for compilation or linking that the
`configure' script does not know about.  Run `./configure --help' for
details on some of the pertinent environment variables.

   You can give `configure' initial values for configuration parameters
by setting variables in the command line or in the environment.  Here
is an example:

     ./configure CC=c99 CFLAGS=-g LIBS=-lposix

   *Note Defining Variables::, for more details.

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 can use 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 `..'.

   With a non-GNU `make', it is safer 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' installs the package's commands under
`/usr/local/bin', include files under `/usr/local/include', etc.  You
can specify an installation prefix other than `/usr/local' by giving
`configure' the option `--prefix=PREFIX'.

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

   In addition, if you use an unusual directory layout you can give
options like `--bindir=DIR' 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' cannot figure out automatically,
but needs to determine by the type of machine the package will run on.
Usually, assuming the package is built to be run on the _same_
architectures, `configure' can figure that out, but if it prints a
message saying it cannot guess the machine type, give it the
`--build=TYPE' option.  TYPE can either be a short name for the system
type, such as `sun4', or a canonical name which has the form:

     CPU-COMPANY-SYSTEM

where SYSTEM can have one of these forms:

     OS KERNEL-OS

   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 machine type.

   If you are _building_ compiler tools for cross-compiling, you should
use the option `--target=TYPE' to select the type of system they will
produce code for.

   If you want to _use_ a cross compiler, that generates code for a
platform different from the build platform, you should specify the
"host" platform (i.e., that on which the generated programs will
eventually be run) with `--host=TYPE'.

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.

Defining Variables
==================

Variables not defined in a site shell script can be set in the
environment passed to `configure'.  However, some packages may run
configure again during the build, and the customized values of these
variables may be lost.  In order to avoid this problem, you should set
them in the `configure' command line, using `VAR=value'.  For example:

     ./configure CC=/usr/local2/bin/gcc

causes the specified `gcc' to be used as the C compiler (unless it is
overridden in the site shell script).

Unfortunately, this technique does not work for `CONFIG_SHELL' due to
an Autoconf bug.  Until the bug is fixed you can use this workaround:

     CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash

`configure' Invocation
======================

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

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

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

`--cache-file=FILE'
     Enable the cache: use and save the results of the tests in FILE,
     traditionally `config.cache'.  FILE defaults to `/dev/null' to
     disable caching.

`--config-cache'
`-C'
     Alias for `--cache-file=config.cache'.

`--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.

`configure' also accepts some other, not widely useful, options.  Run
`configure --help' for more details.

ولی وقتی دستور

./configure; make; make install

رو اجرا می کنم یه error کلفت می ده که log ش اینه

This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by totem configure 2.27.2, which was
generated by GNU Autoconf 2.63.  Invocation command line was

  $ ./configure

## --------- ##
## Platform. ##
## --------- ##

hostname = linux
uname -m = i686
uname -r = 2.6.22-14-generic
uname -s = Linux
uname -v = #1 SMP Sun Oct 14 23:05:12 GMT 2007

/usr/bin/uname -p = unknown
/bin/uname -X     = unknown

/bin/arch              = unknown
/usr/bin/arch -k       = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo      = unknown
/bin/machine           = unknown
/usr/bin/oslevel       = unknown
/bin/universe          = unknown

PATH: /usr/local/sbin
PATH: /usr/local/bin
PATH: /usr/sbin
PATH: /usr/bin
PATH: /sbin
PATH: /bin
PATH: /usr/games


## ----------- ##
## Core tests. ##
## ----------- ##

configure:2485: checking for a BSD-compatible install
configure:2553: result: /usr/bin/install -c
configure:2564: checking whether build environment is sane
configure:2624: result: yes
configure:2765: checking for a thread-safe mkdir -p
configure:2804: result: /bin/mkdir -p
configure:2817: checking for gawk
configure:2847: result: no
configure:2817: checking for mawk
configure:2833: found /usr/bin/mawk
configure:2844: result: mawk
configure:2855: checking whether make sets $(MAKE)
configure:2877: result: yes
configure:2979: checking for style of include used by make
configure:3007: result: GNU
configure:3077: checking for gcc
configure:3093: found /usr/bin/gcc
configure:3104: result: gcc
configure:3336: checking for C compiler version
configure:3344: gcc --version >&5
gcc (GCC) 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

configure:3348: $? = 0
configure:3355: gcc -v >&5
Using built-in specs.
Target: i486-linux-gnu
Configured with: ../src/configure -v --enable-languages=c,c++,fortran,objc,obj-c++,treelang --prefix=/usr --enable-shared --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --enable-nls --with-gxx-include-dir=/usr/include/c++/4.1.3 --program-suffix=-4.1 --enable-__cxa_atexit --enable-clocale=gnu --enable-libstdcxx-debug --enable-mpfr --enable-checking=release i486-linux-gnu
Thread model: posix
gcc version 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)
configure:3359: $? = 0
configure:3366: gcc -V >&5
gcc: '-V' option must have argument
configure:3370: $? = 1
configure:3393: checking for C compiler default output file name
configure:3415: gcc    conftest.c  >&5
/usr/bin/ld: crt1.o: No such file: No such file or directory
collect2: ld returned 1 exit status
configure:3419: $? = 1
configure:3457: result:
configure: failed program was:
| /* confdefs.h.  */
| #define PACKAGE_NAME "totem"
| #define PACKAGE_TARNAME "totem"
| #define PACKAGE_VERSION "2.27.2"
| #define PACKAGE_STRING "totem 2.27.2"
| #define PACKAGE_BUGREPORT "http://bugzilla.gnome.org/enter_bug.cgi?product=totem"
| #define PACKAGE "totem"
| #define VERSION "2.27.2"
| #define GETTEXT_PACKAGE "totem"
| /* end confdefs.h.  */
|
| int
| main ()
| {
|
|   ;
|   return 0;
| }
configure:3463: error: in `/home/linux/Desktop/totem-2.27.2':
configure:3466: error: C compiler cannot create executables
See `config.log' for more details.

## ---------------- ##
## Cache variables. ##
## ---------------- ##

ac_cv_env_BEMUSED_CFLAGS_set=
ac_cv_env_BEMUSED_CFLAGS_value=
ac_cv_env_BEMUSED_LIBS_set=
ac_cv_env_BEMUSED_LIBS_value=
ac_cv_env_BROWSER_PLUGIN_CFLAGS_set=
ac_cv_env_BROWSER_PLUGIN_CFLAGS_value=
ac_cv_env_BROWSER_PLUGIN_DIR_set=
ac_cv_env_BROWSER_PLUGIN_DIR_value=
ac_cv_env_BROWSER_PLUGIN_LIBS_set=
ac_cv_env_BROWSER_PLUGIN_LIBS_value=
ac_cv_env_CCC_set=
ac_cv_env_CCC_value=
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_DBUS_CFLAGS_set=
ac_cv_env_DBUS_CFLAGS_value=
ac_cv_env_DBUS_LIBS_set=
ac_cv_env_DBUS_LIBS_value=
ac_cv_env_DEPENDENCY_CFLAGS_set=
ac_cv_env_DEPENDENCY_CFLAGS_value=
ac_cv_env_DEPENDENCY_LIBS_set=
ac_cv_env_DEPENDENCY_LIBS_value=
ac_cv_env_DISC_RECORDER_CFLAGS_set=
ac_cv_env_DISC_RECORDER_CFLAGS_value=
ac_cv_env_DISC_RECORDER_LIBS_set=
ac_cv_env_DISC_RECORDER_LIBS_value=
ac_cv_env_GLIB_CFLAGS_set=
ac_cv_env_GLIB_CFLAGS_value=
ac_cv_env_GLIB_LIBS_set=
ac_cv_env_GLIB_LIBS_value=
ac_cv_env_GMYTH_CFLAGS_set=
ac_cv_env_GMYTH_CFLAGS_value=
ac_cv_env_GMYTH_LIBS_set=
ac_cv_env_GMYTH_LIBS_value=
ac_cv_env_GST_CFLAGS_set=
ac_cv_env_GST_CFLAGS_value=
ac_cv_env_GST_LIBS_set=
ac_cv_env_GST_LIBS_value=
ac_cv_env_GTK_CFLAGS_set=
ac_cv_env_GTK_CFLAGS_value=
ac_cv_env_GTK_LIBS_set=
ac_cv_env_GTK_LIBS_value=
ac_cv_env_LDFLAGS_set=
ac_cv_env_LDFLAGS_value=
ac_cv_env_LIBEPC_CFLAGS_set=
ac_cv_env_LIBEPC_CFLAGS_value=
ac_cv_env_LIBEPC_LIBS_set=
ac_cv_env_LIBEPC_LIBS_value=
ac_cv_env_LIBGALAGO_CFLAGS_set=
ac_cv_env_LIBGALAGO_CFLAGS_value=
ac_cv_env_LIBGALAGO_LIBS_set=
ac_cv_env_LIBGALAGO_LIBS_value=
ac_cv_env_LIBGDATA_CFLAGS_set=
ac_cv_env_LIBGDATA_CFLAGS_value=
ac_cv_env_LIBGDATA_LIBS_set=
ac_cv_env_LIBGDATA_LIBS_value=
ac_cv_env_LIBS_set=
ac_cv_env_LIBS_value=
ac_cv_env_MEDIA_PLAYER_KEYS_CFLAGS_set=
ac_cv_env_MEDIA_PLAYER_KEYS_CFLAGS_value=
ac_cv_env_MEDIA_PLAYER_KEYS_LIBS_set=
ac_cv_env_MEDIA_PLAYER_KEYS_LIBS_value=
ac_cv_env_MISSING_PLUGINS_CFLAGS_set=
ac_cv_env_MISSING_PLUGINS_CFLAGS_value=
ac_cv_env_MISSING_PLUGINS_LIBS_set=
ac_cv_env_MISSING_PLUGINS_LIBS_value=
ac_cv_env_MM_CFLAGS_set=
ac_cv_env_MM_CFLAGS_value=
ac_cv_env_MM_LIBS_set=
ac_cv_env_MM_LIBS_value=
ac_cv_env_NAUTILUS_CFLAGS_set=
ac_cv_env_NAUTILUS_CFLAGS_value=
ac_cv_env_NAUTILUS_LIBS_set=
ac_cv_env_NAUTILUS_LIBS_value=
ac_cv_env_PKG_CONFIG_set=
ac_cv_env_PKG_CONFIG_value=
ac_cv_env_PYGTK_CFLAGS_set=
ac_cv_env_PYGTK_CFLAGS_value=
ac_cv_env_PYGTK_LIBS_set=
ac_cv_env_PYGTK_LIBS_value=
ac_cv_env_SCREENSAVER_CFLAGS_set=
ac_cv_env_SCREENSAVER_CFLAGS_value=
ac_cv_env_SCREENSAVER_LIBS_set=
ac_cv_env_SCREENSAVER_LIBS_value=
ac_cv_env_SMCLIENT_CFLAGS_set=
ac_cv_env_SMCLIENT_CFLAGS_value=
ac_cv_env_SMCLIENT_LIBS_set=
ac_cv_env_SMCLIENT_LIBS_value=
ac_cv_env_TRACKER_CFLAGS_set=
ac_cv_env_TRACKER_CFLAGS_value=
ac_cv_env_TRACKER_LIBS_set=
ac_cv_env_TRACKER_LIBS_value=
ac_cv_env_UNIQUE_CFLAGS_set=
ac_cv_env_UNIQUE_CFLAGS_value=
ac_cv_env_UNIQUE_LIBS_set=
ac_cv_env_UNIQUE_LIBS_value=
ac_cv_env_VALA_CFLAGS_set=
ac_cv_env_VALA_CFLAGS_value=
ac_cv_env_VALA_LIBS_set=
ac_cv_env_VALA_LIBS_value=
ac_cv_env_XMKMF_set=
ac_cv_env_XMKMF_value=
ac_cv_env_XVIDMODE_CFLAGS_set=
ac_cv_env_XVIDMODE_CFLAGS_value=
ac_cv_env_XVIDMODE_LIBS_set=
ac_cv_env_XVIDMODE_LIBS_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=
ac_cv_path_install='/usr/bin/install -c'
ac_cv_path_mkdir=/bin/mkdir
ac_cv_prog_AWK=mawk
ac_cv_prog_ac_ct_CC=gcc
ac_cv_prog_make_make_set=yes

## ----------------- ##
## Output variables. ##
## ----------------- ##

ACLOCAL='${SHELL} /home/linux/Desktop/totem-2.27.2/missing --run aclocal-1.11'
ACLOCAL_AMFLAGS=''
ALL_LINGUAS=''
ALL_PLUGINS=''
AMDEPBACKSLASH='\'
AMDEP_FALSE='#'
AMDEP_TRUE=''
AMTAR='${SHELL} /home/linux/Desktop/totem-2.27.2/missing --run tar'
AM_CFLAGS=''
AM_CPPFLAGS=''
AM_CXXFLAGS=''
AM_LDFLAGS=''
AR=''
AUTOCONF='${SHELL} /home/linux/Desktop/totem-2.27.2/missing --run autoconf'
AUTOHEADER='${SHELL} /home/linux/Desktop/totem-2.27.2/missing --run autoheader'
AUTOMAKE='${SHELL} /home/linux/Desktop/totem-2.27.2/missing --run automake-1.11'
AWK='mawk'
BEMUSED_CFLAGS=''
BEMUSED_LIBS=''
BROWSER_PLUGIN_CFLAGS=''
BROWSER_PLUGIN_DIR=''
BROWSER_PLUGIN_LIBS=''
CATALOGS=''
CATOBJEXT=''
CC='gcc'
CCDEPMODE=''
CFLAGS=''
CPP=''
CPPFLAGS=''
CXX=''
CXXCPP=''
CXXDEPMODE=''
CXXFLAGS=''
CYGPATH_W='echo'
DATADIRNAME=''
DBUS_BIND=''
DBUS_CFLAGS=''
DBUS_LIBS=''
DEFS=''
DEPDIR='.deps'
DEPENDENCY_CFLAGS=''
DEPENDENCY_LIBS=''
DISABLE_DEPRECATED=''
DISC_RECORDER_CFLAGS=''
DISC_RECORDER_LIBS=''
DISTCHECK_CONFIGURE_FLAGS=''
DOC_USER_FORMATS=''
DSYMUTIL=''
DUMPBIN=''
ECHO_C=''
ECHO_N='-n'
ECHO_T=''
EGREP=''
ENABLE_BROWSER_PLUGINS_FALSE=''
ENABLE_BROWSER_PLUGINS_TRUE=''
ENABLE_COMPLEX_PLUGIN_FALSE=''
ENABLE_COMPLEX_PLUGIN_TRUE=''
ENABLE_CONE_PLUGIN_FALSE=''
ENABLE_CONE_PLUGIN_TRUE=''
ENABLE_GMP_PLUGIN_FALSE=''
ENABLE_GMP_PLUGIN_TRUE=''
ENABLE_GTK_DOC_FALSE=''
ENABLE_GTK_DOC_TRUE=''
ENABLE_MULLY_PLUGIN_FALSE=''
ENABLE_MULLY_PLUGIN_TRUE=''
ENABLE_NARROWSPACE_PLUGIN_FALSE=''
ENABLE_NARROWSPACE_PLUGIN_TRUE=''
ENABLE_PYTHON_FALSE=''
ENABLE_PYTHON_TRUE=''
ENABLE_SK_FALSE=''
ENABLE_SK_TRUE=''
ENABLE_VALA_FALSE=''
ENABLE_VALA_TRUE=''
EXEEXT=''
EXTRA_BACKEND_LIBS=''
FGREP=''
FULL_LIBEXECDIR=''
GCONFTOOL=''
GCONF_SCHEMAS_INSTALL_FALSE=''
GCONF_SCHEMAS_INSTALL_TRUE=''
GCONF_SCHEMA_CONFIG_SOURCE=''
GCONF_SCHEMA_FILE_DIR=''
GETTEXT_PACKAGE='totem'
GLIB_CFLAGS=''
GLIB_GENMARSHAL=''
GLIB_LIBS=''
GLIB_MKENUMS=''
GMOFILES=''
GMSGFMT=''
GMYTH_CFLAGS=''
GMYTH_LIBS=''
GREP=''
GST_CFLAGS=''
GST_LIBS=''
GTKDOC_CHECK=''
GTK_CFLAGS=''
GTK_DOC_USE_LIBTOOL_FALSE=''
GTK_DOC_USE_LIBTOOL_TRUE=''
GTK_LIBS=''
HAVE_GNOME_DOC_UTILS_FALSE=''
HAVE_GNOME_DOC_UTILS_TRUE=''
HAVE_NAUTILUS_FALSE=''
HAVE_NAUTILUS_TRUE=''
HAVE_XVIDMODE_FALSE=''
HAVE_XVIDMODE_TRUE=''
HELP_DIR=''
HTML_DIR=''
INSTALL_DATA='${INSTALL} -m 644'
INSTALL_PROGRAM='${INSTALL}'
INSTALL_SCRIPT='${INSTALL}'
INSTALL_STRIP_PROGRAM='$(install_sh) -c -s'
INSTOBJEXT=''
INTLLIBS=''
INTLTOOL_CAVES_RULE=''
INTLTOOL_DESKTOP_RULE=''
INTLTOOL_DIRECTORY_RULE=''
INTLTOOL_EXTRACT=''
INTLTOOL_KBD_RULE=''
INTLTOOL_KEYS_RULE=''
INTLTOOL_MERGE=''
INTLTOOL_OAF_RULE=''
INTLTOOL_PERL=''
INTLTOOL_POLICY_RULE=''
INTLTOOL_PONG_RULE=''
INTLTOOL_PROP_RULE=''
INTLTOOL_SCHEMAS_RULE=''
INTLTOOL_SERVER_RULE=''
INTLTOOL_SERVICE_RULE=''
INTLTOOL_SHEET_RULE=''
INTLTOOL_SOUNDLIST_RULE=''
INTLTOOL_THEME_RULE=''
INTLTOOL_UI_RULE=''
INTLTOOL_UPDATE=''
INTLTOOL_XAM_RULE=''
INTLTOOL_XML_NOMERGE_RULE=''
INTLTOOL_XML_RULE=''
LD=''
LDFLAGS=''
LIBEPC_CFLAGS=''
LIBEPC_LIBS=''
LIBGALAGO_CFLAGS=''
LIBGALAGO_LIBS=''
LIBGDATA_CFLAGS=''
LIBGDATA_LIBS=''
LIBOBJS=''
LIBS=''
LIBTOOL=''
LIPO=''
LIRC_LIBS=''
LN_S=''
LTLIBOBJS=''
MAINT=''
MAINTAINER_MODE_FALSE=''
MAINTAINER_MODE_TRUE=''
MAKEINFO='${SHELL} /home/linux/Desktop/totem-2.27.2/missing --run makeinfo'
MEDIA_PLAYER_KEYS_CFLAGS=''
MEDIA_PLAYER_KEYS_LIBS=''
MISSING_PLUGINS_CFLAGS=''
MISSING_PLUGINS_LIBS=''
MKDIR_P='/bin/mkdir -p'
MKINSTALLDIRS=''
MM_CFLAGS=''
MM_LIBS=''
MSGFMT=''
MSGFMT_OPTS=''
MSGMERGE=''
NAUTILUSDIR=''
NAUTILUS_CFLAGS=''
NAUTILUS_LIBS=''
NM=''
NMEDIT=''
NO_STRICT_ALIASING_CFLAGS=''
OBJDUMP=''
OBJEXT=''
OMF_DIR=''
OTOOL64=''
OTOOL=''
PACKAGE='totem'
PACKAGE_BUGREPORT='http://bugzilla.gnome.org/enter_bug.cgi?product=totem'
PACKAGE_NAME='totem'
PACKAGE_STRING='totem 2.27.2'
PACKAGE_TARNAME='totem'
PACKAGE_VERSION='2.27.2'
PATH_SEPARATOR=':'
PKG_CONFIG=''
PLUGINDIR=''
PLUGINS=''
POFILES=''
POSUB=''
PO_IN_DATADIR_FALSE=''
PO_IN_DATADIR_TRUE=''
PYGTK_CFLAGS=''
PYGTK_CODEGEN=''
PYGTK_DEFSDIR=''
PYGTK_H2DEF=''
PYGTK_LIBS=''
PYTHON=''
PYTHON_CFLAGS=''
PYTHON_EXEC_PREFIX=''
PYTHON_EXTRA_LIBS=''
PYTHON_LIBS=''
PYTHON_LIB_LOC=''
PYTHON_PLATFORM=''
PYTHON_PREFIX=''
PYTHON_VERSION=''
RANLIB=''
SCREENSAVER_CFLAGS=''
SCREENSAVER_LIBS=''
SED=''
SET_MAKE=''
SHELL='/bin/bash'
SMCLIENT_CFLAGS=''
SMCLIENT_LIBS=''
STRIP=''
TOTEM_VERSION_MAJOR=''
TOTEM_VERSION_MICRO=''
TOTEM_VERSION_MINOR=''
TRACKER_CFLAGS=''
TRACKER_LIBS=''
UNIQUE_CFLAGS=''
UNIQUE_LIBS=''
USE_NLS=''
VALAC=''
VALA_CFLAGS=''
VALA_LIBS=''
VERSION='2.27.2'
WARN_CFLAGS=''
WARN_CXXFLAGS=''
WITH_DBUS_FALSE=''
WITH_DBUS_TRUE=''
WITH_SMCLIENT_FALSE=''
WITH_SMCLIENT_QUARTZ_FALSE=''
WITH_SMCLIENT_QUARTZ_TRUE=''
WITH_SMCLIENT_TRUE=''
WITH_SMCLIENT_WIN32_FALSE=''
WITH_SMCLIENT_WIN32_TRUE=''
WITH_SMCLIENT_XSMP_FALSE=''
WITH_SMCLIENT_XSMP_TRUE=''
XGETTEXT=''
XMKMF=''
XTEST_LIBS=''
XVIDMODE_CFLAGS=''
XVIDMODE_LIBS=''
X_LIBS=''
ac_ct_CC='gcc'
ac_ct_CXX=''
ac_ct_DUMPBIN=''
am__EXEEXT_FALSE=''
am__EXEEXT_TRUE=''
am__fastdepCC_FALSE=''
am__fastdepCC_TRUE=''
am__fastdepCXX_FALSE=''
am__fastdepCXX_TRUE=''
am__include='include'
am__isrc=''
am__leading_dot='.'
am__quote=''
am__tar='${AMTAR} chof - "$$tardir"'
am__untar='${AMTAR} xf -'
bindir='${exec_prefix}/bin'
build=''
build_alias=''
build_cpu=''
build_os=''
build_vendor=''
datadir='${datarootdir}'
datarootdir='${prefix}/share'
docdir='${datarootdir}/doc/${PACKAGE_TARNAME}'
dvidir='${docdir}'
exec_prefix='NONE'
host=''
host_alias=''
host_cpu=''
host_os=''
host_vendor=''
htmldir='${docdir}'
includedir='${prefix}/include'
infodir='${datarootdir}/info'
install_sh='${SHELL} /home/linux/Desktop/totem-2.27.2/install-sh'
libdir='${exec_prefix}/lib'
libexecdir='${exec_prefix}/libexec'
localedir='${datarootdir}/locale'
localstatedir='${prefix}/var'
lt_ECHO='echo'
mandir='${datarootdir}/man'
mkdir_p='/bin/mkdir -p'
oldincludedir='/usr/include'
pdfdir='${docdir}'
pkgpyexecdir=''
pkgpythondir=''
prefix='NONE'
program_transform_name='s,x,x,'
psdir='${docdir}'
pyexecdir=''
pythondir=''
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
sysconfdir='${prefix}/etc'
target_alias=''

## ----------- ##
## confdefs.h. ##
## ----------- ##

#define PACKAGE_NAME "totem"
#define PACKAGE_TARNAME "totem"
#define PACKAGE_VERSION "2.27.2"
#define PACKAGE_STRING "totem 2.27.2"
#define PACKAGE_BUGREPORT "http://bugzilla.gnome.org/enter_bug.cgi?product=totem"
#define PACKAGE "totem"
#define VERSION "2.27.2"
#define GETTEXT_PACKAGE "totem"

configure: exit 77

لطفا یکی یه راهنمایی کنه.
ممنون

[Midgårdsormen]

اینکه سورسه...معلومه نباید توش بسته‌ی deb داشته باشه
باید خودتون در حالی که سوپریوزر هستید کامپایلش کنید
معمولا اینجوریه:

کد: [انتخاب]

./configure
make
make install
make cleanولی حتما فایل readmeرو کامل بخونید.شاید خودتون لازم بدونید که با پارامترهای خاصی کانفیگ کنید
تازه باید قبلش dependancyهارو هم خودتون دستی نصب کنید

[فاراب]

خب دوست من یکم دقت کنید. در همون متنی که گذاشتید، بروشنی مراحل نصب رُ توضیح داده:

1. `cd' to the directory containing the package's source code and type
     `./configure' to configure the package for your system.

     Running `configure' might take a while.  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.

برای اسکریپت‌ها یا فایل‌های با پسوند sh با فرض اینکه نام فایل، file.sh هست، هم در ترمینال بنویسید:

کد: [انتخاب]

./file.sh

یا

کد: [انتخاب]

sh file.sh

[whitehat0o]

ممنون از جواباتون.
این کدهایی رو که گفتین من بالا گفته بودم که اجراشون کردم ولی error داده!!!!!!
متن error رو هم اینجا گذاشتم تا کمکم کنید ببینم چه parameter ها یی باید همراه دستور استفاده کنم. چون من چند تا از اونا رو تست کردم بازم جواب نداد.
و یا اینکه اگه dependancy می خواد  که چه dependancy یی؟

[penguinsjr]

این پست رو اشتباهی زدم و نتونستم پاکش کنم

[penguinsjr]

.deb
.tar.gz
.tar.bz2
.rmp
.bin

[penguinsjr]

کسی نمی خواد جواب سوال بالای منو بده؟

[سعید رسولی]

کسی نمی خواد جواب سوال بالای منو بده؟

منظورتون از سوال اینه؟؟؟

.deb
.tar.gz
.tar.bz2
.rmp
.bin

شما به این میگید سوال؟؟!!!

[penguinsjr]

ببخشید شرمنه اینطوری شده...
دوباره می پرسم..
لطفا در مورد انیا هی توضیح بدید و نحوه ی استفاده از اونا رو هم بگید... ممنون

.deb
.tar.gz
.tar.bz2
.rmp
.bin

[penguinsjr]

رفیق جوابم رو ندادید که...

[whitehat0o]

سلام.
بهتر بود برای سوالت یه topic جدید درست می کردی!!!!!
چون اصلا ربطی به  کمک در نسب برنامه هایی که سورس و shellScript هستند نداره!
به هر حال
.deb  پسوند توزیع هایی هستش که برای debian linux استفاده می شده.
ubuntu هم که base ش از debian هستش از این بسته ها استفاده می کنه.
نصب کردنش با دستور dpkg -i packet_name.deb هستش.

در مورد بسته های rmp باید بگم برای redhat linux از اونها استفاده می شده. که بعدا در fedora استفاده شدند.
برای نصب اونا از دستور :
rpm -i packet_name.rpm استفاده میکنیم. البته همچین دستوری در ubuntu نیس. چون اصلا packet های rpm مال ubuntu نیستن.
در مورد .tar.gz و .tar.bz2 فکر میکنم صرفا پسوندی برای فایل های فشرده است. همچنان که اگه تو windows دقت کرده باشی
winrar هر 2 تا رو ساپورت می کنه.
در مورد .bin فکر کنم مربوط فایلهای shell باشه ولی زیاد رو این حساب نکن مخصوصا که الان با ubuntu کانکت نیستم تست کنم.