What bakunin said is true, but in the interest of clairvoyant debugging, what happens if you put the following call before your first call to cvs?
Are you developing and running on the same host?
I just set up an ftp server with Red Hat 5.2. I am doing the work, I'm baby stepping, but it seems like every step I get stuck. Currently, I'm trying to set up a crontab job, but I'm getting the following message: /bin/sh: /usr/bin/vi: No such file or directory. I see that vi exists in /bin/vi,... (3 Replies)
Hi all,
below is the problem details:
ora10g@CNORACLE1>which ld
/usr/ucb/ld
ora10g@CNORACLE1>cd /usr/ccs/bin
ora10g@CNORACLE1>ln -s /usr/ucb/ld ld
ln: cannot create ld: File exists
ora10g@CNORACLE1>
how to link it to /usr/ccs/bin? (6 Replies)
Hi gentlemen.
For what intended is the directory /usr/local/bin? In this directory are some script.
I don't understand how these scripts being in this directory are started.
Each time after registration of the user occurs start of these scripts. These scripts start applications. (7 Replies)
Q1. I understand that /usr/local/bin means I can install/uninstall stuff in here and have any chance of messing up my original system files or effecting any other users. I created this directory myself.
But what about the directory I didn't create, namely /Users/m/bin? How is that directory... (1 Reply)
Hi Experts,
I found that the same commands(sort, du, df, find, grep etc.) exists in both dir.
What is the difference to use them?
i.e: to use xpg4/bin/grep and usr/bin/grep
My OS version is SunOS 5.10
Regards,
Saps (7 Replies)
Legends,
I am not able to set "expr" function in ksh script.
Below is the sample code i used, and output is as "Syntax error"
Please help me to come out of it.
OUTPUT (9 Replies)
Hi Guys,
OS:- Solaris 10 64Bit
I have a small query.
On one server a user is facing sed command issue.
He gets error regarding sed for this location
/users/hoy/2999/batch5/bin/internal.sh: /usr/local/bin/sed: not found
How ever the sed is actually present at this location on server:-... (13 Replies)
I'm not sure if this is the default behavior for the ld command, but it does not seem to be looking in /usr/local/lib for shared libraries.
I was trying to compile the latest version of Kanatest from svn. The autorgen.sh script seems to exit without too much trouble:
$ ./autogen.sh
checking... (2 Replies)
Hi Everyone,
We are trying to compile Kerberos library using xlc and we get an error that xlc is not found in the system.
We tried using gcc as well but it also fails with the same error. We could not find the compiler in the software media we received from IBM.
Any inputs on how... (2 Replies)
Discussion started by: madhav.kunapa
2 Replies
LEARN ABOUT DEBIAN
cvs-debuild
CVS-DEBUILD(1) General Commands Manual CVS-DEBUILD(1)NAME
cvs-debuild - build a Debian package using cvs-buildpackage and debuild
SYNOPSIS
cvs-debuild [debuild options] [cvs-buildpackage options] [--lintian-opts lintian options]
DESCRIPTION
cvs-debuild is a wrapper around cvs-buildpackage to run it with debuild as the package-building program. (This cannot simply be accom-
plished using the -C option of cvs-buildpackage, as it does not know how to handle all of the special debuild options.)
The program simply stashes the debuild and lintian options, and passes them to debuild when it is called by cvs-buildpackage. All of the
standard debuild options may be used (as listed below), but note that the root command specified by any --rootcmd or -r command-line option
will be passed as an option to cvs-buildpackage. The first non-debuild option detected will signal the start of the cvs-buildpackage
options.
The selection of the root command is slightly subtle: if there are any command-line options, these will be used. If not, then if cvs-
buildpackage is set up to use a default root command, that will be used. Finally, if neither of these are the case, then debuild will use
its procedures to determine an appropriate command, as described in its documentation.
See the manpages for debuild(1) and cvs-buildpackage for more information about the behaviour of each.
OPTIONS
The following are the debuild options recognised by cvs-debuild. All cvs-buildpackage and lintian options are simply passed to the appro-
priate program. For explanations of the meanings of these variables, see debuild(1).
--no-conf, --noconf
--rootcmd=gain-root-command, -rgain-root-command
--preserve-env
--preserve-envvar=var, -evar
--set-envvar=var=value, -evar=value
--lintian, --no-lintian
--ignore-dirname, --check-dirname
These should not be needed, but it is provided nevertheless.
SEE ALSO cvs-buildpackage(1), debuild(1), dpkg-buildpackage(1) and lintian(1).
AUTHOR
This program was written by Julian Gilbey <jdg@debian.org>.
DEBIAN Debian Utilities CVS-DEBUILD(1)