I looked at config.log and found that I had entered the path incorrectly. 
After going thru the steps of configure, make, etc., I was able to install 
swish!  Thank you for the help. There seems to be one problem remaining, 
when I run swish.  I get an 'open failed', as listed below.

bash-2.05# swish-e
ld.so.1: swish-e: fatal: libgcc_s.so.1: open failed: No such file or 
directory
Killed
bash-2.05# /usr/local/bin/swish-e
ld.so.1: /usr/local/bin/swish-e: fatal: libgcc_s.so.1: open failed: No such 
file or directory
Killed

William E. Branson
Administrator, Systems Planning
Chicago Transit Authority
wbranson@transitchicago.com
312.681.4226
----- Original Message ----- 
From: "Bill Moseley" <moseley@hank.org>
To: "Multiple recipients of list" <swish-e@sunsite3.berkeley.edu>
Sent: Wednesday, March 16, 2005 9:52 AM
Subject: [SWISH-E] Re: Problem Installing swish-e 2.4.3


> (please reply to the list)
>
> On Wed, Mar 16, 2005 at 08:24:40AM -0600, William Branson wrote:
>> Thank you for your reply.  I added 'ar' to my path, and received a
>> different set of errors. (see below).   I also tried putting gnu make in
>> the path, with similar results.  The other posts show that my problem is
>> not unique, but I don't see a conclusive fix mentioned.
>>
>> Making install in expat
>> /bin/bash ../../libtool --mode=link gcc  -g -O2    -o libswexpat.la
>> xmltok.lo xmlrole.lo xmlparse.lo  -lm
>> false cru .libs/libswexpat.a .libs/xmltok.o .libs/xmlrole.o 
>> .libs/xmlparse.o
>  ^^^^^
>
> Sure looks like configure is not finding ar and replacing it with
> 'false'.  (I wonder why configure doesn't abort.)
>
> Look at config.log -- maybe something will show up.  Or look how AR
> is getting assigned in the actual configure script.
>
>
> -- 
> Bill Moseley
> moseley@hank.org
>
>