Thanks for everybody's help, I got it working now. An observation:
The steps Lamar described really created a binary RPM, however
the pg_encoding utility isn't included (it was built though). Similarly
'createdb -E LATIN2 xx' from README.mb doesn't work, while
create database with encoding = 'latin2' works OK.
- Robert
PS If anybody's is in urgent need, I can put those rpms online before
Lamar builts the new version with multibyte support enabled - just let
me know you're interested.
Lamar Owen wrote:
> Robert wrote:
> >
> > I've upgraded to 6.5.3 from RPM but 'set client_encoding' still says
> > 'unknow variable'. How can I know whether RPM was compiled
> > with --enable-locale and --with-mb=LATIN2? And if it wasn't,
> > could I humbly suggest it for next version?
>
> The default 6.5.3-2 RPM's are compiled with --enable-locale, but not
> with --with-mb=LATIN2.
>
> (NOTE: The following procedure tells how to rebuild the RPM set. Before
> doing so, make sure you have a full development system -- C and C++
> compilers, Tcl/Tk (and by extension X11), python-devel, perl, and the
> latest rpm (rpm-3.0.2 or 3.0.3).)
> ...
