#1 Le 13/08/2010, à 13:36
- jmercanton
[résolu]comment reconnaitre un fichier excutable ?
Bonjour le forum,
j'ai installé le logiciel Screem par l'intermédiaire de Alien qui a transformer l'arche téléchargée en un document avec une extension.deb.
J'ai suivi le tuto qui est donnée ici http://ubuntu7.canalblog.com/archives/2007/10/26/6668683.html
Je suis coincé pour retrouver le fichier exécutable afin de pouvoir lancer le programme.
j'ai bien regardé dans la "fenêtre fichier inclus" qui est affichée dans l'installateur de paquet, mais je ne sais pas comment reconnaitre ce fichier exécutable.
Merci d'avance pour l'aide.
Dernière modification par jmercanton (Le 13/08/2010, à 15:52)
Hors ligne
#2 Le 13/08/2010, à 13:41
- helly
Re : [résolu]comment reconnaitre un fichier excutable ?
Bonjour.
Via le terminal va dans le dossier en question, puis fais un
ls -al.
Archlinux-wmii-dwb.
Un problème résolu ? Faites le savoir en mettant [résolu] à côté du titre de votre topic.
Un problème non résolu ? Faites le savoir en insultant ceux qui cherchent à vous aider.
Un site bleu super remasterised©, un wiki cherchant des volontaires pour traduire un site.
Hors ligne
#3 Le 13/08/2010, à 13:50
- jmercanton
Re : [résolu]comment reconnaitre un fichier excutable ?
Merci pour la réponse express,
voici ce que me retourne le terminal
jmichel@serverjm:~$ cd /screem-0.16.1/
jmichel@serverjm:/screem-0.16.1$ ls -al
total 2200
drwxrwxrwx 19 jmichel jmichel 4096 2010-08-13 13:22 .
drwxr-xr-x 23 root root 4096 2010-08-13 13:22 ..
-rw-r--r-- 1 jmichel jmichel 18083 2001-08-19 20:11 ABOUT-NLS
-rw-r--r-- 1 jmichel jmichel 286419 2005-11-12 20:36 aclocal.m4
-rw-r--r-- 1 jmichel jmichel 507 2004-09-26 21:52 AUTHORS
-rw-r--r-- 1 jmichel jmichel 156 2002-12-09 19:14 BUGS
-rw-r--r-- 1 jmichel jmichel 402203 2005-11-16 00:02 ChangeLog
-rwxr-xr-x 1 jmichel jmichel 3707 2005-11-12 20:36 compile
-rwxr-xr-x 1 jmichel jmichel 43499 2005-11-12 20:36 config.guess
-rw-r--r-- 1 jmichel jmichel 4114 2005-11-12 20:36 config.h.in
-rwxr-xr-x 1 jmichel jmichel 31743 2005-11-12 20:36 config.sub
-rwxr-xr-x 1 jmichel jmichel 886444 2005-11-12 20:36 configure
-rw-r--r-- 1 jmichel jmichel 8998 2005-11-12 20:36 configure.ac
-rw-r--r-- 1 jmichel jmichel 18002 2005-05-06 06:17 COPYING
-rw-r--r-- 1 jmichel jmichel 18114 2005-05-06 06:17 COPYING-DOCS
drwxrwxrwx 4 jmichel jmichel 4096 2010-08-13 13:22 data
-rwxr-xr-x 1 jmichel jmichel 15936 2005-11-12 20:36 depcomp
drwxrwxrwx 3 jmichel jmichel 4096 2010-08-13 13:22 docs
drwxrwxrwx 2 jmichel jmichel 4096 2010-08-13 13:22 dtd
drwxrwxrwx 2 jmichel jmichel 4096 2010-08-13 13:22 gdl
drwxrwxrwx 2 jmichel jmichel 4096 2010-08-13 13:22 glade
drwxrwxrwx 5 jmichel jmichel 4096 2010-08-13 13:22 helpers
drwxrwxrwx 2 jmichel jmichel 4096 2010-08-13 13:22 hints
drwxrwxrwx 2 jmichel jmichel 4096 2010-08-13 13:22 include
-rw-r--r-- 1 jmichel jmichel 9478 2005-07-01 21:50 INSTALL
-rwxr-xr-x 1 jmichel jmichel 9233 2005-11-12 20:36 install-sh
-rw-r--r-- 1 jmichel jmichel 22424 2005-11-12 20:36 intltool-extract.in
-rw-r--r-- 1 jmichel jmichel 35216 2005-11-12 20:36 intltool-merge.in
-rw-r--r-- 1 jmichel jmichel 27009 2005-11-12 20:36 intltool-update.in
drwxrwxrwx 5 jmichel jmichel 4096 2010-08-13 13:22 libegg
-rw-r--r-- 1 jmichel jmichel 187039 2005-10-25 06:41 ltmain.sh
-rw-r--r-- 1 jmichel jmichel 1406 2005-09-14 21:19 Makefile.am
-rw-r--r-- 1 jmichel jmichel 27090 2005-11-12 20:36 Makefile.in
-rwxr-xr-x 1 jmichel jmichel 11014 2005-11-12 20:36 missing
-rwxr-xr-x 1 jmichel jmichel 3474 2005-11-12 20:36 mkinstalldirs
-rw-r--r-- 1 jmichel jmichel 771 2001-08-19 20:11 NEWS
drwxrwxrwx 2 jmichel jmichel 4096 2010-08-13 13:22 pixmaps
drwxrwxrwx 11 jmichel jmichel 4096 2010-08-13 13:22 plugins
drwxrwxrwx 2 jmichel jmichel 4096 2010-08-13 13:22 po
-rw-r--r-- 1 jmichel jmichel 1849 2005-06-04 20:59 README
drwxrwxrwx 8 jmichel jmichel 4096 2010-08-13 13:22 resources
-rw-r--r-- 1 jmichel jmichel 505 2004-07-27 05:06 screem.applications
-rw-r--r-- 1 jmichel jmichel 537 2005-01-07 01:59 screem.desktop.in
-rw-r--r-- 1 jmichel jmichel 4760 2001-08-19 20:12 screem.png
-rw-r--r-- 1 jmichel jmichel 14609 2005-10-20 15:22 screem.schemas.in
-rw-r--r-- 1 jmichel jmichel 7447 2004-11-18 02:23 screem.spec
drwxrwxrwx 2 jmichel jmichel 4096 2010-08-13 13:22 splash
drwxrwxrwx 2 jmichel jmichel 4096 2010-08-13 13:22 src
drwxrwxrwx 2 jmichel jmichel 4096 2010-08-13 13:22 tests
-rw-r--r-- 1 jmichel jmichel 81 2003-09-13 18:46 TODO
drwxrwxrwx 2 jmichel jmichel 4096 2010-08-13 13:22 uiet maintenant?? je dois choisir lequel la dedans??
Hors ligne
#4 Le 13/08/2010, à 13:52
- helly
Re : [résolu]comment reconnaitre un fichier excutable ?
Hé bien déjà on peut voir que tout ceux qui sont marqués « x » sont executables.
Ensuite je pense que le fichier à lancer doit être spécifié dans le README !
À vue de nez je dirai que c'est install-sh qu'il faut lancer.
Archlinux-wmii-dwb.
Un problème résolu ? Faites le savoir en mettant [résolu] à côté du titre de votre topic.
Un problème non résolu ? Faites le savoir en insultant ceux qui cherchent à vous aider.
Un site bleu super remasterised©, un wiki cherchant des volontaires pour traduire un site.
Hors ligne
#5 Le 13/08/2010, à 14:06
- jmercanton
Re : [résolu]comment reconnaitre un fichier excutable ?
voici ce qui est écrit dans le fichier README
Screem (C) 1999-2005 David A Knight
- see COPYING for license information
==========================================================================
Screem is a website development environment. Its purpose is to increase
productivity when constructing a web site by providing quick access to
commonly used features of web sites (such as tables). It is written for
use with the GNOME (http://www.gnome.org) desktop environment
Unlike most other website/html editors screem *does not* provide a WYSIWYG
display of the page, but instead just gives you the raw html source code in
its editor window. This enables you to type the html you want and also
quickly add commonly used tags by using the features provided. The reasoning
behind this is that WYSIWYG editors, in general, do not produce good valid
html and also can slow you down if they do not support a tag that you wish
to insert, therefore by just having the source shown to be edited you can
type what you want when you want, but also have the ease of use of clicking
a button to have the tag(s) you want inserted.
One of the main features is the html tag list. This provides a tree that,
with one click, you can add the tag you want into the source. The tree
is entirely configurable from the programs preferences allowing you to add
whatever tags you want and also the tag options to use for them.
Screem features a plugin system where developers can write their own
features as a module and have Screem load it in at run time. The plugins
have complete access to the UI and as such can add things to it, such as
menu entries for the plugin, or a new toolbar icon.
The image wizard button pixmap on the toolbar is from gwp, the folder icons
in the filelist are from gmc, the rest are standard Gnome icons.
The screem program icon is by Matthew J Gardner (matthew@screem.org)J'ai essayé de double cliquer sur install-sh mais ca ouvre une fenêtre avec les boutons lancer /lancer dans le terminal /afficher.
Aucun de ses bouton ne me lance le programme.
Hors ligne
#6 Le 13/08/2010, à 14:10
- yannzbig
Re : [résolu]comment reconnaitre un fichier excutable ?
Qu'y a t-il dans le fichier INSTALL ? On dirait un descriptif de l'install justement.
#7 Le 13/08/2010, à 14:10
- helly
Re : [résolu]comment reconnaitre un fichier excutable ?
Qu'y a t'il dans le fichier INSTALL ?
Archlinux-wmii-dwb.
Un problème résolu ? Faites le savoir en mettant [résolu] à côté du titre de votre topic.
Un problème non résolu ? Faites le savoir en insultant ceux qui cherchent à vous aider.
Un site bleu super remasterised©, un wiki cherchant des volontaires pour traduire un site.
Hors ligne
#8 Le 13/08/2010, à 14:22
- jmercanton
Re : [résolu]comment reconnaitre un fichier excutable ?
voici le contenu du fichier install
Screem (C) 1999-2005 David A Knight
- see COPYING for license information
==========================================================================
Screem is a website development environment. Its purpose is to increase
productivity when constructing a web site by providing quick access to
commonly used features of web sites (such as tables). It is written for
use with the GNOME (http://www.gnome.org) desktop environment
Unlike most other website/html editors screem *does not* provide a WYSIWYG
display of the page, but instead just gives you the raw html source code in
its editor window. This enables you to type the html you want and also
quickly add commonly used tags by using the features provided. The reasoning
behind this is that WYSIWYG editors, in general, do not produce good valid
html and also can slow you down if they do not support a tag that you wish
to insert, therefore by just having the source shown to be edited you can
type what you want when you want, but also have the ease of use of clicking
a button to have the tag(s) you want inserted.
One of the main features is the html tag list. This provides a tree that,
with one click, you can add the tag you want into the source. The tree
is entirely configurable from the programs preferences allowing you to add
whatever tags you want and also the tag options to use for them.
Screem features a plugin system where developers can write their own
features as a module and have Screem load it in at run time. The plugins
have complete access to the UI and as such can add things to it, such as
menu entries for the plugin, or a new toolbar icon.
The image wizard button pixmap on the toolbar is from gwp, the folder icons
in the filelist are from gmc, the rest are standard Gnome icons.
The screem program icon is by Matthew J Gardner (matthew@screem.org)Hors ligne
#9 Le 13/08/2010, à 14:24
- jmercanton
Re : [résolu]comment reconnaitre un fichier excutable ?
oups!!!
petite erreur
voici le fichier install
Installation Instructions
*************************
Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005 Free
Software Foundation, Inc.
This file is free documentation; the Free Software Foundation gives
unlimited permission to copy, distribute and modify it.
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, 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 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. 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=c89 CFLAGS=-O2 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 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 support 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=PREFIX'.
You can specify separate installation prefixes for
architecture-specific files and architecture-independent files. If you
give `configure' the option `--exec-prefix=PREFIX', the package will
use PREFIX 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=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 `--target=TYPE' option 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). Here is a another example:
/bin/bash ./configure CONFIG_SHELL=/bin/bash
Here the `CONFIG_SHELL=/bin/bash' operand causes subsequent
configuration-related scripts to be executed by `/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.Hors ligne
#10 Le 13/08/2010, à 14:24
- helly
Re : [résolu]comment reconnaitre un fichier excutable ?
Tain c'est quoi ces fichiers qui servent à rien ? >_<
Archlinux-wmii-dwb.
Un problème résolu ? Faites le savoir en mettant [résolu] à côté du titre de votre topic.
Un problème non résolu ? Faites le savoir en insultant ceux qui cherchent à vous aider.
Un site bleu super remasterised©, un wiki cherchant des volontaires pour traduire un site.
Hors ligne
#11 Le 13/08/2010, à 14:27
- jmercanton
Re : [résolu]comment reconnaitre un fichier excutable ?
je n'ai pas compris ce que tu veux dire par cette question
Hors ligne
#12 Le 13/08/2010, à 14:29
- helly
Re : [résolu]comment reconnaitre un fichier excutable ?
Non c'était pas vraiment une question ^^.
Je me renseigne…
Archlinux-wmii-dwb.
Un problème résolu ? Faites le savoir en mettant [résolu] à côté du titre de votre topic.
Un problème non résolu ? Faites le savoir en insultant ceux qui cherchent à vous aider.
Un site bleu super remasterised©, un wiki cherchant des volontaires pour traduire un site.
Hors ligne
#13 Le 13/08/2010, à 14:30
- helly
Re : [résolu]comment reconnaitre un fichier excutable ?
Ho !
Tu as essayé la manipulation :
./configure && make && sudo make install?
Archlinux-wmii-dwb.
Un problème résolu ? Faites le savoir en mettant [résolu] à côté du titre de votre topic.
Un problème non résolu ? Faites le savoir en insultant ceux qui cherchent à vous aider.
Un site bleu super remasterised©, un wiki cherchant des volontaires pour traduire un site.
Hors ligne
#14 Le 13/08/2010, à 14:31
- jmercanton
Re : [résolu]comment reconnaitre un fichier excutable ?
ok
Alors je te laisse décortiquer le contenu du fichier install
Si tu trouve une info dans ce fichier, je te remercie de bien vouloir m'indiquer comment je vais finalement pouvoir faire apparaitre ce logiciel sur mon écran.:rolleyes:
merci en tout cas pour ton aide
Hors ligne
#15 Le 13/08/2010, à 14:33
- helly
Re : [résolu]comment reconnaitre un fichier excutable ?
T'as essayé mon idée ?
Archlinux-wmii-dwb.
Un problème résolu ? Faites le savoir en mettant [résolu] à côté du titre de votre topic.
Un problème non résolu ? Faites le savoir en insultant ceux qui cherchent à vous aider.
Un site bleu super remasterised©, un wiki cherchant des volontaires pour traduire un site.
Hors ligne
#16 Le 13/08/2010, à 14:36
- yannzbig
Re : [résolu]comment reconnaitre un fichier excutable ?
Comme l'as dit helly, il faut compiler les sources dans un terminal et dans le bon répertoire:
./configure
make
sudo make install#17 Le 13/08/2010, à 14:36
- jmercanton
Re : [résolu]comment reconnaitre un fichier excutable ?
voici ce que ca donne
jmichel@serverjm:/screem-0.16.1$ ./configure && make && sudo make install
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for style of include used by make... GNU
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking dependency style of gcc... gcc3
checking for a sed that does not truncate output... /bin/sed
checking for egrep... grep -E
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for /usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognise dependent libraries... pass_all
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking for g77... no
checking for f77... no
checking for xlf... no
checking for frt... no
checking for pgf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for f90... no
checking for xlf90... no
checking for pgf90... no
checking for epcf90... no
checking for f95... no
checking for fort... no
checking for xlf95... no
checking for ifc... no
checking for efc... no
checking for pgf95... no
checking for lf95... no
checking for gfortran... no
checking whether we are using the GNU Fortran 77 compiler... no
checking whether accepts -g... no
checking the maximum length of command line arguments... 32768
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking if gcc static flag works... yes
checking if gcc supports -fno-rtti -fno-exceptions... no
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 whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC
checking if g++ PIC flag -fPIC works... yes
checking if g++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
appending configuration tag "F77" to libtool
checking for library containing strerror... none required
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ANSI C... (cached) none needed
checking dependency style of gcc... (cached) gcc3
checking for ANSI C header files... (cached) yes
checking for gconftool-2... /usr/bin/gconftool-2
checking for intltool >= 0.29... 0.34.1 found
checking for perl... /usr/bin/perl
checking for XML::Parser... ok
checking for iconv... /usr/bin/iconv
checking for msgfmt... /usr/bin/msgfmt
checking for msgmerge... /usr/bin/msgmerge
checking for xgettext... /usr/bin/xgettext
checking for pkg-config... /usr/bin/pkg-config
checking for GLIB - version >= 2.5.6... no
*** Could not run GLIB test program, checking why...
*** The test program failed to compile or link. See the file config.log for the
*** exact error that occured. This usually means GLIB is incorrectly installed.
configure: error:
*** GLIB 2.5.6 or better is required. The latest version of
*** GLIB is always available from ftp://ftp.gtk.org/.
jmichel@serverjm:/screem-0.16.1$Hors ligne
#18 Le 13/08/2010, à 14:40
- helly
Re : [résolu]comment reconnaitre un fichier excutable ?
Ça y est on tiend le bon bout !!!
Après c'est juste qu'il te manque des paquets :
Fais un
sudo apt-get install glibc-2.10-1Puis relance la manip.
Archlinux-wmii-dwb.
Un problème résolu ? Faites le savoir en mettant [résolu] à côté du titre de votre topic.
Un problème non résolu ? Faites le savoir en insultant ceux qui cherchent à vous aider.
Un site bleu super remasterised©, un wiki cherchant des volontaires pour traduire un site.
Hors ligne
#19 Le 13/08/2010, à 14:41
- jmercanton
Re : [résolu]comment reconnaitre un fichier excutable ?
Ok voici ce que ca donne
jmichel@serverjm:/screem-0.16.1$ sudo apt-get install glibc-2.10-1
[sudo] password for jmichel:
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
Note, sélection de libc6 au lieu de glibc-2.10-1
libc6 est déjà la plus récente version disponible.
Les paquets suivants ont été installés automatiquement et ne sont plus nécessaires :
libparted0
Veuillez utiliser « apt-get autoremove » pour les supprimer.
0 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour.
jmichel@serverjm:/screem-0.16.1$Hors ligne
#20 Le 13/08/2010, à 14:46
- jmercanton
Re : [résolu]comment reconnaitre un fichier excutable ?
ok j'ai rentré la commance
jmichel@serverjm:/screem-0.16.1$ ./configure && make && sudo make install
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for style of include used by make... GNU
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking dependency style of gcc... gcc3
checking for a sed that does not truncate output... /bin/sed
checking for egrep... grep -E
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for /usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognise dependent libraries... pass_all
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking for g77... no
checking for f77... no
checking for xlf... no
checking for frt... no
checking for pgf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for f90... no
checking for xlf90... no
checking for pgf90... no
checking for epcf90... no
checking for f95... no
checking for fort... no
checking for xlf95... no
checking for ifc... no
checking for efc... no
checking for pgf95... no
checking for lf95... no
checking for gfortran... no
checking whether we are using the GNU Fortran 77 compiler... no
checking whether accepts -g... no
checking the maximum length of command line arguments... 32768
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking if gcc static flag works... yes
checking if gcc supports -fno-rtti -fno-exceptions... no
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 whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC
checking if g++ PIC flag -fPIC works... yes
checking if g++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
appending configuration tag "F77" to libtool
checking for library containing strerror... none required
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ANSI C... (cached) none needed
checking dependency style of gcc... (cached) gcc3
checking for ANSI C header files... (cached) yes
checking for gconftool-2... /usr/bin/gconftool-2
checking for intltool >= 0.29... 0.34.1 found
checking for perl... /usr/bin/perl
checking for XML::Parser... ok
checking for iconv... /usr/bin/iconv
checking for msgfmt... /usr/bin/msgfmt
checking for msgmerge... /usr/bin/msgmerge
checking for xgettext... /usr/bin/xgettext
checking for pkg-config... /usr/bin/pkg-config
checking for GLIB - version >= 2.5.6... no
*** Could not run GLIB test program, checking why...
*** The test program failed to compile or link. See the file config.log for the
*** exact error that occured. This usually means GLIB is incorrectly installed.
configure: error:
*** GLIB 2.5.6 or better is required. The latest version of
*** GLIB is always available from ftp://ftp.gtk.org/.
jmichel@serverjm:/screem-0.16.1$Hors ligne
#21 Le 13/08/2010, à 15:18
- inbox
Re : [résolu]comment reconnaitre un fichier excutable ?
Salut,
Une autre solution est d'installer le deb de screem-0.16.1 pour Hardy. Ce paquet n'est plus disponible sous Lucid.
Il n'y a pas de version plus récente.
A+
Un problème résolu ? Indiquez le en modifiant le titre du sujet.
Hors ligne
#22 Le 13/08/2010, à 15:51
- jmercanton
Re : [résolu]comment reconnaitre un fichier excutable ?
Bon bin!!
cette solution fonctionne:lol:
j'ai installé cette version
http://fr.archive.ubuntu.com/ubuntu/pool/main/s/screem/screem_0.16.1-4.2ubuntu1_i386.deb
je retrouve le lancer dans Application / Programmation
le programme s'ouvre, c'est super !!
Un très grand merci pour l'aide de tous.
bonne journée
Hors ligne