Thread: Compile on x86_64

Compile on x86_64

From
Ray Auge
Date:
Hello All,

Firstly, many thanks to all of the devs for an excellent tool. I use it
(an older version) almost daily at work (on i568 FC4 linux) and it
rocks.

I've just picked-up the latest release src rpm for FC4pgadmin3-1.4.1-1.src.rpm

Now I'm trying to rebuild it on my x86_64 box without success.

I've tried

rpmbuild --rebuild pgadmin3-1.4.1-1.src.rpm

I've tried installing the src rpm into my build tree and doing

rpmbuild -ba pgadmin3.spec

I'm fairly certain that I have the latest version of wxGTK(2) and all
the devel packages that are a available in the FC4 Extras repository.

Here is the build trace and error:

[user@localhost SPECS]$ rpmbuild -ba pgadmin3.spec
Executing(%prep): /bin/sh -e /home/user/rpm/tmp/rpm-tmp.85080
+ umask 022
+ cd /home/user/rpm/BUILD
+ LANG=C
+ export LANG
+ unset DISPLAY
+ cd /home/user/rpm/BUILD
+ rm -rf pgadmin3-1.4.1
+ /bin/gzip -dc /home/user/rpm/SOURCES/pgadmin3-1.4.1.tar.gz
+ tar -xf -
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ cd pgadmin3-1.4.1
++ /usr/bin/id -u
+ '[' 605 = 0 ']'
++ /usr/bin/id -u
+ '[' 605 = 0 ']'
+ /bin/chmod -Rf a+rX,u+w,g-w,o-w .
+ exit 0
Executing(%build): /bin/sh -e /home/user/rpm/tmp/rpm-tmp.96020
+ umask 022
+ cd /home/user/rpm/BUILD
+ cd pgadmin3-1.4.1
+ LANG=C
+ export LANG
+ unset DISPLAY
+ CFLAGS='-O2 -g -pipe -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -m64
-mtune=nocona'
+ export CFLAGS
+ CXXFLAGS='-O2 -g -pipe -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -m64
-mtune=nocona'
+ export CXXFLAGS
+ FFLAGS='-O2 -g -pipe -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -m64
-mtune=nocona'
+ export FFLAGS
++ find . -name config.guess -o -name config.sub
+ for i in '$(find . -name config.guess -o -name config.sub)'
++ basename ./config/config.guess
+ '[' -f /usr/lib/rpm/redhat/config.guess ']'
+ /bin/rm -f ./config/config.guess
++ basename ./config/config.guess
+ /bin/cp -fv /usr/lib/rpm/redhat/config.guess ./config/config.guess
`/usr/lib/rpm/redhat/config.guess' -> `./config/config.guess'
+ for i in '$(find . -name config.guess -o -name config.sub)'
++ basename ./config/config.sub
+ '[' -f /usr/lib/rpm/redhat/config.sub ']'
+ /bin/rm -f ./config/config.sub
++ basename ./config/config.sub
+ /bin/cp -fv /usr/lib/rpm/redhat/config.sub ./config/config.sub
`/usr/lib/rpm/redhat/config.sub' -> `./config/config.sub'
+ ./configure --build=x86_64-redhat-linux-gnu
--host=x86_64-redhat-linux-gnu --target=x86_64-redhat-linux-gnu
--program-prefix= --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin
--sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share
--includedir=/usr/include --libdir=/usr/lib64 --libexecdir=/usr/libexec
--localstatedir=/var --sharedstatedir=/usr/com --mandir=/usr/share/man
--infodir=/usr/share/info --enable-static --disable-debug
checking build system type... x86_64-redhat-linux-gnu
checking host system type... x86_64-redhat-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking how to create a ustar tar archive... gnutar
checking for x86_64-redhat-linux-gnu-gcc... no
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for x86_64-redhat-linux-gnu-g++... no
checking for x86_64-redhat-linux-gnu-c++... no
checking for x86_64-redhat-linux-gnu-gpp... no
checking for x86_64-redhat-linux-gnu-aCC... no
checking for x86_64-redhat-linux-gnu-CC... no
checking for x86_64-redhat-linux-gnu-cxx... no
checking for x86_64-redhat-linux-gnu-cc++... no
checking for x86_64-redhat-linux-gnu-cl... no
checking for x86_64-redhat-linux-gnu-FCC... no
checking for x86_64-redhat-linux-gnu-KCC... no
checking for x86_64-redhat-linux-gnu-RCC... no
checking for x86_64-redhat-linux-gnu-xlC_r... no
checking for x86_64-redhat-linux-gnu-xlC... no
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking how to run the C preprocessor... gcc -E
checking for egrep... grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking arpa/inet.h usability... yes
checking arpa/inet.h presence... yes
checking for arpa/inet.h... yes
checking netdb.h usability... yes
checking netdb.h presence... yes
checking for netdb.h... yes
checking netinet/in.h usability... yes
checking netinet/in.h presence... yes
checking for netinet/in.h... yes
checking for stdlib.h... (cached) yes
checking for stdbool.h that conforms to C99... yes
checking for _Bool... yes
checking for an ANSI C-conforming const... yes
checking for size_t... yes
checking whether time.h and sys/time.h may both be included... yes
checking for working strtod... yes
checking for gethostbyname... yes
checking for inet_ntoa... yes
checking for memmove... yes
checking for memset... yes
checking for strchr... yes
checking the wxWidgets version... 2.6
checking for wx-config binary... yes
checking for pgsql include files... yes
checking for pgsql... yes
checking for PQexec in -lpq... yes
checking for SSL_connect in -lpq... yes
checking libpq-fe.h usability... yes
checking libpq-fe.h presence... yes
checking for libpq-fe.h... yes
checking pgsql in /usr... ok
checking for wxWidgets... yes
configure: error: Could not find your wxWidgets 2.6 installation. You
might need to use the --with-wx=DIR configure option
error: Bad exit status from /home/user/rpm/tmp/rpm-tmp.96020 (%build)


RPM build errors:   Bad exit status from /home/user/rpm/tmp/rpm-tmp.96020 (%build)


Any suggestions??


-- 
Ray Auge <rayauge@doublebite.com>



Re: Compile on x86_64

From
"Dave Page"
Date:

> -----Original Message-----
> From: pgadmin-support-owner@postgresql.org
> [mailto:pgadmin-support-owner@postgresql.org] On Behalf Of Ray Auge
> Sent: 03 April 2006 04:09
> To: pgadmin-support
> Subject: [pgadmin-support] Compile on x86_64
>
> Hello All,
>
> Firstly, many thanks to all of the devs for an excellent
> tool. I use it (an older version) almost daily at work (on
> i568 FC4 linux) and it rocks.

Glad you like it :-)

> I've just picked-up the latest release src rpm for FC4
> pgadmin3-1.4.1-1.src.rpm
>
> Now I'm trying to rebuild it on my x86_64 box without success.
>

I can't help with RPM building, but the error below seems somewhat
telling:

> configure: error: Could not find your wxWidgets 2.6
> installation. You might need to use the --with-wx=DIR configure option

Where is your wxWidgets installation?

Regards, Dave


Re: Compile on x86_64

From
"Dave Page"
Date:

> -----Original Message-----
> From: Raymond Auge [mailto:rayauge@doublebite.com]
> Sent: 03 April 2006 15:39
> To: Dave Page
> Cc: pgadmin-support
> Subject: RE: [pgadmin-support] Compile on x86_64
>
> > Where is your wxWidgets installation?
>
> All the libs and headers are in standard FC locations (under
> /usr/lib, /usr/include/wx, etc...)
>
> I was under the assumption that an FC4 rpm should build using
> the standard FC4 wx packages. Is this wrong? I have every wx
> package installed.

I don't know about an RPM build, but a normal build should go fine. I
assume you have wxGTK 2.6.something installed, and not anything earlier?
If so, please update to 2.6.2 (or .3). If not, please forward a copy of
the config.log file that's generated.

Regards, Dave


Re: Compile on x86_64

From
Raymond Auge
Date:
On Mon, 2006-04-03 at 08:49 +0100, Dave Page wrote:
>  
> > -----Original Message-----
> > From: pgadmin-support-owner@postgresql.org 
> > [mailto:pgadmin-support-owner@postgresql.org] On Behalf Of Ray Auge
> > Sent: 03 April 2006 04:09
> > To: pgadmin-support
> > Subject: [pgadmin-support] Compile on x86_64
> > 
> > Hello All,
> > 
> > Firstly, many thanks to all of the devs for an excellent 
> > tool. I use it (an older version) almost daily at work (on 
> > i568 FC4 linux) and it rocks.
> 
> Glad you like it :-)
> 
> > I've just picked-up the latest release src rpm for FC4  
> > pgadmin3-1.4.1-1.src.rpm
> > 
> > Now I'm trying to rebuild it on my x86_64 box without success.
> > 
> 
> I can't help with RPM building, but the error below seems somewhat
> telling:
> 
> > configure: error: Could not find your wxWidgets 2.6 
> > installation. You might need to use the --with-wx=DIR configure option
> 
> Where is your wxWidgets installation?

All the libs and headers are in standard FC locations
(under /usr/lib, /usr/include/wx, etc...)

I was under the assumption that an FC4 rpm should build using the
standard FC4 wx packages. Is this wrong? I have every wx package
installed.

> 
> Regards, Dave
> 
-- 
Raymond Augé
Senior System Analyst/Data Architect



Re: Compile on x86_64

From
Devrim GUNDUZ
Date:
Hi,

On Mon, 2006-04-03 at 10:39 -0400, Raymond Auge wrote:
> I was under the assumption that an FC4 rpm should build using the
> standard FC4 wx packages. Is this wrong? I have every wx package
> installed. 

That is wrong. We use Wx from source installation. 

Regards,
-- 
The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: PL/php, plPerlNG - http://www.commandprompt.com/



Re: Compile on x86_64

From
Devrim GUNDUZ
Date:
Hi,

On Sun, 2006-04-02 at 23:08 -0400, Ray Auge wrote:
> Now I'm trying to rebuild it on my x86_64 box without success.

BTW, why do you think that you need 64 bit version of pgAdmin? :-) IMHO
it is as useless as using an 64 bit Firefox -- noone has a web page
which is 4 GB in size :-)

Regards,
-- 
The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: PL/php, plPerlNG - http://www.commandprompt.com/



Re: Compile on x86_64

From
"Dave Page"
Date:

> -----Original Message-----
> From: pgadmin-support-owner@postgresql.org
> [mailto:pgadmin-support-owner@postgresql.org] On Behalf Of
> Devrim GUNDUZ
> Sent: 03 April 2006 16:25
> To: Ray Auge
> Cc: pgadmin-support
> Subject: Re: [pgadmin-support] Compile on x86_64
>
> Hi,
>
> On Sun, 2006-04-02 at 23:08 -0400, Ray Auge wrote:
> > Now I'm trying to rebuild it on my x86_64 box without success.
>
> BTW, why do you think that you need 64 bit version of
> pgAdmin? :-) IMHO it is as useless as using an 64 bit Firefox
> -- noone has a web page which is 4 GB in size :-)

Yeah they do if they use MS Word as an HTML editor ;-).

Regards, Dave.


Re: Compile on x86_64

From
Raymond Auge
Date:
On Mon, 2006-04-03 at 18:20 +0300, Devrim GUNDUZ wrote:
> Hi,
> 
> On Mon, 2006-04-03 at 10:39 -0400, Raymond Auge wrote:
> > I was under the assumption that an FC4 rpm should build using the
> > standard FC4 wx packages. Is this wrong? I have every wx package
> > installed. 
> 
> That is wrong. We use Wx from source installation. 

Hmm, then there is really no point in building an FC4 rpm at all... One
should just build from source. This really goes against the theory of
rpm packaging...

Not a problem. I'll do that. Pity!

As for whether I WANT an x86_64 build or not is irrelevant. If all the
distribution's libraries are compiled x86_64 then that is the arch I
must target, otherwise why use it at all...

I know the pain I must go through to run ix86 applications concurrently
with x86_64, and I don't much enjoy it. I'd rather stick with either one
or the other.

It's simply a matter of principle, and would be no different if I were
using ppc instead (which I do and must compile pgAdminIII there as
well). If there is a src rpm to simplify the move from one platform to
another, then hooray. Otherwise there is always source.

I'm not complaining, I'm just clarifying my situation and my natural
assumptions.

Ray

> 
> Regards,
-- 
Raymond Augé
Senior System Analyst/Data Architect



Re: Compile on x86_64

From
Raymond Auge
Date:
Note this probably won't be an issue on FC5 because the Extras
repository contains wx 2.6.2.

Ray

On Mon, 2006-04-03 at 12:12 -0400, Raymond Auge wrote:
> On Mon, 2006-04-03 at 18:20 +0300, Devrim GUNDUZ wrote:
> > Hi,
> > 
> > On Mon, 2006-04-03 at 10:39 -0400, Raymond Auge wrote:
> > > I was under the assumption that an FC4 rpm should build using the
> > > standard FC4 wx packages. Is this wrong? I have every wx package
> > > installed. 
> > 
> > That is wrong. We use Wx from source installation. 
> 
> Hmm, then there is really no point in building an FC4 rpm at all... One
> should just build from source. This really goes against the theory of
> rpm packaging...
> 
> Not a problem. I'll do that. Pity!
> 
> As for whether I WANT an x86_64 build or not is irrelevant. If all the
> distribution's libraries are compiled x86_64 then that is the arch I
> must target, otherwise why use it at all...
> 
> I know the pain I must go through to run ix86 applications concurrently
> with x86_64, and I don't much enjoy it. I'd rather stick with either one
> or the other.
> 
> It's simply a matter of principle, and would be no different if I were
> using ppc instead (which I do and must compile pgAdminIII there as
> well). If there is a src rpm to simplify the move from one platform to
> another, then hooray. Otherwise there is always source.
> 
> I'm not complaining, I'm just clarifying my situation and my natural
> assumptions.
> 
> Ray
> 
> > 
> > Regards,
-- 
Raymond Augé
Senior System Analyst/Data Architect



Re: Compile on x86_64

From
Devrim GUNDUZ
Date:
Hi,

On Mon, 2006-04-03 at 12:35 -0400, Raymond Auge wrote:
> Note this probably won't be an issue on FC5 because the Extras
> repository contains wx 2.6.2. 

Well... I built the FC5 rpm using the stock WX, but I could do that by
omitting --enable-static.

Regards,
-- 
The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: PL/php, plPerlNG - http://www.commandprompt.com/