Pspp 0.7.4

Marcurse · Le 22/06/2010, à 10:24

Bonjour à tous,

Je travaille depuis quelques temps sous Ubuntu 10.04 LTS si je ne m'abuse. Je fais une étude de marché donc avec plein de stats et de réponses et de tableaux croisés à faire.. Jusque là ca va! C'est ma petite vie.

J'ai pu travailler avec la version de PSPP 0.6.2 (dispo sous synaptic). La prochaine étape de mon travail nécessite des PCA disponibles apparement dans la version de pspp 0.7.4. (une version non officielle)

Je suis donc dans le terminal, j'installe les paquets manquants comme gtk 2.0, zlib ect..

./configure

pspp configure réussi

make

au début ca ne marchait pas, je suis passé sur votre forum, farfouillé un peu, j ai installé les paquets fakeroot, checkinstall et build-essential.

Maintenant je tape "make" et ca lance des check et des trucs que je ne comprends pas en boucle.. je sais pas si je peux avoir le texte du terminal pour mieux expliquer.

En gros apres "make" le terminal se bloque dans une sorte de boucle et à par quitter le terminal, je ne sais que faire.

Voici le tuto de l installation que j'essaye de suivre:

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

These are installation instructions specific to PSPP (including PSPPIRE,
the graphic user interface). These instructions contain the
information most commonly needed by people wishing to build the
program from source. More detailed information can be found in the
generic autoconf manual which is available at
http://www.gnu.org/software/autoconf/manual/html_node/Running-configure-Scripts.html

The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation.

If you need to do unusual things to compile the package, please
report the problem to bug-gnu-pspp@gnu.org. We will try to figure out
how `configure' could work better in your situation for the next
release.

The simplest way to compile PSPP is:

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

You may invoke `configure' with --help to see what options are
available. The most common of these are listed under "Optional
Features", below.

It is best to build and install PSPP in directories whose names do
not contain unusual characters such as spaces or single-quotes, due
to limitations of the tools involved in the build process.

If you installed some of the libraries that PSPP uses in a
non-standard location (on many systems, anywhere other than
/usr), you may need to provide some special flags to `configure'
to tell it where to find them. For example, on GNU/Linux, if you
installed some libraries in /usr/local, then you need to invoke
it with at least the following options:

./configure LDFLAGS='-L/usr/local/lib -Wl,-rpath,/usr/local/lib' CPPFLAGS='-I/usr/local/include'

Running `configure' takes awhile. While running, it prints some
messages telling which features it is checking for.

If `configure' completes successfully, it prints the message
"PSPP configured successfully." at the end of its run.
Otherwise, it may stop with a list of packages that you must
install before PSPP. If it does, you need to install those
packages, then re-run this step. Some prerequisites may be
omitted by passing a --without-<feature> flag to `configure' (see
"Optional Features", below). If you use one of these flags, then
the feature that it disables will not be available in your PSPP
installation.

`configure' may also print a list of packages that you should
consider installing. If you install them, then re-run
`configure', additional features will be available in your PSPP
installation.

2. Type `make' to compile the package. mon problème est ici

3. Optionally, type `make check' to run the self-tests that come
with the package. If any of the self-tests fail, please mail
bug-gnu-pspp@gnu.org with the details, to give the PSPP
developers an opportunity to fix the problem in the next release.

4. Type `make install' to install the programs and any data files
and documentation. Ordinarily you will need root permissions to
do this. The "su" and "sudo" commands are common ways to obtain
root permissions. If you cannot get root permissions, see
"Installation Names", below.

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

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

Some systems may 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

See "Defining Variables", below, for more details.

Installation Names
==================

By default, `make install' installs PSPP's commands under
`/usr/local/bin', data files under `/usr/local/share', etc. You
can specify an installation prefix other than `/usr/local' by giving
`configure' the option `--prefix=PREFIX'.

You may wish to install PSPP on a machine where you do not have
root permissions. To do so, specify a prefix relative within your
home directory, e.g. `--prefix=$HOME' or `--prefix=$HOME/inst'. All
PSPP files will be installed under the prefix directory, which `make
install' will create if necessary. You may run PSPP directly from the
`bin' directory under the prefix directory as, e.g., `~/inst/bin/pspp'
under most shells, or for added convenience you can add the
installation directory to your PATH by editing a shell startup file
such as `.bashrc'.

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.

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

Si vous avez des soluces ou autres conseils. Je suis preneur!
J'ai aussi songé à R. mais... j'ai été formé sur spss alors si je pouvais gérer pspp..

Merci à tous en tout cas.

Bonne journée

Michel Leunen · Le 22/06/2010, à 10:28

Ca ressemble à une compilation de programme tout à fait normale.
Es-tu sûr que ton make tourne en boucle? Ca peut être (très) long une compilation.
As-tu essayé après le ./configure de faire un make check à la place du make tout simple. Et est-ce que ça renvoie des erreurs ?

Marcurse · Le 22/06/2010, à 10:34

Je vais lancer un make check et vous dire..

Marcurse · Le 22/06/2010, à 10:40

Alors le make check fait de meme il tourne en boucle. par contre il doit me manquer des paquets ou qqchose.

config.status: executing libtool commands
sed: can't read ./ltmain.sh: No such file or directory
sed: can't read ./ltmain.sh: No such file or directory
mv: cannot stat `libtoolT': No such file or directory
cp: cannot stat `libtoolT': No such file or directory
chmod: cannot access `libtool': No such file or directory
CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/bash /home/infoevent/Bureau/pspp/pspp-0.7.4/missing --run aclocal-1.11 -I m4 -I gl/m4
/home/infoevent/Bureau/pspp/pspp-0.7.4/missing: line 52: aclocal-1.11 : commande introuvable
WARNING: `aclocal-1.11' is missing on your system. You should only need it if
you modified `acinclude.m4' or `configure.ac'. You might want
to install the `Automake' and `Perl' packages. Grab them from
any GNU archive site.
cd . && /bin/bash /home/infoevent/Bureau/pspp/pspp-0.7.4/missing --run automake-1.11 --gnu
/home/infoevent/Bureau/pspp/pspp-0.7.4/missing: line 52: automake-1.11 : commande introuvable
WARNING: `automake-1.11' is missing on your system. You should only need it if
you modified `Makefile.am', `acinclude.m4' or `configure.ac'.
You might want to install the `Automake' and `Perl' packages.
Grab them from any GNU archive site.
CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/bash /home/infoevent/Bureau/pspp/pspp-0.7.4/missing --run autoconf
/home/infoevent/Bureau/pspp/pspp-0.7.4/missing: line 52: autoconf : commande introuvable
WARNING: `autoconf' is missing on your system. You should only need it if
you modified `configure.ac'. You might want to install the
`Autoconf' and `GNU m4' packages. Grab them from any GNU
archive site.
/bin/bash ./config.status --recheck
running CONFIG_SHELL=/bin/bash /bin/bash ./configure --no-create --no-recursion
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking build system type... i686-pc-linux-gnu

Je n avais pu interrompre la boucle avant donc je ne voyais pas le probleme. Apparement il manque des lignes dans le programme que j'ai chopé

Marcurse · Le 22/06/2010, à 10:44

Je vais telecharger les paquets "autoconf" et "perl" aussi

Michel Leunen · Le 22/06/2010, à 10:46

Marcurse a écrit :

sed: can't read ./ltmain.sh: No such file or directory
sed: can't read ./ltmain.sh: No such file or directory
Je n avais pu interrompre la boucle avant donc je ne voyais pas le probleme. Apparement il manque des lignes dans le programme que j'ai chopé

Il manque au moins ce fichier-là, oui.

Marcurse · Le 22/06/2010, à 10:46

Apres avoir installé autoconf (la version de perl était déja la plus récente):

/Bureau/pspp/pspp-0.7.4$ make check
CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/bash /home/infoevent/Bureau/pspp/pspp-0.7.4/missing --run aclocal-1.11 -I m4 -I gl/m4
aclocal-1.11: aclocal: file `m4/lt~obsolete.m4' does not exist
make: *** [aclocal.m4] Erreur 1

Marcurse · Le 22/06/2010, à 11:00

Je continue ma petite progression:

J'ai donc réinstallé le paquet contenant le fichier ltmain.

J'ai relancé le make check:

gperf -m 10 ./iconv_open-aix.gperf > ./iconv_open-aix.h-t
/bin/bash: gperf : commande introuvable
make[2]: *** [iconv_open-aix.h] Erreur 127
make[2]: quittant le répertoire « /home/infoevent/Bureau/pspp/pspp-0.7.4/gl »
make[1]: *** [check-recursive] Erreur 1
make[1]: quittant le répertoire « /home/infoevent/Bureau/pspp/pspp-0.7.4 »
make: *** [check] Erreur 2

Michel Leunen · Le 22/06/2010, à 11:06

Je suppose que si tu installe gperf, cela passera.
Tu es sûr que le ./configure est passé sans donner d'erreurs ? Parce que c'est son rôle de tester ce genre de truc.

Marcurse · Le 22/06/2010, à 11:24

Apparement:

configure: creating ./config.status
config.status: creating Makefile
config.status: creating gl/Makefile
config.status: creating tests/atlocal
config.status: creating perl-module/lib/PSPP.pm
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing tests/atconfig commands
config.status: executing depfiles commands
config.status: executing libtool commands
PSPP configured successfully.

Marcurse · Le 22/06/2010, à 14:54

Après moults modifs, paquets... j'ai lancé un dernier test:

Test Summary Report
-------------------
t/Pspp.t (Wstat: 512 Tests: 0 Failed: 0)
  Non-zero exit status: 2
  Parse errors: Bad plan.  You planned 36 tests but ran 0.
Files=1, Tests=0,  0 wallclock secs ( 0.04 usr  0.01 sys +  0.03 cusr  0.02 csys =  0.10 CPU)
Result: FAIL
Failed 1/1 test programs. 0/0 subtests failed.
make[4]: *** [test_dynamic] Error 2
make[4]: Leaving directory `/home/infoevent/Bureau/pspp/pspp-0.7.4/perl-module'
make[3]: *** [perl_module_check] Erreur 2
make[3]: quittant le répertoire « /home/infoevent/Bureau/pspp/pspp-0.7.4 »
make[2]: *** [check-am] Erreur 2
make[2]: quittant le répeTest Summary Report
-------------------
t/Pspp.t (Wstat: 512 Tests: 0 Failed: 0)
  Non-zero exit status: 2
  Parse errors: Bad plan.  You planned 36 tests but ran 0.
Files=1, Tests=0,  0 wallclock secs ( 0.04 usr  0.01 sys +  0.03 cusr  0.02 csys =  0.10 CPU)
Result: FAIL
Failed 1/1 test programs. 0/0 subtests failed.
make[4]: *** [test_dynamic] Error 2
make[4]: Leaving directory `/home/infoevent/Bureau/pspp/pspp-0.7.4/perl-module'
make[3]: *** [perl_module_check] Erreur 2
make[3]: quittant le répertoire « /home/infoevent/Bureau/pspp/pspp-0.7.4 »
make[2]: *** [check-am] Erreur 2
make[2]: quittant le répertoire « /home/infoevent/Bureau/pspp/pspp-0.7.4 »
make[1]: *** [check-recursive] Erreur 1
make[1]: quittant le répertoire « /home/infoevent/Bureau/pspp/pspp-0.7.4 »
make: *** [check] Erreur 2
rtoire « /home/infoevent/Bureau/pspp/pspp-0.7.4 »
make[1]: *** [check-recursive] Erreur 1
make[1]: quittant le répertoire « /home/infoevent/Bureau/pspp/pspp-0.7.4 »
make: *** [check] Erreur 2

Si qqun à une idée..
Merci à vous et merci Michel

Michel Leunen · Le 22/06/2010, à 16:31

Je n'ai aucune idée de ce que tout cela veut dire
Je te conseillerais de contacter celui qui a écrit le programme. Il est quand même le plus à même de t'aider

Ubuntu-fr

Navigation

Liens de recherche

Annonce

#1 Le 22/06/2010, à 10:24

Pspp 0.7.4

#2 Le 22/06/2010, à 10:28

Re : Pspp 0.7.4

#3 Le 22/06/2010, à 10:34

Re : Pspp 0.7.4

#4 Le 22/06/2010, à 10:40

Re : Pspp 0.7.4

#5 Le 22/06/2010, à 10:44

Re : Pspp 0.7.4

#6 Le 22/06/2010, à 10:46

Re : Pspp 0.7.4

#7 Le 22/06/2010, à 10:46

Re : Pspp 0.7.4

#8 Le 22/06/2010, à 11:00

Re : Pspp 0.7.4

#9 Le 22/06/2010, à 11:06

Re : Pspp 0.7.4

#10 Le 22/06/2010, à 11:24

Re : Pspp 0.7.4

#11 Le 22/06/2010, à 14:54

Re : Pspp 0.7.4

#12 Le 22/06/2010, à 16:31

Re : Pspp 0.7.4

Pied de page des forums