Sponsored Content
Full Discussion: Include files
Top Forums Programming Include files Post 3232 by coredump on Wednesday 27th of June 2001 08:10:02 AM
Old 06-27-2001
compiler options?

is it exactly the code u compiled and ran??
check out the angled braces
if u have not compiled with -lsocket option, there vud be a linking problem..
check that out...
if nothing works, get back.
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

how to include external files in tcsh

Hello Simple question about tcsh , i like to make external file that some tcsh script will read from him var=="some value" how can i make the include in tcsh files? Thanks (0 Replies)
Discussion started by: umen
0 Replies

2. Shell Programming and Scripting

include all files under a directory

I want to include all the subnet files under /etc/dhcpd/ to /etc/dhcpd.conf so here is my content of dhcpd.conf ... include "/etc/dhcpd/*"; however, the check-syntax reports syntax error, as they do not recognize the wildcard *, and display that " file /etc/dhcpd/* could not be found. ... (4 Replies)
Discussion started by: fredao
4 Replies

3. Programming

gcc does not include certain .h-files

Hi there! gcc seems not to include available files, see below: What should I do? Look forward to your reply/replies! Thanks Grahamb In the source directory I enter: #gcc -Wall -I/usr/include ./gtkdaq.c > ./out.log 2>&1 Response: In file included from ./gtkdaq.c:3:... (2 Replies)
Discussion started by: grahamb
2 Replies

4. Solaris

Compilation - unable to finding include files

Hey there, This is gotta be a stupid question, if there ever was one, but I am learning a lot by asking such questions. Now I am trying to build this humungous library, which has all kinds a dependencies, which I realize as it makes, and i download all those dependent libs. The compilation is... (1 Reply)
Discussion started by: shriyer123
1 Replies

5. Solaris

include files

Our admin has upgraded our OS solaris system to 5.11 but no more I can compile any trivial or non-trivial code. I'm trying to compile a trivial c++ program(a Helloworld program) but It gives error indicating that include files do not exist (in this trivial case <stdio.h>), it starts compiling but... (1 Reply)
Discussion started by: Newsha
1 Replies

6. UNIX for Dummies Questions & Answers

linux include files

what is the relationship between /usr/include/sys/*.h and /usr/include/unistd.h ? Fuctions in unistd.h are syscalls. Do the fuctions in sys/*.h call syscalls? (7 Replies)
Discussion started by: vistastar
7 Replies

7. Shell Programming and Scripting

include file name to extracted files

I've written the script below to merge only .txt files that exist in one directory into one huge .txt file and ignore other files with other extensions. now the result is one huge .txt file with all the contents of other .txt files how can i add a File Name as a comment before each file? ... (12 Replies)
Discussion started by: miss_dodi
12 Replies

8. HP-UX

How do I include header files outside of my current directory

I am trying to compile a file called PPFormatageMUT.c in which I have included header file which are at some other location but the point is that while compiling the file, it is throwing error saying that error : no such file or directory source code location:... (1 Reply)
Discussion started by: ezee
1 Replies

9. Shell Programming and Scripting

Using Grep Include/Exclude Files

I wrote this korn script and ran into a hole. I can use find to exclude all the hidden directories and to use my include file/exclude files for running a full backup find / -depth -ipath '/home/testuser/.*' -prune -o -print| grep -f include.mydirs | grep -v -f exclude.mydirs but when I... (8 Replies)
Discussion started by: metallica1973
8 Replies

10. Programming

Include files

I have an implementation file tomog.cpp that implements a class called Tomog where I need to include its header file which resides in another place. How can I best specify the include file? I would not like to do #include "../../tomso/tomography/tomog.hpp" I wish to do instead ... (3 Replies)
Discussion started by: kristinu
3 Replies
PG_CONFIG(1)						  PostgreSQL 9.1.9 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. 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.1.9 2013-04-01 PG_CONFIG(1)
All times are GMT -4. The time now is 02:15 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy