Обсуждение: --with-mb=SQL_ASCII for 6.5.3 RPMs.
Ok, got a minor problem here in RPM building. It was requested that when I build locale-enabled RPM's, that I also enable multibyte support. The suggestion was then made to use --with-mb=SQL_ASCII -- and the README.mb for 6.5.3 supports that. HOWEVER, --with-mb=SQL_ASCII throws a configure error -- SQL_ASCII is not valid for this switch, or something like that. So, my question is: unless someone here who is an autoconf wizard suggests otherwise, I'm going to patch configure to allow the SQL_ASCII switch (I _know_ that the real fix lies in patching configure.in -- I'm just wanting to get the RPM out the door without having to learn how to run autoconf first -- unless that would be preferable). Are there any other things I need to patch other than the list of allowed encodings in order to use --with-mb=SQL_ASCII?? I'd love to get the 6.5.3-3 RPMs out the door today if possible. This RPM set includes a few bugfixes as well as the headers necessary to build SPI modules. TIA -- Lamar Owen WGCR Internet Radio 1 Peter 4:11
Lamar Owen <lamar.owen@wgcr.org> writes:
> (I _know_ that the real fix lies in patching configure.in -- I'm
> just wanting to get the RPM out the door without having to learn how to
> run autoconf first -- unless that would be preferable).
1. Install autoconf (get it from any GNU archive). Be sure you have
version 2.13 to ensure you get the same results as the rest of us.
Install is no harder than "configure; make; make install". You do need
to have GNU m4, but if you are on a Linux box you probably already do.
Try "m4 --version" to check.
2. type "autoconf" in the pgsql/src directory.
Can't get much easier. Changing configure.in is a LOT easier than
patching the output, IMHO...
regards, tom lane
Tom Lane wrote: > > Lamar Owen <lamar.owen@wgcr.org> writes: > > (I _know_ that the real fix lies in patching configure.in -- I'm > > just wanting to get the RPM out the door without having to learn how to > > run autoconf first -- unless that would be preferable). > > 1. Install autoconf (get it from any GNU archive). Be sure you have > version 2.13 to ensure you get the same results as the rest of us. > Install is no harder than "configure; make; make install". You do need > to have GNU m4, but if you are on a Linux box you probably already do. > Try "m4 --version" to check. > > 2. type "autoconf" in the pgsql/src directory. > > Can't get much easier. Changing configure.in is a LOT easier than > patching the output, IMHO... Well, I actually have to do both, in the RPM scheme of things. I did as you suggested (RedHat 6.1 ships autoconf 2.13 -- installing is a simple 'rpm -i autoconf-2.13-5.i386.rpm'). Popped configure.in into vi, made the change, ran autoconf, generated the resulting patchset (the RPM philosophy is that a source RPM contains everything necessary to rebuild all the binary RPMs -- using pristine sources plus whatever scripts, patches, and extra programs are necessary to make it build binaries that will run. The control file that determines how to do all of this is called a 'spec' file -- the postgresql spec file is one of the more complex ones due to the large differences in file locations vis-a-vis the pristine source install.), built a test RPM set, and am editing the README now to reflect the successful changes. I should release in a couple of hours, once I have all four sets of binaries built (RH 6.1, RH 6.1 non-locale, RH5.2, RH 5.2 non-locale). -- Lamar Owen WGCR Internet Radio 1 Peter 4:11