Hrm, you're right of course, this is a classic PEBKAC case on my part.
It seems that the sfw 2.14 package wasn't actually installed on the
dev box I'm working on atm, so I've been compiling against whatever
old glib2 Sol10 is shipped with. I'd been assuming that the sfw
package was in place, so I was taking the configure fails to indicate
that 2.14 < 2.6 - brain dropping in a decimal point that wasn't there
or something. Clearly not enough coffee this morning. ;O
Might want to update that Enchant page, in any case - you do require
2.6, not 2.0. I do wonder about whether using g_fopen a few times is
worth being broken on stock Solaris10, but I'm cool with it now that I
am, er, unconfused - I can no doubt easily install the sfw package and
get the latest enchant built now. Thanks!
Jeff
Might be worthwhile to update the text, anyways.
On Tue, May 20, 2008 at 12:12 PM, Hubert Figuiere <hfiguiere@teaser.fr> wrote:
>
>
> On Tue, 2008-05-20 at 12:02 -0400, J Dietrich wrote:
>> ... but many months before that commit (November 16, '07), in r22309 :
>> "since we now use g_fopen, bump glib version requirement to >= 2.6" -
>> and it does alter configure.in to require 2.6. This is in response to
>> r22307 using g_fopen in pwl.c and enchant.c.
>>
>> I'm on Solaris 10 (sparc), with the usual slightly bastardized
>> GNU/sunfreeware toolchain required to actually get things done on that
>> platform, but can't easily use 2.6. 2.14.1 is the latest pre-packaged
>> version @ sunfreeware for sol10sparc, and I'm pretty hesitant to
>> compile + install 2.6+ by hand just for enchant - particularly given
>> that I can successfully compile rather more involved software, like
>> the latest mono, without it.
>
> I don't see your issue. 2.6 < 2.14.1 If you have 2.14.1 there is no
> problem.
>
>
>
> Hub
>
>
Received on Tue May 20 21:19:18 2008
This archive was generated by hypermail 2.1.8 : Tue May 20 2008 - 21:19:18 CEST