Skip to main content.
home | support | download

Back to List Archive

Re: Problems with command line parsing -- swish-e on Solaris 2.5.1

From: Bill Moseley <moseley(at)>
Date: Mon Sep 06 2004 - 16:11:18 GMT
On Mon, Sep 06, 2004 at 08:22:04AM -0700, Thomas R. Bruce wrote:
> Bill et al:
> I am attempting an upgrade from 2.3.5 (yeah, I know) under Solaris.


Since I don't know Solaris much I find it really frustrating.

Maybe it's just a matter of the way this system is setup, but
/configure && make runs fine but when trying to run swish I see: /data/_g/lii/swish-e-2.5.1-2004-08-30/src/.libs/swish-e: fatal: open failed: No such file or directory

Obviously, gcc was installed and the libraries placed in /usr/local,
but the dynamic linker doesn't know about /usr/local.

526) ~/swish-e-2.5.1-2004-08-30/tests %crle

Default configuration file (/var/ld/ld.config) not found
  Default Library Path (ELF):   /usr/lib  (system default)
  Trusted Directories (ELF):    /usr/lib/secure  (system default)

Is that normal setup?


Now, back to your question:

> Both the current 2.4.x stable release and the latest development
> snapshot have a similar problem -- swish-e insists on finding
> "empty" arguments on the command line.  For instance, running the
> perl makefile produces the following:
> Your SWISH-E version: 2.5.1 Creating index...'/usr/local/bin/swish-e
> -c t/test.conf -f t/index.swish-e -v 0'
> err: Couldn't open the configuration file '': No such file or
> directory .

That's weird.  I just built the daily (which is a few days old)
snapshot and had no problems like that on Solaris 5.8.

What happens if you try something simple like this?

550) ~ %echo '#comment' > config
551) ~ %swish-e -c config -i config -v0 -T indexed_words
    Adding:[1:swishdefault(1)]   'comment'   Pos:5  Stuct:0x9 ( BODY FILE )

Bill Moseley

Unsubscribe from or help with the swish-e list:

Help with Swish-e:
Received on Mon Sep 6 09:11:36 2004