One solution is to take your libraries with you, at least in a limited sense,
One does this by using the link option:
before you transfer the executable to another platform (a similar platform, I hasten to add). I have done this several times without problems.
A draw back is that the resulting executable will be, of course, far larger in size compared to its dynamic version.
Just getting into the Unix command line programming and am unable to run any program I write. I am using a Makefile and the source is compiling but when I enter the name of the output file I get back:
bash: lab01exe.out: command not found
I'm sure I am just dooing something simple... (2 Replies)
I am confused about how to use a .exe file in unix along with a compiled C++ program. I've been using emacs and I compiled with g++, but I have no idea how that relates to use with a .exe. (1 Reply)
iam in the way of making graphics using SDL.i copied from cd usign
mount -a /cdrom
cd /cdrom
cp SDL-1.2.11.tar.gz /usr/test
cd /usr/test
gunzip SDL-1.2.11.tar.gz
tar -xf SDL-1.2.11.tar
cd SDL-1.2.11
./configure
...
...
it stops at
checking whether the c compiler... (4 Replies)
Hello All,
I have coded a C program which looks something like below... (program name: test.c)
#include<stdio.h>
main()
{
int dist,dm,dcm;
printf(" Enter the distance between 2 cities in KM : ");
scanf("%d",&dist);
dm=dist*1000;
dcm=dist*10;
printf("Distance between 2 cities in... (6 Replies)
I am trying to make an application which works on unix to work on linux. I already tried copying the binary files and start it up but I am getting an error stating "Cannot execute binary file". Then I tried to recompile but i am getting an error whenever I tried to recompile. I am getting the... (1 Reply)
Long story short: I'm working inside of a Unix SSH under a bash shell. I have to code a C program that generates a random number. Then I have to call the compiled C program with a Perl program to run the C program 20 times and put all the generated random #s into a text file, then print that text... (1 Reply)
Hi,
We upgraded our servers from solaris 9 to 10. We recompiled all the Pro*C programs with the new oracle version as well. Oracle is 11g. We are facing core dump with the below error for certain executions. But when we are placing new statements between the error fucntion we get junk values to... (1 Reply)
I have put some yellow color codes and works well.
I call the funstion using
print_usage(stderr, 0);
I would like to know if there is any way, to store the ansi color codes in variables and then call them inside fprintf.
Or have a format followed by the strings I want to output.
... (5 Replies)
Hello everyone,
I would like to setup a lamp server from a minimal distro and to compile PHP, MySQL and Apache myself.
I have chosen CentOS minimal for the OS and I am trying to build the stack by hand... But well, it appears I need some help!
First: I am looking for good and recent... (3 Replies)
Discussion started by: freddie50
3 Replies
LEARN ABOUT DEBIAN
dh_strip
DH_STRIP(1) Debhelper DH_STRIP(1)NAME
dh_strip - strip executables, shared libraries, and some static libraries
SYNOPSIS
dh_strip [debhelperoptions] [-Xitem] [--dbg-package=package] [--keep-debug]
DESCRIPTION
dh_strip is a debhelper program that is responsible for stripping executables, shared libraries, and static libraries that are not used for
debugging.
This program examines your package build directories and works out what to strip on its own. It uses file(1) and file permissions and
filenames to figure out what files are shared libraries (*.so), executable binaries, and static (lib*.a) and debugging libraries (lib*_g.a,
debug/*.so), and strips each as much as is possible. (Which is not at all for debugging libraries.) In general it seems to make very good
guesses, and will do the right thing in almost all cases.
Since it is very hard to automatically guess if a file is a module, and hard to determine how to strip a module, dh_strip does not
currently deal with stripping binary modules such as .o files.
OPTIONS -Xitem, --exclude=item
Exclude files that contain item anywhere in their filename from being stripped. You may use this option multiple times to build up a
list of things to exclude.
--dbg-package=package
Causes dh_strip to save debug symbols stripped from the packages it acts on as independent files in the package build directory of the
specified debugging package.
For example, if your packages are libfoo and foo and you want to include a foo-dbg package with debugging symbols, use dh_strip
--dbg-package=foo-dbg.
Note that this option behaves significantly different in debhelper compatibility levels 4 and below. Instead of specifying the name of
a debug package to put symbols in, it specifies a package (or packages) which should have separated debug symbols, and the separated
symbols are placed in packages with -dbg added to their name.
-k, --keep-debug
Debug symbols will be retained, but split into an independent file in usr/lib/debug/ in the package build directory. --dbg-package is
easier to use than this option, but this option is more flexible.
NOTES
If the DEB_BUILD_OPTIONS environment variable contains nostrip, nothing will be stripped, in accordance with Debian policy (section 10.1
"Binaries").
CONFORMS TO
Debian policy, version 3.0.1
SEE ALSO debhelper(7)
This program is a part of debhelper.
AUTHOR
Joey Hess <joeyh@debian.org>
9.20120909 2012-05-19 DH_STRIP(1)