Re: Postgres failed to compile on debian x86

[Josh Fremer <jfremer(at)earthlink(dot)net>]

On Sep 5, 2006, at 11:01 AM, Seneca Cunningham wrote:
> Now that I'm connected to a Linux system, I've tried your original  
> configure line of:
>
>   ./configure --with-perl --with-openssl \
>     --with-includes=/usr/include/linux/:/usr/include \
>     --with-libraries=/usr/lib/
>
> and reproduced your results.  Change that to:
>
>   ./configure --with-perl --with-openssl \
>     --with-includes=/usr/include --with-libraries=/usr/lib
>
> and it should work.  Incidentally, the --with-includes and
> --with-libraries aren't necessary at this point as /usr/include  
> and /usr/lib are in the default search path of gcc, ld, and cpp.

Installation complete.  Thanks so much for all your help.

For completeness, I'd like to mention that after a successful  
configure, make failed on my setup with the following error:

gcc -O2 -Wall -Wmissing-prototypes -Wpointer-arith -Winline -Wendif- 
labels -fno-strict-aliasing -Wno-error  -L../../../../src/port  -Wl,- 
rpath,/usr/local/pgsql/lib preproc.o type.o ecpg.o ecpg_keywords.o  
output.o keywords.o c_keywords.o ../ecpglib/typename.o descriptor.o  
variable.o -lpgport -lssl -lcrypto -lz -lreadline -lcrypt -lresolv - 
lnsl -ldl -lm   -o ecpg
/usr/lib/libc_nonshared.a(elf-init.oS)(.text.__i686.get_pc_thunk.bx 
+0x0): In function `__i686.get_pc_thunk.bx':
: multiple definition of `__i686.get_pc_thunk.bx'
../ecpglib/typename.o(.gnu.linkonce.t.__i686.get_pc_thunk.bx+0x0):  
first defined here
collect2: ld returned 1 exit status
make[4]: *** [ecpg] Error 1
make[4]: Leaving directory `/home/josh/postgresql-8.1.4/src/ 
interfaces/ecpg/preproc'
make[3]: *** [all] Error 2
make[3]: Leaving directory `/home/josh/postgresql-8.1.4/src/ 
interfaces/ecpg'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/home/josh/postgresql-8.1.4/src/interfaces'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/josh/postgresql-8.1.4/src'
make: *** [all] Error 2


After a little research I tried upgrading from gcc-3.4 to gcc-3.5,  
which is the latest version currently available in debian stable.   
The error persisted.  After that I tried upgrading to gcc-4.0 out of  
debian testing, which solved the issue.

Again, thanks for your patience and great advice.

Cheers,

Josh