Hello,
I am always confused about adding library path for ./configure when compiling software under Linux Debian based OS. For example the README of the software tells
--with-boost=PATH specify directory for the boost header files
--with-mpi=PATH specify prefix directory for... (4 Replies)
Friends,
I need help with the following in UNIX.
Merge all csv files in one folder considering only 1 header row and ignoring header of all other files.
FYI - All files are in same format and contains same headers.
Thank you (4 Replies)
Hi,
I'm porting code from Windows to HP-UX 11, compiling with g++.
I'm getting a compilation error on the system's debug.h include file, which is included very indirectly through a series of other system include files. The one I am including is <map> .
The errors I am getting are:... (4 Replies)
Hey,
I'm trying to install fluxbox. Currently i'm running Mandrake 10.1 with KDE. When i ./configure fluxbox it returns an error saying
configure: error: Fluxbox requires the X Window System libraries and headers.
Where do i download the X window System libraries and headers from? I... (3 Replies)
Hi,
I tried to compile a code referencing XWindows Programming Functions, i found out that i have no XWindows Header files present. But XWindows is running on my System.Is the XWindows Development package different from the XWindows running on my system? if so, can you instruct me how to... (0 Replies)
Hello,
We someone help me resolve this problem. I have window 2000 professional, windows 98 and Unixware 7.0.1 on the network. I was able to establish connection with all. However, l was unable to ping window 98 from window 2000 professional. I was able to ping the window 2000 from the window... (10 Replies)
I registered a printer hp123 on Sun Solaris Server.
I think my printer is expecting a carriage return and linefeed combination at the end of each line (DOS standard), but unix files only have linefeeds at the end of each line.
How can I configure the lp system to filter files passed to it?... (1 Reply)
PG_CONFIG(1) PostgreSQL 9.2.7 Documentation PG_CONFIG(1)NAME
pg_config - retrieve information about the installed version of PostgreSQL
SYNOPSIS
pg_config [option...]
DESCRIPTION
The pg_config utility prints configuration parameters of the currently installed version of PostgreSQL. It is intended, for example, to be
used by software packages that want to interface to PostgreSQL to facilitate finding the required header files and libraries.
OPTIONS
To use pg_config, supply one or more of the following options:
--bindir
Print the location of user executables. Use this, for example, to find the psql program. This is normally also the location where the
pg_config program resides.
--docdir
Print the location of documentation files.
--htmldir
Print the location of HTML documentation files.
--includedir
Print the location of C header files of the client interfaces.
--pkgincludedir
Print the location of other C header files.
--includedir-server
Print the location of C header files for server programming.
--libdir
Print the location of object code libraries.
--pkglibdir
Print the location of dynamically loadable modules, or where the server would search for them. (Other architecture-dependent data files
might also be installed in this directory.)
--localedir
Print the location of locale support files. (This will be an empty string if locale support was not configured when PostgreSQL was
built.)
--mandir
Print the location of manual pages.
--sharedir
Print the location of architecture-independent support files.
--sysconfdir
Print the location of system-wide configuration files.
--pgxs
Print the location of extension makefiles.
--configure
Print the options that were given to the configure script when PostgreSQL was configured for building. This can be used to reproduce
the identical configuration, or to find out with what options a binary package was built. (Note however that binary packages often
contain vendor-specific custom patches.) See also the examples below.
--cc
Print the value of the CC variable that was used for building PostgreSQL. This shows the C compiler used.
--cppflags
Print the value of the CPPFLAGS variable that was used for building PostgreSQL. This shows C compiler switches needed at preprocessing
time (typically, -I switches).
--cflags
Print the value of the CFLAGS variable that was used for building PostgreSQL. This shows C compiler switches.
--cflags_sl
Print the value of the CFLAGS_SL variable that was used for building PostgreSQL. This shows extra C compiler switches used for building
shared libraries.
--ldflags
Print the value of the LDFLAGS variable that was used for building PostgreSQL. This shows linker switches.
--ldflags_ex
Print the value of the LDFLAGS_EX variable that was used for building PostgreSQL. This shows linker switches used for building
executables only.
--ldflags_sl
Print the value of the LDFLAGS_SL variable that was used for building PostgreSQL. This shows linker switches used for building shared
libraries only.
--libs
Print the value of the LIBS variable that was used for building PostgreSQL. This normally contains -l switches for external libraries
linked into PostgreSQL.
--version
Print the version of PostgreSQL.
-?, --help
Show help about pg_config command line arguments, and exit.
If more than one option is given, the information is printed in that order, one item per line. If no options are given, all available
information is printed, with labels.
NOTES
The option --includedir-server was added in PostgreSQL 7.2. In prior releases, the server include files were installed in the same location
as the client headers, which could be queried with the option --includedir. To make your package handle both cases, try the newer option
first and test the exit status to see whether it succeeded.
The options --docdir, --pkgincludedir, --localedir, --mandir, --sharedir, --sysconfdir, --cc, --cppflags, --cflags, --cflags_sl, --ldflags,
--ldflags_sl, and --libs were added in PostgreSQL 8.1. The option --htmldir was added in PostgreSQL 8.4. The option --ldflags_ex was added
in PostgreSQL 9.0.
In releases prior to PostgreSQL 7.1, before pg_config came to be, a method for finding the equivalent configuration information did not
exist.
EXAMPLE
To reproduce the build configuration of the current PostgreSQL installation, run the following command:
eval ./configure `pg_config --configure`
The output of pg_config --configure contains shell quotation marks so arguments with spaces are represented correctly. Therefore, using
eval is required for proper results.
PostgreSQL 9.2.7 2014-02-17 PG_CONFIG(1)