Re: [greenstone-devel] Error encountered in configure - config.cache

From John R. McPherson
DateMon, 22 Nov 2004 10:33:05 +1300
Subject Re: [greenstone-devel] Error encountered in configure - config.cache
In-Reply-To (5-2-0-9-2-20041119150229-02e5cb70-psulias-psu-edu)
On Sat, 2004-11-20 at 09:18, Kurt Baker wrote:
> Hello Greenstone developers:
>
> I am trying to install Greenstone from the source on Sun
> Solaris. During the configure, I get an error at line 188 in the file
> config.cache. It seems to be a syntax error in the sed command contained
> within the line. I am not proficient with sed nor do I understand the
> developers intent.
> Below is the line in question. Any help will be appreciated.
>
> test "${lt_cv_global_symbol_to_c_name_address+set}" = set ||
> lt_cv_global_symbol
> _to_c_name_address=$'sed -n -e 's/^: \([^ ]*\) $/ {\"\1\", (lt_ptr)
> 0},/p
> ' -e 's/^[BCDEGRST] \([^ ]*\) \([^ ]*\)$/ {"\2", (lt_ptr) \&\2},/p''
>
> Thanks,
> Kurt Baker

Hi,
that is a bit ugly... rest assured that those lines are not from a
greenstone developer, but automatically generated by the configure
script. The problem (as far as I can see, at least) is that you can't
escape a ' char inside '...' quotes, so '...'....' shouldn't work
on proper bourne shell.

I have no idea why the configure script is making bad shell code since
it is supposedly tested to be portable - I assume it is/was a bug
in a particular version of autoconf/autotools.

Perhaps you could try downloading a newer version of the autotools
package, and then running 'autoconf' in the greenstone directory to
generate a new 'configure' script from our configure.in, and see if
that fixes the problem - if so, let us know and we'll try to get it
fixed for future releases.

John McPherson