Quoth David DeSimone:
> Don Blaheta <[EMAIL PROTECTED]> wrote:
> >
> > Ok, I've been having similar problems (I maintain the local copy of
> > mutt, but don't have root; I need to use a special program "cscp" to
> > copy files into the public hierarchy), so I configured with
> > "--prefix=./subdir".
>
> The problem you'll run into here is that Mutt gets built in a directory,
> then when it's moved to the installed directory by your 'cscp' program,
> it will continue looking for support files from the origina directory
> where you configured it.
Aha. Should've realised that. *d'oh*
> I think what you'll have to do is configure mutt with --prefix set to
> the actual path you will eventually install to. Then, you'll have to
> recreate the actions that 'make install' would have performed ('make -n
> install' would probably be helpful here), using your 'cscp' program.
Ok. So I configured it how I wanted it, then I made all the little
incantations that make install asked for, but I *still* can't get
foreign language support working (let's not even get started on
alternate charsets). Correct me if I'm wrong, but I should be able to
type
setenv LANG fr
./mutt
and have mutt give most/all messages to me in French, yes? I guess my
question just boils down to, is there a list somewhere of
* what files mutt needs
* where it needs them
* how it finds them <-- this seems to be the tricky one....
For example, I have installed all the .mo files in
/cs/share/mutt/locale/$lang/LC_MESSAGES/ ; and I recompiled the intl
code with -DLOCALEDIR="/cs/share/locale", and made sure that mutt was
linked with that version of the intl library... what more do I need to
do?
--
-=-Don [EMAIL PROTECTED]=-=-<http://www.cs.brown.edu/~dpb/>-=-
Warp 7 -- It's a law we can live with.
