Sponsored Content
Top Forums Programming Help building and using a shared object (x64) Post 302617897 by Maelstrom on Tuesday 3rd of April 2012 08:47:59 AM
Old 04-03-2012
Quote:
Originally Posted by migurus
just a side note: why not to use shared memory (shmop,shmctl,shmget)?
Because I pack a large number of data arrays in the shared object, and I would need to do more work to also implement some kind of memory map on that.
Besides, my shared objects will be patches to my application.
====================================================================
To wrap this thread up, I just want to thank you, Corona688, for your advice.
Although they didn't help me as much as I hoped, you definitely gave me some new things to feed the brain Smilie

Now hold on to you shorts, here comes the solution for my problem Smilie

As I said on my first post, on CentOS 32bit release everything was ok, but on 64bit, I got garbage addresses when performing dlsym, hence I assumed it was some kind of compiler issue. After compiling my shared objects with a lot of possible combinations of options for gcc and failing, I got the most retarded idea ever : I just moved util_load_library to another C+h file, and it worked without any complains. The C file where I moved it is one of the files from where I call my loader function.

I assume this had something to do with the fact that the initial C+h file could have been packed in some other so, and maybe this messed up the address space on the 64bit version.

Anyway, just wanted to let you know I solved my issue in the weirdest way possible Smilie

Thanks a lot for you support!

Last edited by Maelstrom; 04-03-2012 at 09:56 AM..
 

10 More Discussions You Might Find Interesting

1. Programming

Does my ld support shared object creation

Hi, I have been trying to create a sharef object on my HP UX 11 machine (HP-UX <myhostname> B.11.00 A 9000/879 ...... two-user license) to create the shared object first I am creating the object file using cc -Aa -c +z dyn.c (I use -Aa and +z as per HP's manual on linkers ) to create the... (0 Replies)
Discussion started by: linuxpenguin
0 Replies

2. Linux

Shared Object File

Hi All, I created the share object file using gcc -shared -fpic mypp.cpp -o myp.so but, pls tell me how to link this .so file to my client program. Thanks (0 Replies)
Discussion started by: sarwan
0 Replies

3. AIX

Shared Object library problem

Hi, When using shared objects on AIX 4.3 i am getting runtime problems. I have a small sample program which links to a shared object libray, oracle and system related libraries. At runtime it fails (gives segmentation fault and coredump ) in one proc file when executing login statement. But... (0 Replies)
Discussion started by: suman_jakkula
0 Replies

4. Programming

calling a shared object from a daemon

Hi I have a multithreaded daemon(server) which will accept connections from various clients and sends back results to them. In order to serve my daemon clients, it has to establish a TCP connection to another server(vendor supplied which is listening on a specific TCP port) and gets the... (11 Replies)
Discussion started by: axes
11 Replies

5. UNIX for Advanced & Expert Users

Issue with shared object in AIX

Hi All, I have a problem with the shared objects setup in AIX. We have a customized shell written by the developers over here. When i issue a MQ Series command (mqsilist) it is giving the error as . All the commands making use of this libImbCmdLib.a.so is failing. But when executed in normal... (1 Reply)
Discussion started by: dhanamurthy
1 Replies

6. Shell Programming and Scripting

Any way to access shared object using shell

Hi, I have created a shared object (abc.so) which has a function sum(int a, int b). Is there any way to load the "abc.so" and use the sum function using shell script.. thanks in advance (2 Replies)
Discussion started by: yhacks
2 Replies

7. AIX

AIX 5.2 C++ shared object issue

Hi all, I am developing an application with two components. One "c" binary and one "C++" shared object. While execution, the shared object crashes out and core dump is created whenever "new" is executed. But if i use malloc this will work perfectly. I tried to use dbx. Below given was... (1 Reply)
Discussion started by: itssujith
1 Replies

8. Programming

Error while running shared object

Hello, While running a c++ shared object on AIX I am facing below error - rtld: 0712-001 Symbol __ct__3ETDFv was referenced from module /bancs/aml/lib/libmonitor.so(), but a runtime definition of the symbol was not found. rtld: 0712-001 Symbol etd_insert__3ETDFv was... (3 Replies)
Discussion started by: yatrik007
3 Replies

9. Red Hat

shared object

Hi, I would like to create a shared object ( .so). This shared object 1. uses the functions from a library. 2. Also it should be able to use the global variable in an app To achieve this what should I do ? 1) To use the functions in the library should I give the -ld option while... (1 Reply)
Discussion started by: rvan
1 Replies

10. Programming

Shared Object Question

Hello, I am new to programming shared objects and I was hoping someone could tell me if what I want to do is possible, or else lead me in the right direction. I have a main program that contains an abstract base class. I also have a subclass that I'm compiling as a shared object. The subclass... (13 Replies)
Discussion started by: dorik
13 Replies
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)
All times are GMT -4. The time now is 02:29 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy