Re: [aspell-devel] cygwin no-go with latest

[Kevin Atkinson]

On Sun, 25 Aug 2002, Melvin Hadasht wrote:

> Hi Jan,
> 
> on Sun, 25 Aug 2002 10:27:27 -0400
> Jan Wells <address@hidden> wrote:
> 
>  > Perhaps other messages are available on the subject, but I cannot locate
>  > such as those.  So, this post/question.
>  > 
>  > Can apsell really be compiled under cygwin?  I've tried without
>  > success.  Sadly, I know neither C nor C++ and somedays am pretty much
>  > all thumbs anyway.  Odds of getting aspell going on my machine under
>  > cygwin may, therefor, be remote.  Still, if there's an easy fix, that
>  > would be wonderful.  Last few lines captured from the console window
>  > are as follows:

> I had once such error on linux with gcc-3.2 (or was it 3.1.1) + optimization
> -O3. It compiled ok with -O2 (or by adding -fno-inline-functions). 

Yes, avoiding -O3 may fix the problem. 

Please also note the following:

(From the manual of the upcoming 0.50.1 release)

Due to limited time and my general dislike for Microsoft Windows,
Win32 is not an officially supported platform for Aspell. However,
with a little effort, it should be possible for someone with
experience with the Cgiwin development environment to create an Aspell
binary and library (dll) using gcc. The library in theory should be
able to be used by any Win32 compiler if it is compiled right, but
this theory has never been tested.

If you have experience with using Cgiwin or a Unix like environment
and are willing to maintain an Aspell binary and/or library I would be
willing to work with you to get Aspell to compile. If you are
seriously interested please post to address@hidden after you
have given it an initial try. However, if, after reading this section,
you do not know how to start then you most likely do not have the
necessary experience to be able to get Aspell to compile. Please do
not bother me with questions such as "I would like to use Aspell on
Win32 but I have no idea what to do.", as I am not willing to teach
you the basics of working with a Unix like environment.

Aspell requires Gcc 2.95 (or better) and the Cgiwin development
environment in order to compile on Win32. Both the Cgiwin or the Mingw
version of Gcc should work. The Mingw version of Aspell will have
slightly less functionality, but none of which is noticeable to the
end user. Microsoft Visual C++, however, will not work as the compiler
is far to buggy as far as C++ compliance goes. You are more than
welcome to try but be warned that others in the past have tried and
given up.

In order to get the nice full screen interface with Mingw when spell
checking files a curses implementation that does not require Cygwin is
required. The PDCurses ([http://www.lightlink.com/hessling/PDCurses/])
implementation is known to work, other implementations may work
however they have not been tested. See the previous section for
information on specifying the location of the curses library and
include file.

If Aspell is compiled with --enable-win32-relocatable and the bindir
is set to the same value as prefix (ie not <<prefix>>/bin) then the
Aspell directory (what prefix is set to) can be relocated anywhere
provided that none of the data files are moved around within the
Aspell directory. Please not that this feature has not been tested
with GNU Aspell 0.50 so it may or may not work.

The default paths for Aspell are designed for a Unix system and not a
Win32 system so you might want to specify different ones when
compiling Aspell. Also if the HOME environmental variable is not set
Aspell will assume it is the current working directly. This may lead
to your personal word lists being saved in unpredictable locations. To
solve this either compile with --enable-win32-relocatable (see above)
or specify the complete path of the personal and replacement word
lists in aspell.conf. If Aspell is compiled with
--enable-win32-relocatable than the personal word lists are saved in
the prefix directory and the name is changed from ".aspell.<lang>.*"
to" <lang>.*".

-- 
http://kevin.atkinson.dhs.org