Salut,

Si un fichier n'est pas exécutable, même le root ne peut pas l'exécuter!

Poste le Thursday 27 November 2003 21:25:59

Salut,

IDEM que P Hoquet, mais pour le rendre executable : chmod u+x INSTALL

Mais en fait, t'es sûr que c'est pas un fichier texte contenant les infos pour l'installation (on en voit souvent qui ont ce nom là).

A+

Poste le Thursday 27 November 2003 21:36:30

ben si c est un probleme de format en principe l'erreur est :" Cannot execute"

essaie de taper file ./INSTALL et regarde quel type de fichier ca renvoie.

s'il est executable, alors la, c est autre chose

Poste le Thursday 27 November 2003 22:08:19

Peut etre aussi la partition contenant les fichiers en noexec..

Poste le Friday 28 November 2003 13:21:24

Salut,

Qui êut m'expliquer ce qui se passe et m'aider a le résoudre !
voila j'tapé ce qui suit et voila le message :

[root@mdk92 gtuner-0.4.0]# ./INSTALL
bash: ./INSTALL: Permission denied
[root@mdk92 gtuner-0.4.0]# chmod u+x INSTALL
[root@mdk92 gtuner-0.4.0]# ./INSTALL
./INSTALL: line 1: Basic: command not found
./INSTALL: line 2: ==================: command not found
./INSTALL: line 4: These: command not found
./INSTALL: command substitution: line 1: unexpected EOF while looking for matching `''
./INSTALL: command substitution: line 4: syntax error: unexpected end of file
./INSTALL: line 10: RUN: command not found
./INSTALL: command substitution: line 1: unexpected EOF while looking for matching `''
./INSTALL: command substitution: line 3: syntax error: unexpected end of file
./INSTALL: line 11: It: command not found
./INSTALL: command substitution: line 1: unexpected EOF while looking for matching `''
./INSTALL: command substitution: line 3: syntax error: unexpected end of file
./INSTALL: line 15: reconfiguring,: command not found
./INSTALL: command substitution: line 1: unexpected EOF while looking for matching `''
./INSTALL: command substitution: line 3: syntax error: unexpected end of file
./INSTALL: line 20: diffs: command not found
./INSTALL: command substitution: line 1: unexpected EOF while looking for matching `''
./INSTALL: command substitution: line 2: syntax error: unexpected end of file
./INSTALL: command substitution: line 1: unexpected EOF while looking for matching `''
./INSTALL: command substitution: line 3: syntax error: unexpected end of file
./INSTALL: line 24: The: command not found
./INSTALL: line 28: The: command not found
./INSTALL: line 1: cd to the directory containing the packages: command not found
./INSTALL: line 31: 1.: command not found
./INSTALL: command substitution: line 1: unexpected EOF while looking for matching `''
./INSTALL: command substitution: line 3: syntax error: unexpected end of file
./INSTALL: line 33: using: command not found
./INSTALL: command substitution: line 1: unexpected EOF while looking for matching `''
./INSTALL: command substitution: line 4: syntax error: unexpected end of file
./INSTALL: line 39: configure takes awhile. While running, it prints some
messages telling which features it is checking for.

2. Type `make: command not found
./INSTALL: command substitution: line 1: unexpected EOF while looking for matching `''
./INSTALL: command substitution: line 5: syntax error: unexpected end of file
./INSTALL: line 41: 3.: command not found
./INSTALL: command substitution: line 1: unexpected EOF while looking for matching `''
./INSTALL: command substitution: line 3: syntax error: unexpected end of file
./INSTALL: line 49: files: command not found
./INSTALL: line 60: syntax error near unexpected token `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''
./INSTALL: line 60: `the `configure' script does not know about. You can give `configure''
[root@mdk92 gtuner-0.4.0]# [root@mdk92 gtuner-0.4.0]# ./INSTALL
bash: [root@mdk92: command not found
[root@mdk92 gtuner-0.4.0]# bash: ./INSTALL: Permission denied
bash: bash:: command not found
[root@mdk92 gtuner-0.4.0]#

Merci d'avance, salutations.

Poste le Friday 28 November 2003 21:24:37

As-tu seulement regardé ce qu'il y a dans ce fichier.
As-tu vérifié comme le suggérait Teotihuacan que ce fichier n'était pas un fichier texte contenant des instructions d'installations.
A mon avis si ce fichier n'était pas exécutable c'est qu'il y avait une raison.

Poste le Friday 28 November 2003 21:36:53

salut,

Mais alors comment installer un fichier sans ./install
de gtuner-0.4.0.tar.gz

une fois décompréssé :
----------------------
[root@mdk92 gtuner-0.4.0]# dir
acconfig.h config.cache gtuner.desktop gtunerrc missing
acinclude.m4 config.guess gtuner.layout INSTALL mkinstalldirs
aclocal.m4 config.h.in gtuner.layout1 install-sh NEWS
applet_skins config.log gtuner.layout2 libtool plugins
AUTHORS config.sub gtuner.layout3 ltconfig README
BUGS configure gtuner.layout4 ltmain.sh src
ChangeLog configure.in gtuner.layout5 Makefile.am stamp-h.in
confdefs.h COPYING gtuner.layout7 Makefile.in TODO
[root@mdk92 gtuner-0.4.0]#

--------------------------------------------------------------------

Fichier Readme avec gedit :
---------------------------
gtuner - Readme file
Gnome tuner application

If someone wants to write some documentation, please contact me

gtuner is quite advanced, but I only work on a single machine over here
and my setup may not be compatable with yours. If you find any problems
with the installation scripts, please try modify them and post me a copy
with details of the problem so we can avoid future problems.

To disable gnome support `configure --disable-gnome'
To disable only gnome panel support `configure --disable-panel'

Basics:
gtuner uses 2 files for its configuration: /etc/gtunerrc and ~/.gtunerrc
The /etc/gtunerrc file is read first, followed by ~/.gtunerrc
The settings in ~/.gtunerrc override the settings in /etc/gtunerrc

The gtuner GUI is configured via a layout engine. The layout
configuration file is specified in the config file.
A default layout script is installed, but feel free to play with
the other example scripts or try write your own.
NB: The layout engine is currently undocumentated

The pixmaps used in gtuner are fully configurable. gtuner comes with
it's own set of pixmaps but you can make your own. If anyone
makes a nice set, please send me a copy.

The gnome panel applet is configurable and has a few basic styles.
One style is the themeable applet. I really need you guys to make
me some cool themes.

Usage:
gtuner should be quite easy to use.
I'm not going to explain it now... right click on the display to get
the main menu.


Finnish this documentation

--------------------------------------------------------------------

Fichier INSTALL avec gedit
--------------------------
p stallation
==================

These are generic installation instructions.

RUN `configure --help' for compile options

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, option?

--------------------------------------------------------------------

je ne comprend pas ??

Merci d'avance, saltutations

Poste le Friday 28 November 2003 21:58:17

Comme prévu tout est expliqué dans le fichier texte install, après la phrase:
The simplest way to compile this package is:....
Tout est là, il suffit de suivre les instructions.
cd vers le répertoire décompressé
./configure
make
Passer en root
puis
make install

Poste le Friday 28 November 2003 22:02:27

C'est la manière la plus courante d'installer un programme à partir des sources. Le fichiers INSTALL contient des explications, et il faut utiliser les commandes :

./configure
make
-> pour la compilation

make install (en root)
-> pour l'installation

Certes, ça change de Install.exe sous Windows mais ce n'est en général pas vraiment plus difficile...

Plusieurs types d'erreurs peuvent survenir lors de la compilation :

- il manque une librairie, dans ce cas il faut l'installer
- le compilateur gcc n'est pas installé ou n'est pas dans la bonne version
- des programmes nécessaires à la complilation (bison, yacc) ne sont pas installés
- il y a des options particulières pour compiler le programme (assez rare)

gcc et tous les outils de compilation sont sur le CD de toutes les distributions. Un simple "urpmi gcc" sera suffisant si tu es sous Mandrake. Il en est de même pour de nombreuses bibiothèques.

[lea-linux.org]

Mais avant d'installer un programme à partir des sources, vérifies toujours s'il n'existe pas de paquet rpm, c'est plsu simple à installer.

Poste le Friday 28 November 2003 22:37:21

Salut,

J'ai tapé comme tu le dit et voila le message (a la fin du message) :

[root@mdk92 gtuner-0.4.0]# ./configure
loading cache ./config.cache
checking for a BSD compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... yes
checking for working aclocal... found
checking for working autoconf... found
checking for working automake... found
checking for working autoheader... found
checking for working makeinfo... found
checking for sed... /bin/sed
checking host system type... i686-pc-linux-gnu
checking for ranlib... ranlib
checking for gcc... gcc
checking whether the C compiler (gcc ) works... yes
checking whether the C compiler (gcc ) is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether gcc accepts -g... yes
checking for ld used by GCC... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking for object suffix... o
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.lo... yes
checking if gcc supports -fno-rtti -fno-exceptions ... no
checking if gcc static flag -static works... none
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the linker (/usr/bin/ld) supports shared libraries... yes
checking command to parse /usr/bin/nm -B output... yes
checking how to hardcode library paths into programs... immediate
checking for /usr/bin/ld option to reload object files... -r
checking dynamic linker characteristics... Linux ld.so
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking for objdir... .libs
creating libtool
checking for gcc... (cached) gcc
checking whether the C compiler (gcc -g -O2 ) works... yes
checking whether the C compiler (gcc -g -O2 ) is a cross-compiler... no
checking whether we are using GNU C... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for a BSD compatible install... /usr/bin/install -c
checking whether ln -s works... (cached) yes
checking whether make sets ${MAKE}... (cached) yes
checking how to run the C preprocessor... gcc -E
checking for unistd.h... yes
checking for getpagesize... yes
checking for working mmap... yes
checking for glib-config... no
checking for GLIB - version >= 1.2.0... no
*** The glib-config script installed by GLIB could not be found
*** If GLIB was installed in PREFIX, make sure PREFIX/bin is in
*** your path, or set the GLIB_CONFIG environment variable to the
*** full path to glib-config.
configure: error: *** GLIB >= 1.2.0 not installed - please install first ***

[root@mdk92 gtuner-0.4.0]# make
make: *** Pas de cibles spécifiées et aucun makefile n'a été trouvé. Arrêt.

[root@mdk92 gtuner-0.4.0]# make install
make: *** Pas de règle pour fabriquer la cible « install ». Arrêt.
[root@mdk92 gtuner-0.4.0]#

Comment Faire ?

Merci davance, salutations

Poste le Friday 28 November 2003 22:41:55

>> GLIB >= 1.2.0 not installed - please install first
C'est le premier cas d'erreur que je viens d'indiquer : il manque une librairie, en l'occurence glib1.2.

Es tu sous Mandrake ? Dans ce cas, tapes "urpmi glib" dans un terminal. Si glib n'est pas sur les CD de Mandrake, tu peux télécharger le paquet rpm à :
[rpmfind.net]

Tu peux également trouver une version à compiler à :
[www.fr.linuxfromscratch.org]

As tu l'ADSL ??? Dans ce cas tu peux configurer les sources pour urpmi et installer beaucoup plus facilement ce genre de logiciels. kwintv existe en rpm...

Poste le Friday 28 November 2003 22:57:49

Déjà on ne sait pas quel est ta distrib. Est elle à base de rpm ? Le package existe pour RedHat, SUSE, Mandrake...
Dans ce cas pas besoin de compilateur...
Pour Mandrake le package se trouve dans contrib.
Si tu es sur Mandrake tu trouveras ici [plf.zarb.org] les instructions pour déclarer contrib comme entrepôt de rpm. Tant que tu y es déclare aussi plf.
Ensuite tu tapes urpmi kwintv et c'est tout.

Poste le Saturday 29 November 2003 06:36:34

Désolé, on sait quel est ta distrib même si tu ne le précises pas...

Poste le Saturday 29 November 2003 06:40:57

Salut,

Je suis sur Mandrake 9.2

Merci d'avance, salutations

Poste le Saturday 29 November 2003 13:35:35

En résumé, voilà ce que tu as à faire :

1) Ajouter des sources pour urpmi : [plf.zarb.org]
2) urpmi glib
3) urpmi kwintv

ça prend 10 minutes !

Poste le Saturday 29 November 2003 14:03:14