|Date||Mon, 03 Feb 2003 23:27:28 +1300|
|Subject||Re: Greenstone Install problem|
|John R. McPherson wrote:
> On Mon, Feb 03, 2003 at 08:54:38PM +1300, Stefan Boddie wrote:
>>Problem number 2: As discussed between Gordon and John McP on this list
>>a week or two ago there's a problem compiling the Greenstone source with
>>gcc-3.2. According to the SuSE website SuSE linux 8.1 includes gcc-3.2
>>so you'll have this problem if you go ahead and try to compile from
>>source. To work around this problem you should do the following:
>>If possible (and if they're still reading this :-) could John and/or
>>Gordon let me know what they think the best solution to this bug is? We
>>need to get a fix committed to CVS soon as I'm just in the process of
>>creating the gsdl-2.39 release.
> I added a test to configure.in that defines ENABLE_NLS if there is
> a gettext() function in the c library. I don't think we actually even
> need any of the gettext stuff in the source code as we don't use
> the multi-lingual stuff, but mg uses it in a few places. If ENABLE_NLS
> is set then the sysfuncs.h doesn't try to define its own textdomain().
> This was committed to cvs last week (or maybe the week before).
> I tested this on linux slackware 8 and debian woody 3. If you remind me
> I'll checkout and test compilation on OS X and maybe a solaris machine
> if I can find one on sourceforge's compile farm...
Sorry, should have checked CVS first. Thanks for that. It configures and