[ome-devel] OME install problems with fedora core 2

[Mark Roden]

Hi Ilya (et al),

Thanks for the tip, it worked.  It looks like the version of
GD that's installed from the OME repository is version 1.33,
not 2.16, which might account for the failure.

There was another small error (the script said I had XML 1.57
or later, when in fact I had perl-XML 1.56) that took a bit to
 track down, but that's also done.

Now I'm in territory where I am, to put it mildly, a bit
lost-- postgres failures.  I have installed postgres rpms, and
can run initdb, postmaster, createdb, and psql just fine, as
per chapter 14 of the postgres documentation.  The OME
installer ends with this error:
<error>
CREATION OF USER ome FAILED -- OUTPUT:
createuser: could not connect to database template1: FATAL: 
user "postgres" does not exist
</error>
When I go to adduser postgres, the system informs me that user
postgres already exists.  What should I do?

Also, until I ran 'initdb' by hand, the postgres step failed
with a different error, something like:
<error>
createdb: could not connect to database template1: could not
connect to server:
No such file or directory
        Is the server running locally and accepting
        connections on Unix domain socket "/tmp/.s.PGSQL.5432"?
</error>
Now, when I did the initdb step by hand, I was able to get
past this step.  Should I add initdb and suchlike to some
startup script?  If I should, what should I add, just to make
sure everything runs smoothly?

Thanks for the help,
Mark

---- Original message ----
>Date: Wed, 22 Sep 2004 16:14:16 -0400
>From: Ilya Goldberg <igg at nih.gov>  
>Subject: Re: [ome-devel] OME install problems with fedora
core 2  
>To: Mark Roden <mark at intelligent-imaging.com>
>Cc: ome-devel at lists.openmicroscopy.org.uk
>
>
>On Sep 22, 2004, at 3:02 PM, Mark Roden wrote:
>
>> Hi,
>>
>> I'm having problems installing OME version 2.2.1 on a
>> completely clean fedora core 2 installation.  I've managed to
>> quite a bit further installing the OME server package with
>> fedora, as opposed to a piecemeal Redhat 9 installation;
>> however, I still have the following problems:
>>
>> <begin OME install log>
>> Would you like to install GD from the repository ? [y/n]: y
>>    \_ Downloading
>> http://openmicroscopy.org/packages/perl/GD-1.33.tar.gz
[SUCCE SS].
>>    \_ Unpacking [SUCCESS].
>>    \_ Configuring NOTICE: This module requires libgd 1.8.3 or
>> higher (shared li brary version 4.X).
>> Please choose the features that match how libgd was built:
>> Build JPEG support? [y] y
>> Build FreeType support? [y] y
>> Build XPM support? [y] y
>> If you experience compile problems, please check the @INC,
>> @LIBPATH and @LIBS
>> arrays defined in Makefile.PL and manually adjust, if
necessary.
>> Writing Makefile for GD
>> [SUCCESS].
>>    \_ Compiling [FAILURE].
>> Errors executing task: Unable to compile module, see
>> PerlModuleTask.log for deta ils. at (eval 32) line 1
>>        main::run_tasks() called at install.pl line 249
>> # Looks like your test died before it could output anything.
>> </end OME install log>
>
>Installation output goes to installation log files which are in 
>/var/tmp/OME/install/
>This is also where any supplementary modules get downloaded and 
>installed from - this is where the Makefile in question lives.
>
>GD has unfortunately become a problem child.  Last I checked
(several 
>months ago), there was no perl RPM for GD.
>There is a package for Fedora called something like (this is
for a 
>64-bit OS):
>gd-2.0.21-2.x86_64.rpm
>You might as well get these too (I think that's all of them)
>gd-progs-2.0.21-2.x86_64.rpm
>gd-devel-2.0.21-2.x86_64.rpm
>download and install that using yum, red carpet or whatever (the 
>version number doesn't matter very much - use "the latest")
>Get the Perl bindings for it here:
>wget
http://search.cpan.org/CPAN/authors/id/L/LD/LDS/GD-2.16.tar.gz
>then:
>tar -zxvf GD-2.16.tar.gz; cd GD-2.16; perl Makefile.PL
>answer the questions (just hit return), then
>make
>make test
>(ignore any errors here)
>and finally:
>sudo make install
>(or su to become root then 'make install')
>
>Usually this works.  If it doesn't, let me know.  We should
probably 
>just turn this thing off because its only used by legacy code 
>presently.
>-Ilya
>
>