08-17-2008
It means dependency that .c files are created from .pc files.
So it's bellow description you should write.
---------------
.pc.c:
---------------
Regards.
10 More Discussions You Might Find Interesting
1. Programming
Gurus,
I am teaching myself C and have a question.
I wrote a small prog that reads characters as entered at the prompt and checks the value for EOF.
Unless I am 100% wrong, the value will be '1' until getchar() has anything to read in my stream.
/* PROG 1 */
#include <stdio.h>
... (4 Replies)
Discussion started by: alan
4 Replies
2. Shell Programming and Scripting
#!/usr/bin/perl
open(STDOUT, ">>$Textfile")
open(STDERR, ">>$Textfile")
print "program running\n";
$final = join("+", $initial,$final) #5
close (STDOUT);
close (STDERR);Hi all, above is my perl code. Notice i have captured the stdout and stderr to the same textfile. my code is expected to... (1 Reply)
Discussion started by: new2ss
1 Replies
3. Shell Programming and Scripting
Hi,
I am re-writing a script I wrote which emulated the "rm" command, in my orginal script I had problems with precedence, I did find a way round it by creating a seperate case statements which checked the options and performed the actions accordingly, does anyone know if I can use getopts... (1 Reply)
Discussion started by: jack1981
1 Replies
4. High Performance Computing
I am new to creating makefiles.
I have several fortran programs in a folder called as "test" and also have several subroutines in another folder (which is inside this test folder) called as libry
My makefile is in the folder "test"
I want to create a makefile which can access the files in... (2 Replies)
Discussion started by: explorer
2 Replies
5. UNIX for Advanced & Expert Users
Hi, I'm trying to run the module load command in a Makefile and i'm getting the following error:
make: module: command not found
Why is this? Is there any way to run this command in a Makefile?
NOTE: command - module load msjava/sunjdk/1.5.0 works fine outside of the Makefile (2 Replies)
Discussion started by: hernandinho
2 Replies
6. UNIX for Advanced & Expert Users
I have 2 libraries in 2 different directories that I build with Makefiles.
library B depends on library A. If I modify a .cpp file in library A and run lib B's Makefile can I have B's makefile to automatically rebuild library A?
I am now rebuilding A, followed by B... but I'd like B to... (0 Replies)
Discussion started by: wwuster
0 Replies
7. Homework & Coursework Questions
Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted!
1. The problem statement, all variables and given/known data:
Basically, the prompt is make a makefile with various sub makefiles in their respective subdirectories. All code... (1 Reply)
Discussion started by: Tatl
1 Replies
8. Shell Programming and Scripting
Hello,
I am trying to write a small acript to change directory to $HOME depending on the user logged in. However when i provide this command
say,
ABC_USER=myself
cd ~${ABC_USER} i am getting the following error,
ksh: ~myself: not found
I know i am doing something really silly but... (4 Replies)
Discussion started by: arvindspr06
4 Replies
9. UNIX for Dummies Questions & Answers
Hi All,
I am new to unix.
In this forum some days back, I have read something like below:
1) Do not use perl if awk can do your work.
2) Do not use awk if sed can do your work.
.
.
.
I do not re-collect the whole thing. I think it is good to know the precedence of using these... (2 Replies)
Discussion started by: Prathmesh
2 Replies
10. Programming
Hi All,
We have moved our OS from Sun Solaris to Linux and also some of the compilers.
Our old makefile used to be as below:
CC=cc
FLAGS=-G -KPIC -DLG_SOLARIS_OS
DEFINES=-DSunOS
SYSLIBS=-lc
.SUFFIXES : .c
.c.o : ;$(CC) -c $(FLAGS) $(DEFINES) $*.c -o $*.o
... (3 Replies)
Discussion started by: shash
3 Replies
LEARN ABOUT OPENDARWIN
deb-symbols
deb-symbols(5) dpkg suite deb-symbols(5)
NAME
deb-symbols - Debian's extended shared library information file
SYNOPSIS
symbols
DESCRIPTION
The symbol files are shipped in Debian binary packages, and its format is a subset of the template symbol files used by dpkg-gensymbols(1)
in Debian source packages.
The format for an extended shared library dependency information entry in these files is:
library-soname main-dependency-template
[| alternative-dependency-template]
[...]
[* field-name: field-value]
[...]
symbol minimal-version [id-of-dependency-template]
The library-soname is exactly the value of the SONAME field as exported by objdump(1). A dependency-template is a dependency where #MINVER#
is dynamically replaced either by a version check like "(>= minimal-version)" or by nothing (if an unversioned dependency is deemed
sufficient).
Each exported symbol (listed as name@version, with version being "Base" if the library is not versioned) is associated to a minimal-version
of its dependency template (the main dependency template is always used and will end up being combined with the dependency template
referenced by id-of-dependency-template if present). The first alternative dependency template is numbered 1, the second one 2, etc.
Each entry for a library can also have some fields of meta-information. Those fields are stored on lines starting with an asterisk.
Currently, the only valid fields are:
Build-Depends-Package
It indicates the name of the "-dev" package associated to the library and is used by dpkg-shlibdeps to make sure that the dependency
generated is at least as strict as the corresponding build dependency (since dpkg 1.14.13).
Ignore-Blacklist-Groups
It indicates what blacklist groups should be ignored, as a whitespace separated list, so that the symbols contained in those groups
get included in the output file (since dpkg 1.17.6). This should only be necessary for toolchain packages providing those
blacklisted symbols. The available groups are system dependent, for ELF and GNU-based systems these are aeabi and gomp.
EXAMPLES
Simple symbols file
libftp.so.3 libftp3 #MINVER#
DefaultNetbuf@Base 3.1-1-6
FtpAccess@Base 3.1-1-6
[...]
Advanced symbols file
libGL.so.1 libgl1
| libgl1-mesa-glx #MINVER#
* Build-Depends-Package: libgl1-mesa-dev
publicGlSymbol@Base 6.3-1
[...]
implementationSpecificSymbol@Base 6.5.2-7 1
[...]
SEE ALSO
https://wiki.debian.org/Projects/ImprovedDpkgShlibdeps
dpkg-shlibdeps(1), dpkg-gensymbols(1).
1.19.0.5 2018-04-16 deb-symbols(5)