10-23-2019
I've found a man page for libPW
here. Its use appears to be deprecated, which is probably why you can't find it. If you wanted to run the programs that link to it I might be inclined to identify the functions in that library and see if equivalents exist in the standard C library.
Andrew
10 More Discussions You Might Find Interesting
1. Programming
Hi everybody!
I'm not familiar with C programming in Unix, but I'm trying to make work an example to execute external procedures (developed in C) from PL/SQL.
The example includes .c and .pc source files, which I have compiled succesfully.
After that, links the .o files into .so to declare... (0 Replies)
Discussion started by: lwnorowski
0 Replies
2. Programming
can i know what is the differnece between using librery function and system calls for performing any of the operation like read, write and other operations (1 Reply)
Discussion started by: MKSRaja
1 Replies
3. Programming
This is a quick question: is '%b' a valid conversion to use in any of the 'printf' routines for binary data? I did some searching through old posts in this site and found some that said it is, though internet searching outside this site, as well as books I've looked at (both recent and not so... (1 Reply)
Discussion started by: cleopard
1 Replies
4. Shell Programming and Scripting
Hi all,
My aim is to get the log details of datastage job using unix scipt.
we know that DSjob are used to get the log details from datastage universe through the adminstrator.can we call that DSjob rountine in our unix script.
Thanks in advance
Regards,
NimmyRaju:) (0 Replies)
Discussion started by: nimmyraju
0 Replies
5. Solaris
Hi,
I have an executable that takes indefinitely long time to search for the libsendfile.so in particular solaris machines only. The library is actually in the /lib folder. Where as it works fine on few of the machines, it takes long time in few others.
I have checked crle options. Its... (1 Reply)
Discussion started by: kk2202
1 Replies
6. Shell Programming and Scripting
Hello guys,
In my script, I need to add two other routines where I Manipulate the files with a 'x'
The routine looks at CLI named qip-getobjectprof that references a input file named hosts_list.txt
Then I use the CLI named qip-setobject to set the orignal name with an 'x'and move the... (3 Replies)
Discussion started by: richsark
3 Replies
7. Solaris
An application was getting built using Motif 1.2 that used come along Solaris 6 OS for compiling and linking. Application is run using Motif 2.1 on Solaris 10 and it is working fine.
Application compilation and linking is working fine on Solaris 10 with Motif 2.1.0 but running the application... (0 Replies)
Discussion started by: shafi2all
0 Replies
8. Shell Programming and Scripting
The script distributes files from an AIX server using iether ftp or sftp depending on the constraint of the destination server. I am interested in having the error checking routine critically reviewed. I will only include an excerpt from the script concerning error trapping: (where $FTP_OUT is the... (7 Replies)
Discussion started by: peleton
7 Replies
9. AIX
My product has 2 libraries say "x & y".
x depends on y.
During the installation of my products package, user will be prompted for his own location to copy my product libraries.
Installation will copy libraries "x & y" and create my product specific ENV variable say "MYPATH" pointing to User... (4 Replies)
Discussion started by: erra_krishna
4 Replies
10. UNIX for Beginners Questions & Answers
Hello,
i have installed open-motif -2.3.8_1 X11 Toolkit on freebsd32bit machine.
wanna compile a little script. script is ok. already compiled on other machine (linux)
the message is as follows
cc -o button button.c -lXm -lXt -lX11
button.c:3:10: fatal error: 'Xm/Xm.h' file not found... (5 Replies)
Discussion started by: Sennenmut
5 Replies
LEARN ABOUT DEBIAN
imager::probe
Imager::Probe(3pm) User Contributed Perl Documentation Imager::Probe(3pm)
NAME
Imager::Probe - hot needle of inquiry for libraries
SYNOPSIS
require Imager::Probe;
my %probe =
(
# short name of what we're looking for (displayed to user)
name => "FOO",
# pkg-config lookup
pkg => [ qw/name1 name2 name3/ ],
# perl subs that probe for the library
code => [ &foo_probe1, &foo_probe2 ],
# or just: code => &foo_probe,
inccheck => sub { ... },
libcheck => sub { ... },
# search for this library if libcheck not supplied
libbase => "foo",
# library link time options, uses libbase to build options otherwise
libopts => "-lfoo",
# C code to check the library is sane
testcode => "...",
# header files needed
testcodeheaders => [ "stdio.h", "foo.h" ],
);
my $result = Imager::Probe->probe(\%probe)
or print "Foo library not found: ",Imager::Probe->error;
DESCRIPTION
Does the probes that were hidden in Imager's Makefile.PL, pulled out so the file format libraries can be externalized.
The return value is either nothing if the probe fails, or a hash containing:
o "INC" - "-I" and other C options
o "LIBS" - "-L", "-l" and other link-time options
o "DEFINE" - "-D" options, if any.
The possible values for the hash supplied to the probe() method are:
o "pkg" - an array of pkg-config names to probe for. If the pkg-config checks pass, "inccheck" and "libcheck" aren't used.
o "inccheck" - a code reference that checks if the supplied include directory contains the required header files.
o "libcheck" - a code reference that checks if the supplied library directory contains the required library files. Note: the Makefile.PL
version of this was supplied all of the library file names instead. "libcheck" can also be an arrayref of library check code
references, all of which must find a match for the library to be considered "found".
o "libbase" - if "inccheck" is supplied, but "libcheck" isn't, then a "libcheck" that checks for "lib"libbase$Config{_a} and
"lib"libbase.$Config{so} is created. If "libopts" isn't supplied then that can be synthesized as "-llibbase". "libbase" can also be an
arrayref of library base names to search for, in which case all of the libraries mentioned must be found for the probe to succeed.
o "libopts" - if the libraries are found via "inccheck"/"libcheck", these are the "-l" options to supply during the link phase.
o "code" - a code reference to perform custom checks. Returns the probe result directly. Can also be an array ref of functions to call.
o "testcode" - test C code that is run with Devel::CheckLib. You also need to set "testcodeheaders".
o "testcodeprologue" - C code to insert between the headers and the main function.
o "incpath" - $Config{path_sep} separated list of header file directories to check, or a reference to an array of such.
o "libpath" - $Config{path_sep} separated list of library file directories to check, or a reference to an array of such.
o "alternatives" - an optional array reference of alternate configurations (as hash references) to test if the primary configuration
isn't successful. Each alternative should include an "altname" key describing the alternative. Any key not mentioned in an
alternative defaults to the value from the main configuration.
perl v5.14.2 2012-04-29 Imager::Probe(3pm)