Mail Archives: djgpp/1999/04/20/04:00:28
On Sun, 18 Apr 1999, Daniel Barker wrote:
> Here is what I have changed the relevant line of "pc\local.djgpp" to:
>
> #define LANGUAGES "{british,MASTERDICTS=britmed,HASHFILES=britmed.hash}
> {american}"
I thing this is wrong. I suggest to try this:
#define LANGUAGES "{british,MASTERDICTS=british.med,HASHFILES=britmed.hash}
{american,MASTERDICTS=american.med,HASHFILES=amermed.hash}
I just tried to build Ispell on Windows 95 with this setting, and it
worked for me.
You need to specify the language completely and not rely on defaults,
like the "{american}" case does, because I'm not sure the build
process will support that. To avoid problems with file names like
`american.med+' on MS-DOS, I changed the file names generated by
languages/Makefile (see the `pc/cfglang.sed' script for the gory
details), and after all these years I don't remember if omitting the
explicit names for MASTERDICTS and HASHFILES will pick up the tweaked
names. Better be safe than sorry ;-).
You also need to change MASTERHASH and DEFHASH, as the file
`local.djgpp' explains in the comments. I suggest to use these:
#define MASTERHASH "britmed.hash"
#define DEFHASH "english.hash"
> Here is the first problem:
>
> iwhich: sed: command not found
> iwhich: false: command not found
> iwhich: sed: command not found
> iwhich: false: command not found
>
> ("sed" and "false" are actually installed.)
This is a bug in the build process that I failed to handle. To work
around it, create an X:\BIN directory (where X: is the drive where you
build Ispell), and copy `sed.exe' and `false' there. Then it should
work.
> Then, almost immediately, the build fails as follows:
>
> make.exe[3]: Entering directory
> `c:/Local/djgpp/gnu/ispell-3.120/languages/british'
> make.exe[3]: *** No rule to make target `britmed'. Stop.
I believe this is because you used incorrect LANGUAGES definition, see
above.
- Raw text -