XML::Parser problem on Solaris 9 (was: Re: lr_config aborts with local installation on Solaris 9)

Tue Jul 29 23:42:57 CEST 2003

Hi,

On Tue, Jul 29, 2003 at 04:13:20PM +0200, Robert_G_Kennington at notes.tcs.treas.gov wrote:
> 
> Since system installation failed for me (see below), despite my grit and
> determination, I opted for local installation and lire compiled without a
> hitch.  In the long run, I'd like to be able to complete a system
> installation.   If I succeed, the outcome of this will be very detailed
> Solaris 9 installation instructions I'd be glad to share.

That'd be nice :)

> In the mean time, lr_config aborts.  Here's what happened.
> 
> isbld2br>pwd
> /rkenning
> 
> isbld2br>env
> _=/usr/bin/env
> HZ=100
> LC_MONETARY=en_US.ISO8859-15
> LC_TIME=en_US.ISO8859-15
> PATH=/usr/local/bin:/etc:/usr/ccs/bin:/usr/bin:/rkenning/lire/bin:.
> EDITOR=vi
> LOGNAME=rkenning
> MAIL=/var/mail/rkenning
> PS1=isbld2br>
> LC_MESSAGES=C
> LC_CTYPE=en_US.ISO8859-15
> SHELL=/bin/ksh
> HOME=/rkenning
> LC_COLLATE=en_US.ISO8859-15
> LC_NUMERIC=en_US.ISO8859-15
> TERM=xterm
> PWD=/rkenning
> TZ=US/Eastern
> 
> isbld2br>lr_config
> Can't locate XML/Parser.pm in at INC (@INC contains:
> /rkenning/lire/share/perl5 /usr/perl5/5.6.1/lib/sun4-solaris-64int
> /usr/perl5/5.6.1/lib /usr/perl5/site_perl/5.6.1/sun4-solaris-64int
> /usr/perl5/site_perl/5.6.1 /usr/perl5/site_perl
> /usr/perl5/vendor_perl/5.6.1/sun4-solaris-64int
> /usr/perl5/vendor_perl/5.6.1 /usr/perl5/vendor_perl .) at
> /rkenning/lire/share/perl5/Lire/DlfSchema.pm line 7.
> BEGIN failed--compilation aborted at
> /rkenning/lire/share/perl5/Lire/DlfSchema.pm line 7.
> Compilation failed in require at
> /rkenning/lire/share/perl5/Lire/OldDlfAdapter.pm line 9.
> BEGIN failed--compilation aborted at
> /rkenning/lire/share/perl5/Lire/OldDlfAdapter.pm line 9.
> Compilation failed in require at
> /rkenning/lire/share/perl5/Lire/DlfConverterManager.pm line 8.
> BEGIN failed--compilation aborted at
> /rkenning/lire/share/perl5/Lire/DlfConverterManager.pm line 8.
> Compilation failed in require at
> /rkenning/lire/share/perl5/Lire/Config/Spec.pm line 582.
> BEGIN failed--compilation aborted at
> /rkenning/lire/share/perl5/Lire/Config/Spec.pm line 582.
> Compilation failed in require at
> /rkenning/lire/share/perl5/Lire/Config/Parser.pm line 7.
> BEGIN failed--compilation aborted at
> /rkenning/lire/share/perl5/Lire/Config/Parser.pm line 7.
> Compilation failed in require at /rkenning/lire/share/perl5/Lire/Config.pm
> line 235.
> BEGIN failed--compilation aborted at
> /rkenning/lire/share/perl5/Lire/Config.pm line 235.
> Compilation failed in require at /rkenning/lire/bin/lr_config line 9.
> BEGIN failed--compilation aborted at /rkenning/lire/bin/lr_config line 9.
> 
> isbld2br>

This is lire-full-1.3.tar.gz on Solaris 9, I suppose?

I just did, on my Debian GNU/Linux box:

 joostvb at nagy:/usr.../local/src/lire% wget \
  http://download.logreport.org/pub/lire-full-1.3.tar.gz
 joostvb at nagy:/usr.../local/src/lire% tar zxf \
  lire-full-1.3.tar.gz
 joostvb at nagy:/usr.../local/src/lire% cd lire-1.3
 joostvb at nagy:/usr.../local/src/lire/lire-1.3% ./configure \
  --prefix=$HOME/local
 joostvb at nagy:/usr.../local/src/lire/lire-1.3% make
 joostvb at nagy:/usr.../local/src/lire/lire-1.3% make install

joostvb at nagy:~% export PATH=$HOME/local/bin:$PATH
joostvb at nagy:~% lr_config

"Lire Configurator                    Edit a file
   a) Create a new file
   0) Exit

Select a file to edit:                          "

My ~/local/bin/lr_config has, on it's 3th non-white line,

 use lib '/home/joostvb/local/share/perl5';

Does your lr_config have a similar statement?

Do you have XML::Parser installed on your system?  You can get this Perl
module from CPAN.  It is listed in the "Minimum Requirements" in the
"Installing Lire" chapter in the Lire User Manual.  If you didn't have
this installed on your system before installing Lire, the Lire
installation should've found out about this, and should've installed
XML::Parser along with Lire (it is shipped with lire-full, in extras/ .)

It might have happened that something went wrong while doing this.  It'd
be useful if you could sent us the output from ./configure and from your
make call .  Or, maybe, if you could grep for XML_PARSER in
config.status, in the top-level of your Lire build tree:

 joostvb at nagy:/usr.../local/src/lire/lire-1.3% grep XML_PARSER \
  config.status
 s%@INSTALL_XML_PARSER@%no%g
 s%@BUILD_XML_PARSER_TRUE@%#%g
 s%@BUILD_XML_PARSER_FALSE@%%g

.  It could be compilation of XML::Parser failed.  We'd need more output
for this though.

> Date: 7/23/2003
> From: Bob K (Robert.G.Kennington at notes.tcs.treas.gov
> To: questions at logreport.org
> Subj: Building Lire on Solaris 9 as root: make aborting after cc -c
> -I/rkenning/lire-1.3/extras/expat/lib
> 
> I'm attempting to compile and install lire-full-1.3.tar and can't get past
> the following despite installing GNU Solaris freeware (sunfreeware.com)
> autoconf-2.57, automake-1.7.2, gcc-3.3, make-3.80:

You don't need autoconf or automake to install Lire.  All requirements
are listed in the file INSTALL.

> # uname -a
> SunOS isbld2br 5.9 Generic_112233-04 sun4u sparc SUNW,Sun-Blade-100
> 
> # make
> ...
> cp Expat.pm ../blib/lib/XML/Parser/Expat.pm
> /usr/bin/perl -I/usr/perl5/5.6.1/lib/sun4-solaris-64int
> -I/usr/perl5/5.6.1/lib /usr/perl5/5.6.1/lib/ExtUtils/xsubpp -noprototypes
> -typemap /usr/perl5/5.6.1/lib/ExtUtils/typemap -typemap typemap Expat.xs >
> Expat.xsc && mv Expat.xsc Expat.c
> cc -c -I/rkenning/lire-1.3/extras/expat/lib -D_LARGEFILE_SOURCE
> -D_FILE_OFFSET_BITS=64 -xO3 -xdepend   -DVERSION=\"2.31\" -DXS_VERSION
> =\"2.31\" -KPIC -I/usr/perl5/5.6.1/lib/sun4-solaris-64int/CORE  Expat.c
> make[4]: cc: Command not found
> make[4]: *** [Expat.o] Error 127
> make[4]: Leaving directory `/rkenning/lire-1.3/extras/XML-Parser/Expat'
> make[3]: *** [subdirs] Error 2
> make[3]: Leaving directory `/rkenning/lire-1.3/extras/XML-Parser'
> make[2]: *** [stamp-xml-parser] Error 2
> make[2]: Leaving directory `/rkenning/lire-1.3/extras'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/rkenning/lire-1.3/extras'
> make: *** [all-recursive] Error 1
> #

Doing

 CC=gcc make

might help.  (Although this shouldn't be needed.)

> By the way, I initially headed advice about not using configure and make as
> root, but ran into other problem 'cp: cannot create
> /usr/local/lib/#inst.25001#: Permission denied' and make aborted.  My
> account, 'rkenning', has only 'staff' priviledges.  Is that enough?

It depends :)

Typically, you need root access only when running

 make install

.

> Do I need cc?  I thought gcc compiles c code.

Indeed, gcc is fine.

> My gut/intuition tells me
> after reading all somewhat related messages at logreport.org indicate that
> I don't have GNU setup properly on Solaris 9?
> 
> Also, during './configure', it indicates certain things are missing, such
> as automake, which I installed.  Do I need an earlier version of automake?
> 
> # ./configure
> loading cache ./config.cache
> checking for a BSD compatible install... ./install-sh -c
> checking whether build environment is sane... yes
> checking whether make sets ${MAKE}... (cached) no
> checking for working aclocal-1.4... missing
> checking for working autoconf... found
> checking for working automake-1.4... missing

The fact automake-1.4 is missing (or not found) is no problem.

> checking for working autoheader... found
> checking for working makeinfo... missing
> checking if building from CVS... no
> checking if I should ignore builing from CVS requirements... no
> checking for mawk... (cached) nawk
> checking for a BSD compatible install... ./install-sh -c
> checking whether ln -s works... (cached) yes
> checking whether make sets ${MAKE}... (cached) no
> checking for perl... (cached) yes
> checking for perl... (cached) /usr/bin/perl
> checking for pod2man... (cached) yes
> checking for sendmail... (cached) yes
> checking for sendmail... (cached) /usr/lib/sendmail
> checking for logger... (cached) yes
> checking for logger... (cached) /usr/bin/logger
> checking for tar... (cached) /usr/bin/tar
> checking for gzip... (cached) /usr/bin/gzip
> checking for zip... (cached) /usr/bin/zip
> checking for tai64nlocal... (cached) tai64nlocal
> checking for ploticus... no
> checking for pl... no
> checking for gs... (cached) no
> checking for XML::Parser... no (will install included version)

Hm, this looks good: Lire plans to install the XML::Parser shipped with
the tarball.

> checking for GD::Graph... no (you can install it later)
> checking for SpreadSheet::WriteExcel... no (you can install it later)
> checking for MIME::Entity... no (you can install it later)
> checking for Time::Timezone... no (will install included version)
> checking for jade... no
> checking for openjade... no
> checking for pdfjadetex... (cached) no
> checking for pdfxmltex... (cached) no
> checking for xsltproc... (cached) no
> checking for xmlcatalog... (cached) /usr/bin/xmlcatalog
> checking default xslt processor... none
> checking for lynx... (cached) no
> checking for SGML/XML trees...  /usr/lib/sgml
> checking for DocBook XML DTD... no
> checking for DocBook DSSSL stylesheets... no
> checking for DocBook XSL stylesheets... no
> checking for dia... (cached) no
> checking for epsffit... (cached) no
> checking for convert... (cached) no
> checking for epstopdf... (cached) no
> checking for xmllint... (cached) yes
> checking for xmllint... (cached) /usr/bin/xmllint
> checking xmllint version >= 2.4.19... no (20412)
> configure: warning: xmllint from libxml 2.4.19 is advised for building from
> CVS
> creating ./config.status
> ^C
> #

This looks fine.

> Finally, using 'MAKE=gmake ./configure' and then make, as recommended in
> 'building Lire from CVS on Solaris 8 (was: Re: Problem: make: Fatal error:
> Don't know how to make target `all-redirect')' does not appear to work
> either.

You are not building from CVS, this post is not relevant for your case.

> It aborts make earlier as follows:
> 
> # make
> Making all in all
> /bin/sh: gmake: not found
> make: *** [all-recursive] Error 1
> #

Vanilla Solaris make should do just fine.

> I guess my next fallback is to use common, however, I'd like to learn how
> to work compile Lire in order to learn more about it's architecture.  We
> lack a reporting capability for Directory LDAP logs

Which LDAP product, from which vendor, are you using?

> and I look forward to
> plans you all have for this.  Anything I can do to support this effort,
> just let me know.

HTH, Bye,

Joost

-- 
.    .                                        http://logreport.com/
| '.|                        /^LogReport$/
| Lire                                        http://logreport.org/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.logreport.org/pipermail/questions/attachments/20030729/0345c6a1/attachment.bin 