11-10-2009
I check the gcc option "mno-app-regs" and found that it is specific with solaris sparc option.So could you please tell me the appropriate option for opensolaris.
10 More Discussions You Might Find Interesting
1. Programming
Hi,
I am facing problem while creating shared library using makeC++SharedLib_r. I am using the following command
makeC++SharedLib_r -E rpcresolver.exp -L/home/myAccount/lib -lcxxbase -lfsbutil_r -lpthreads -bimport:/usr/lib/sna/appc_r.exp -o resolver-shared.o -p 0 rpcresolver.o
Every time... (0 Replies)
Discussion started by: satguyz
0 Replies
2. Linux
Hi,
I am trying to create shared library. When i run the script to build the library i get these errors
ld: warning: option -o appears more than once, first setting taken
ld: fatal: file libgc.so.0: open failed: No such file or directory
ld: fatal: File processing errors. No output written... (0 Replies)
Discussion started by: masg1
0 Replies
3. UNIX for Dummies Questions & Answers
Getting the following error ,
ld: /opt/syncsort39/lib/libsyncsort.sl: Mismatched ABI. 64-bit PA shared library found in 32-bit link.
Is there any difference in the ld options in opt file while linking a 64 bit shared library ? Or is the problem because we are trying to link both 32 bit and 64... (3 Replies)
Discussion started by: arunkumar_mca
3 Replies
4. Programming
I need to create a shared library to access an in memory DB. The DB is not huge, but big enough to make it cumbersome to carry around in every single process using the shared library. Luckily, it is pretty static information, so I don't need to worry much about synchronizing the data between... (12 Replies)
Discussion started by: DreamWarrior
12 Replies
5. Programming
I am writing a shared library in Linux (but compatible with other UNIXes) and I want to allow multiple instances to share a piece of memory -- 1 byte is enough. What's the "best" way to do this? I want to optimize for speed and portability.
Obviously, I'll have to worry about mutual exclusion. (0 Replies)
Discussion started by: otheus
0 Replies
6. Red Hat
Hi All,
I have RHEL 5 installed in my system. Something must has happened because when i reboot the server, it came with many error..
/usr/bin/rhgb-client -- error while loading shared libraries: libpopt.so.0. Can't open shared object files. No such file/directory
It finnaly ends with the... (0 Replies)
Discussion started by: c00kie88
0 Replies
7. Shell Programming and Scripting
Hi:
I have a library that it only offers Makefile for building static library. It built libxxx.a file. How do I in any way build a shared library? (either changin the Makefile or direct script or command to build shared library)
Thanks. (1 Reply)
Discussion started by: cpthk
1 Replies
8. Programming
Hello.
I am new to this forum and I would like to ask for advice about low level POSIX programming.
I have to implement a POSIX compliant C shared library.
A file will have some variables and the shared library will have some functions which need those variables.
There is one special... (5 Replies)
Discussion started by: iamjag
5 Replies
9. AIX
I'm trying to install libiconv to AIX 7.1 from an rpm off of the perzl site. The rpm appears to install but I get this error message.
add shr4.o shared members from /usr/lib/libiconv.a to /opt/freeware/lib/libiconv.a
add shr.o shared members from /usr/lib/libiconv.a to ... (5 Replies)
Discussion started by: kneemoe
5 Replies
10. Linux
Hi All,
i am facing shared library error, below is the output of the command I am executing on my client
# /usr/software/bin/sudo
/usr/software/bin/sudo: error while loading shared libraries: libaudit.so.1: cannot open shared object file: No such file or directory
#
I tried install... (4 Replies)
Discussion started by: muzaffar.k
4 Replies
allocate(1) allocate(1)
NAME
allocate - device allocation
SYNOPSIS
allocate [-s] [-U uname] device
allocate [-s] [-U uname] -g dev-type
allocate [-s] [-U uname] -F device
The allocate utility manages the ownership of devices through its allocation mechanism. It ensures that each device is used by only one
qualified user at a time.
The device argument specifies the device to be manipulated. To preserve the integrity of the device's owner, the allocate operation is exe-
cuted on all the device special files associated with that device.
The argument dev-type is the device type to be operated on and can only be used with the -g option.
The default allocate operation allocates the device special files associated with device to the uid of the current process.
If the -F option is specified, the device cleaning program is executed when allocation is performed. This cleaning program is found in
/etc/security/lib. The name of this program is found in the device_allocate(4) entry for the device in the dev-exec field.
Only authorized users may allocate a device. The required authorizations are specified in device_allocate(4).
The following options are supported:
-g dev-type Allocates a non-allocated device with a device-type matching dev-type.
-s Silent. Suppresses any diagnostic output.
-F device Reallocates the device allocated to another user. This option is often used with -U to reallocate a specific device to a
specific user. Only a user with the solaris.device.revoke authorization is permitted to use this option.
-U uname Uses the user ID uname instead of the user ID of the current process when performing the allocate operation. Only a user
with the solaris.device.revoke authorization is permitted to use this option.
The following exit values are returned:
non--zero An error occurred.
/etc/security/device_allocate
/etc/security/device_maps
/etc/security/dev/*
/etc/security/lib/*
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
deallocate(1), list_devices(1), bsmconv(1M), dminfo(1M), mkdevalloc(1M), mkdevmaps(1M), device_allocate(4), device_maps(4), attributes(5)
The functionality described in this man page is available only if the Basic Security Module (BSM) has been enabled. See bsmconv(1M) for
more information.
/etc/security/dev, mkdevalloc(1M), and mkdevmaps(1M) might not be supported in a future release of the Solaris Operating Environment.
28 Mar 2005 allocate(1)