Re: exposing pg_controldata and pg_config as functions - Mailing list pgsql-hackers

From Erik Rijkers
Subject Re: exposing pg_controldata and pg_config as functions
Date
Msg-id 4b1905717e204e77d5ce52df7f67f12e@xs4all.nl
Whole thread Raw
In response to exposing pg_controldata and pg_config as functions  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: exposing pg_controldata and pg_config as functions
Re: exposing pg_controldata and pg_config as functions
List pgsql-hackers
> [2015082503-pgconfig_controldata.diff]

I tried to build this, and the patch applies cleanly but then a ld error 
emerges:

(The first four lines (about gram.y) are standard warnings; the error 
starts from the ld line)


In file included from gram.y:14908:0:
scan.c: In function ‘yy_try_NUL_trans’:
scan.c:10307:23: warning: unused variable ‘yyg’ [-Wunused-variable]     struct yyguts_t * yyg = (struct
yyguts_t*)yyscanner;/* This var 
 
may be unused depending upon options. */                       ^
/usr/bin/ld: Dwarf Error: found dwarf version '4', this reader only 
handles version 2 information.
utils/fmgrtab.o:(.rodata+0x19f78): undefined reference to `_null_'
utils/fmgrtab.o:(.rodata+0x1a078): undefined reference to `_null_'
collect2: error: ld returned 1 exit status
make[2]: *** [postgres] Error 1
make[1]: *** [all-backend-recurse] Error 2
make: *** [all-src-recurse] Error 2



The configure was:

./configure \ --prefix=/var/data1/pg_stuff/pg_installations/pgsql.controldata \ --with-pgport=6594 \ 
--bindir=/var/data1/pg_stuff/pg_installations/pgsql.controldata/bin.fast 
\ 
--libdir=/var/data1/pg_stuff/pg_installations/pgsql.controldata/lib.fast 
\ --sysconfdir=/var/data1/pg_stuff/pg_installations/pgsql.controldata/etc 
\ --quiet --enable-depend --with-perl --with-python --with-openssl 
--with-libxml \ --with-extra-version=_controldata_20151030_1432_c5057b2b3481 
--enable-tap-tests




Thanks,

Erik Rijkers








pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Dangling Client Backend Process
Next
From: rafael
Date:
Subject: Re: pg_dump