Обсуждение: Forcing a 32 bit build on a 64 bit system

Hi,
I am running RHEL5 on a 64 bit platform. We want to test with a 32 bit version of PostgreSQL. Can someone point me to the configure switches needed to force a 32 bit build?

Thanks,
Doug Knight
WSI Inc.
Andover, MA

Doug Knight <dknight@wsi.com> writes:
> I am running RHEL5 on a 64 bit platform. We want to test with a 32 bit
> version of PostgreSQL. Can someone point me to the configure switches
> needed to force a 32 bit build?

"setarch i386" will help.

            regards, tom lane

OK. I ran configure as:

setarch i386 ./configure

In the config.log both build and host now say i686-pc-linux-gnu. However, under "checking for C compiler version" I see "Target: x86_64-redhat-linux". Should I be concerned about this wrt building a pure 32 bit postgreSQL? Also, later in the log, there are references to Perl archlibexp and embedded Perl referencing the /usr/lib64 location. Should I be concerned about using the 64 bit perl libs? My goal is to create a pure 32 bit version for some testing we're doing. We ran into some issues with LISTEN/NOTIFY (will be a separate topic), and wanted to confirm or deny that the 64 bit version was the issue.

BTW, setarch i386 make built with no errors.

Thanks,
Doug

On Fri, 2007-08-31 at 10:46 -0400, Tom Lane wrote:

Doug Knight <dknight@wsi.com> writes:
> I am running RHEL5 on a 64 bit platform. We want to test with a 32 bit
> version of PostgreSQL. Can someone point me to the configure switches
> needed to force a 32 bit build?

"setarch i386" will help.

			regards, tom lane

Doug Knight <dknight@wsi.com> writes:
> In the config.log both build and host now say i686-pc-linux-gnu.
> However, under "checking for C compiler version" I see "Target:
> x86_64-redhat-linux". Should I be concerned about this wrt building a
> pure 32 bit postgreSQL? Also, later in the log, there are references to
> Perl archlibexp and embedded Perl referencing the /usr/lib64 location.

Hmm ... do you have a 32-bit perl installed?  I'm not sure it's really
possible to install both at once, actually, since there can be only one
/usr/bin/perl.  It might be that your best bet is to set up a 32-bit
buildroot using mock.  I just did that for the first time the other day
and it was a lot less painful than I expected ...

OTOH, if you don't actually need plperl for your test, it may not be
worth troubling with.  If you've got a 32-bit executable and it doesn't
crash when used, that should be good enough for experimental purposes.

            regards, tom lane