OpenOffice compiling problem

Paingiver · 2008-04-04 14:04:40

Hi i am trying to compile openoffice.org 2.4.0, i have installed every dependency listed in this site: http://tools.openoffice.org/dev_docs/build_linux.html
But when i type ./configure i receive an error:

checking which package format to use... rpm
checking for rpm... configure: error: not found

I am getting frustrated what does it have to do with rpm? And all the configure output:

********************************************************************
*                                                                  *
*   Checking the platform pre-requisites.                          *
*                                                                  *
********************************************************************

checking for egrep... grep -E
checking for gawk... gawk
checking for gawk... /bin/gawk
checking for sed... /bin/sed
checking for solenv environment... default
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking whether to enable crashdump feature... no
checking whether to turn warnings to errors... no
checking whether to do a debug build... no
checking whether to build with additional debug utilities... no, full product build
checking whether to include symbols into final build... no
checking whether to strip the solver or not.... checking whether to enable native CUPS support... yes
checking whether to enable fontconfig support... yes
checking whether to enable filters for legacy binary file formats (StarOffice 5.2)... yes
checking whether to use RPATH in shared libraries... yes
checking whether to include MySpell dictionaries... yes
checking which shell to use... tcsh
checking for tcsh... /usr/bin/tcsh
checking gcc home... /usr
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 for gcc... /usr/bin/gcc
checking the GNU gcc compiler version... checked (gcc 4.2.3)
checking whether gcc supports -fvisibility=hidden... yes
checking whether to enable pch feature... no
checking for GNU make... make
checking the GNU make version... make 3.81
checking for --hash-style=both linker support ... found 
checking for perl... /usr/bin/perl
checking the Perl version... checked (perl 5)
checking for required Perl modules... all modules found
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking how to run the C++ preprocessor... g++ -E
checking how to run the C preprocessor... gcc -E
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 for long... yes
checking size of long... 4
checking whether byte ordering is bigendian... no
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... 64
checking for _LARGE_FILES value needed for large files... no
checking whether to disable vba feature... no
checking how to package the vba compatibility api... defaulting to build as uno extension
checking cups/cups.h usability... yes
checking cups/cups.h presence... yes
checking for cups/cups.h... yes
checking whether to enable pam support... yes
checking security/pam_appl.h usability... yes
checking security/pam_appl.h presence... yes
checking for security/pam_appl.h... yes
checking whether to link to libpam... no, dynamically open it
checking whether to link to libcrypt... yes
checking for crypt in -lcrypt... yes
checking whether we are using the GNU C++ compiler... (cached) yes
checking whether g++ accepts -g... (cached) yes
checking the GNU C++ compiler version... checked (g++ 4.2.3)
checking for g++ include path... /usr/lib/gcc/i686-pc-linux-gnu/4.2.3/../../../../include/c++/4.2.3
checking exception type... dwarf2
checking what the default STL should be... stlport
checking for STL providing headers... using internal stlport.
checking which memory allocator to use... internal
checking whether to add custom build version... no
checking whether to build with Java support... yes
checking for java... /opt/java/bin/java
checking the installed JDK... checked (JDK 1.6.0_05)
checking for javac... /opt/java/bin/javac
checking for javadoc... /opt/java/bin/javadoc
checking for jawt lib name... -ljawt
checking whether to enable gcj aot compilation... no
checking for dmake... no
dmake will be built on ./bootstrap
checking whether to enable EPM for packing... yes
checking for epm... no
EPM will be built.
checking which package format to use... rpm
checking for rpm... configure: error: not found

Edit: Site link added

Last edited by Paingiver (2008-04-04 14:06:00)

bgc1954 · 2008-04-04 15:13:08

My guess would be that you downloaded an rpm source when you need a plain source tarball. That would cause it to build you an rpm package which doesn't help you in arch. Just curious...why compiling openoffice?

Paingiver · 2008-04-04 15:34:53

Thanks for the reply.I will check the tarballs. And the compile reason is:
1- The machine is P3 600 Mhz, 320 MB RAM. I want openoffice.org to be faster on this old computer.
2- Curiosity and adventure

bgc1954 · 2008-04-04 16:01:22

1) Just my opinion, but I don't think you'll gain much, if any, speed improvement over the arch openoffice pkg. and on that machine it's going to take forever to compile openoffice.

2) If that's the case it's a plenty good reason.

chicha · 2008-04-04 16:08:04

Well 320 MB might be a little too short to compile OpenOffice.
Also you need a lot of disk space where gcc writes its temporary files (/tmp by default I suppose), at least 1 GO, and you need several Go of free space in the partition where you compile.

I failed compiling Openoffice on a Gentoo system with 512Mo on a P3 733MHz for such problems ...
Also be prepared to wait for more than a day for a full compilation

And last but not least : do not expect much from compilation optimization. As an ex Gentoo user I can testify
If there was some magic optimization options be sure every body would be using them !

Also, I am just curious, why don't you use Openoffice 's PKGBUILD and makepkg with your custom CFLAGS ? Or maybe you are not targeting an Arch system ?

Have fun anyway : this is the bigest application I have ever compiled on a Desktop distro (and never succeeded )

Arch Linux

#1 2008-04-04 14:04:40

OpenOffice compiling problem

#2 2008-04-04 15:13:08

Re: OpenOffice compiling problem

#3 2008-04-04 15:34:53

Re: OpenOffice compiling problem

#4 2008-04-04 16:01:22

Re: OpenOffice compiling problem

#5 2008-04-04 16:08:04

Re: OpenOffice compiling problem

Board footer