pspp-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: PSPP Perl Module Installation Issues


From: Pierre Ayres
Subject: Re: PSPP Perl Module Installation Issues
Date: Thu, 17 Jan 2013 13:37:34 +0200

This is what happens now:

$./configure --without-gui --without-cairo --without-libncurses
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... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
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 ISO C89... none needed
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -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 minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
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 ISO C89... (cached) none needed
checking dependency style of gcc... (cached) gcc3
./configure: line 5157: gl_EARLY: command not found
checking whether gcc and cc understand -c and -o together... yes
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking how to print strings... printf
checking for a sed that does not truncate output... /bin/sed
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking how to convert x86_64-unknown-linux-gnu file names to x86_64-unknown-linux-gnu format... func_convert_file_noop
checking how to convert x86_64-unknown-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... dlltool
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for mt... mt
checking if mt is a manifest tool... no
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) 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 for shl_load... no
checking for shl_load in -ldld... no
checking for dlopen... no
checking for dlopen in -ldl... yes
checking whether a program can dlopen itself... yes
checking whether a statically linked program can dlopen itself... no
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... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking whether makeinfo supports @clicksequence... no
checking whether gcc accepts -Wdeclaration-after-statement... yes
checking for perl... /usr/bin/perl
./configure: line 13081: syntax error near unexpected token `external,'
./configure: line 13081: `AM_GNU_GETTEXT(external, need-ngettext)'

$ make
make: *** No targets specified and no makefile found.  Stop.



On Tue, Jan 15, 2013 at 8:00 PM, John Darrington <address@hidden> wrote:
On Tue, Jan 15, 2013 at 12:50:49PM +0200, Pierre Ayres wrote:

     I am running Ubuntu 12.04.1, I have Perl 5.14.2 installed, I have also
     installed GCC.
     I have the source files for PSPP 0.7.9.

     When running "/usr/bin/perl Makefile.PL" for the Perl module I get the
     following "error".

     "Enter the location of the build directory of the configured pspp source:
     []
     Checking if your kit is complete...
     Looks good
     Could not open '/src/libpspp/version.c': No such file or directory at
     /usr/local/share/perl/5.14.2/ExtUtils/MM_Unix.pm line 2637."

     I realize I need to give some directory of sorts but a 'locate' does not
     find this file anywhere on my box.

     Assuming I need to "compile?" PSPP first then I am stuck again as I have no
     idea how to do this in 'dummies' steps.


I did some brief experiments today, and it seems that installing the perl module
without the rest of PSPP is not as easy as it could be.

Basically you are right, you will need to compile PSPP first, but you don't need
to install it.  At a risk of contradicting that sentence, you should follow the
instructions in the file called INSTALL.  However, to save yourself a bit of
time and from having to install lots of things you won't need, you can pass
various --without-* flags to configure, thus:

./configure --without-gui --without-cairo --without-libncurses
make
cd perl-module
make install


Hope this helps.

J'


--
PGP Public key ID: 1024D/2DE827B3
fingerprint = 8797 A26D 0854 2EAB 0285  A290 8A67 719C 2DE8 27B3
See http://keys.gnupg.net or any PGP keyserver for public key.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAlD1mT8ACgkQimdxnC3oJ7M3KACfRtr/TESMBBAp77U3/UPSVEZd
nxMAn2F5qz52LcT/hLtp93Y4SE6GNBcN
=X2Q3
-----END PGP SIGNATURE-----



reply via email to

[Prev in Thread] Current Thread [Next in Thread]