Обсуждение: Postgres 8.3.1 configure fails on Solaris 10 using gcc 3.4.3 and building for 64 bit
Postgres 8.3.1 configure fails on Solaris 10 using gcc 3.4.3 and building for 64 bit
От
Harry Broomhall
Дата:
I've been using Postgres for years on FreeBSD boxen with very little problems. My company have now given me a big Sun box with 4 AMD64 processors to told me to port my system to it. The problem is that I am not fluent in Solaris! I am adding CFLAGS='-m64' to the configure line, but gcc and ld seem strangely reluctant to use 64bit components, with the configure script failing to run the test compile with the error: wrong ELF class: ELFCLASS32 I've used 'crle' to set the paths, but it appears that only controls the loading, not the linking. So I would like to know just what parameters to hand to configure to make this work. I had a look on the 'buildfarm' page, and saw that emperor_moth was nominaly the same type of build. But I can't see there where a 64 bit build is being requested. I'm probably missing somethig simple! Regards, Harry.
Re: Postgres 8.3.1 configure fails on Solaris 10 using gcc 3.4.3 and building for 64 bit
От
Zdenek Kotala
Дата:
You can download 8.3.1 64bit version for Solaris from community web site http://www.postgresql.org/ftp/binary/v8.3.1/solaris/i386/ Or is there something missing what you need? I also put Bjorn on CC. He builded this packages, but we use Sun Studio compiler. You can also look how 8.2 is builded in opensolaris: http://src.opensolaris.org/source/xref/sfw/usr/src/cmd/postgres/postgresql-8.2/ Zdenek Harry Broomhall napsal(a): > I've been using Postgres for years on FreeBSD boxen with very > little problems. > > My company have now given me a big Sun box with 4 AMD64 processors > to told me to port my system to it. The problem is that I am not > fluent in Solaris! > > I am adding CFLAGS='-m64' to the configure line, but gcc and ld > seem strangely reluctant to use 64bit components, with the configure > script failing to run the test compile with the error: > > wrong ELF class: ELFCLASS32 > > I've used 'crle' to set the paths, but it appears that only controls > the loading, not the linking. > > So I would like to know just what parameters to hand to configure > to make this work. > > I had a look on the 'buildfarm' page, and saw that emperor_moth was > nominaly the same type of build. But I can't see there where a 64 bit > build is being requested. > > I'm probably missing somethig simple! > > Regards, > Harry.
Re: Postgres 8.3.1 configure fails on Solaris 10 using gcc 3.4.3 and building for 64 bit
От
Harry Broomhall
Дата:
Thank you for your rapid reply. On Mon, 24 Mar 2008 20:19:28 +0100, you wrote: >You can download 8.3.1 64bit version for Solaris from community web site >http://www.postgresql.org/ftp/binary/v8.3.1/solaris/i386/ I had seen this and downloaded it. The problem is that it is for Solaris Express, not the 'standard' Solaris 10. This fails because it expects a newer version of ssl than supplied. Forgive me if I have used the wrong terms, but it is becoming clear to me that Solaris 10 exists in two versions. The 'commercial' versions, which is what we have to use, and has a slow update cycle (we are on 11/06) and Express, which seems much more up-to-date, but seems not to be available commercialy. > >Or is there something missing what you need? I also put Bjorn on CC. He builded >this packages, but we use Sun Studio compiler. > >You can also look how 8.2 is builded in opensolaris: > >http://src.opensolaris.org/source/xref/sfw/usr/src/cmd/postgres/postgresql-8.2/ > Many thanks for the pointer. I'll take a look at it. It would appear that I haven't been supplied with the Studio compiler. Regards, Harry.
Re: Postgres 8.3.1 configure fails on Solaris 10 using gcc 3.4.3 and building for 64 bit
От
Zdenek Kotala
Дата:
Harry Broomhall napsal(a): > Thank you for your rapid reply. > > On Mon, 24 Mar 2008 20:19:28 +0100, you wrote: > >> You can download 8.3.1 64bit version for Solaris from community web site >> http://www.postgresql.org/ftp/binary/v8.3.1/solaris/i386/ > > I had seen this and downloaded it. The problem is that it is for > Solaris Express, not the 'standard' Solaris 10. This fails because it > expects a newer version of ssl than supplied. Yes, it is true. We are now working on build environment for S10U4 and newer and I hope we will release 8.3.1 for S10U4 soon. > Forgive me if I have used the wrong terms, but it is becoming clear > to me that Solaris 10 exists in two versions. The 'commercial' > versions, which is what we have to use, and has a slow update cycle > (we are on 11/06) and Express, which seems much more up-to-date, but > seems not to be available commercialy. Yes, Solaris 10 is only supported version of solaris, you can buy limited support also for OpenSolaris Developer edition but it is more for application developers. If you are on 11/06 it is probably S10U3 it is not good version for PostgreSQL anyway. We require S10U4 or newer, because it contains krb5, new version of dtrace (important for building) and updated libXML. You can apply patches on your system to update dtrace and libXML, but krb5 is a new feature you can try install krb5 packages from S10U4 but I'm not sure if it works. Zdenek
Re: Postgres 8.3.1 configure fails on Solaris 10 using gcc 3.4.3 and building for 64 bit
От
Harry Broomhall
Дата:
On Tue, 25 Mar 2008 08:16:40 +0100, you wrote: >Yes, Solaris 10 is only supported version of solaris, you can buy limited >support also for OpenSolaris Developer edition but it is more for application >developers. If you are on 11/06 it is probably S10U3 it is not good version for >PostgreSQL anyway. We require S10U4 or newer, because it contains krb5, new >version of dtrace (important for building) and updated libXML. You can apply >patches on your system to update dtrace and libXML, but krb5 is a new feature >you can try install krb5 packages from S10U4 but I'm not sure if it works. Many thanks for the information. Using this, along with info I have read elsewhere, I have persuaded my company to reload the box with U4. It appears that when the box was originaly configured U4 hadn't passed our tests, which is why U3 was there. Once I get the box back I'll try again! Regards, Harry.