04-17-2008
compilation error
hello everyone,
here i am attempting to compile a c++ submodule.OS is HP-UX.
here i am getting the following error.
======================================
"Make: Don't know how to make compile. Stop."
===================================
could you pls somebody suggest why this error is causing.
I suppose this is a common error.it's very urgent.
with regards,
SM
10 More Discussions You Might Find Interesting
1. Programming
Hi All,
I facing the following compilation error; when I implementing the following logic.
ostrstream ostr;
ostr << (( scAxsm.getRecord( i ).getField( 2 ).getShort())%12)!=0?(( scAxsm.getRecord( i ).getField( 2 ).getShort())/12+1)
: (( scAxsm.getRecord( i ).getField( 2 ).getShort())/12) <<... (1 Reply)
Discussion started by: sweta
1 Replies
2. Programming
Hi,
While trying compile a C++ file in UNIX with gcc whose make rule involves the usage of
/usr/ccs/bin/as, I get the following error:
/usr/ccs/bin/as: No such file or directory
/usr/ccs/bin/as: error: write error on output file "<filename>.o"
*** Error code 1
clearmake: Error: Build... (2 Replies)
Discussion started by: smanu
2 Replies
3. Programming
I am compiling a software xchm on solaris 10.
First i run './configure'
There is no error.
But when i start compiling using 'gmake'
following error shown
/usr/local/include/wx-2.6/wx/x11/brush.h: In copy constructor `wxBrush::wxBrush(const wxBrush&)':... (3 Replies)
Discussion started by: mansoorulhaq
3 Replies
4. Solaris
Hi All,
while building, i am receiving the following error......
Undefined first referenced
symbol in file
void os_directory::create(const std::string &) obj.release/BOConfig.o (symbol belongs to implicit dependency... (2 Replies)
Discussion started by: vinod_kumar_k
2 Replies
5. Linux
Hello every one,
here i am attempting to compile a c++ module using gcc.it is throwing a error .
error:
====
> make -S dummyCHARGP
/usr/local/bin/gcc -g -DDEBUG -DMAT -I. -I/swtemp/usbs/cc/unix-ce/root/subsys/lib/Linux/ -I/opt/dce/include -I/opt/dce/include/dce ... (12 Replies)
Discussion started by: mannam srinivas
12 Replies
6. UNIX for Dummies Questions & Answers
state_field state_abvr = {
"AL","ALABAMA",
"AK","ALASKA",
"AZ","ARIZONA",
"AR","ARKANSAS",
"CA","CALIFORNIA",
"CO","COLORADO",
"CT","CONNECTICUT",
"DE","DELAWARE",
"DC","DISTRICT-OF-COLUMBIA",
"FL","FLORIDA",
"GA","GEORGIA",
"HI","HAWAII",
"ID","IDAHO",
"IL","ILLINOIS",... (1 Reply)
Discussion started by: jagan_kalluri
1 Replies
7. Programming
state_field state_abvr = {
"AL","ALABAMA",
"AK","ALASKA",
"AZ","ARIZONA",
"AR","ARKANSAS",
"CA","CALIFORNIA",
"CO","COLORADO",
"CT","CONNECTICUT",
"DE","DELAWARE",
"DC","DISTRICT-OF-COLUMBIA",
"FL","FLORIDA",
"GA","GEORGIA",
"HI","HAWAII",
"ID","IDAHO",
"IL","ILLINOIS",... (1 Reply)
Discussion started by: jagan_kalluri
1 Replies
8. Programming
Hi,
Recently our codes have been migrated to new server, whenever we compile any pro*c programs we receive the following
errorl. please help
>> make -f lib_util.mk all
CC= ucbcc 4Compiling lib_util
### command line files and options (expanded):
### -xO3 -DNULL=0 -v -o lib_util.o... (0 Replies)
Discussion started by: satvd
0 Replies
9. Shell Programming and Scripting
Hi,
Recently our codes have been migrated to new server, whenever we compile any pro*c programs we receive the following
errorl. please help
>> make -f lib_util.mk all
CC= ucbcc 4Compiling lib_util
### command line files and options (expanded):
### -xO3 -DNULL=0 -v -o lib_util.o... (1 Reply)
Discussion started by: satvd
1 Replies
10. Programming
I am getting the below given errors for the following program though all the variables have been declared and used appropriately. Please Help. The environment is AIX.
Error:
------
"gbsizeprofile.c", line 67.4: 1506-275 (S) Unexpected text 'void' encountered.
"gbsizeprofile.c", line 67.10:... (2 Replies)
Discussion started by: yschd
2 Replies
LEARN ABOUT CENTOS
gitmodules
GITMODULES(5) Git Manual GITMODULES(5)
NAME
gitmodules - defining submodule properties
SYNOPSIS
$GIT_WORK_DIR/.gitmodules
DESCRIPTION
The .gitmodules file, located in the top-level directory of a Git working tree, is a text file with a syntax matching the requirements of
git-config(1).
The file contains one subsection per submodule, and the subsection value is the name of the submodule. The name is set to the path where
the submodule has been added unless it was customized with the --name option of git submodule add. Each submodule section also contains the
following required keys:
submodule.<name>.path
Defines the path, relative to the top-level directory of the Git working tree, where the submodule is expected to be checked out. The
path name must not end with a /. All submodule paths must be unique within the .gitmodules file.
submodule.<name>.url
Defines a URL from which the submodule repository can be cloned. This may be either an absolute URL ready to be passed to git-clone(1)
or (if it begins with ./ or ../) a location relative to the superproject's origin repository.
submodule.<name>.update
Defines what to do when the submodule is updated by the superproject. If checkout (the default), the new commit specified in the
superproject will be checked out in the submodule on a detached HEAD. If rebase, the current branch of the submodule will be rebased
onto the commit specified in the superproject. If merge, the commit specified in the superproject will be merged into the current
branch in the submodule. If none, the submodule with name $name will not be updated by default.
This config option is overridden if 'git submodule update' is given
the '--merge', '--rebase' or '--checkout' options.
submodule.<name>.branch
A remote branch name for tracking updates in the upstream submodule. If the option is not specified, it defaults to master. See the
--remote documentation in git-submodule(1) for details.
submodule.<name>.fetchRecurseSubmodules
This option can be used to control recursive fetching of this submodule. If this option is also present in the submodules entry in
.git/config of the superproject, the setting there will override the one found in .gitmodules. Both settings can be overridden on the
command line by using the "--[no-]recurse-submodules" option to "git fetch" and "git pull".
submodule.<name>.ignore
Defines under what circumstances "git status" and the diff family show a submodule as modified. When set to "all", it will never be
considered modified, "dirty" will ignore all changes to the submodules work tree and takes only differences between the HEAD of the
submodule and the commit recorded in the superproject into account. "untracked" will additionally let submodules with modified tracked
files in their work tree show up. Using "none" (the default when this option is not set) also shows submodules that have untracked
files in their work tree as changed. If this option is also present in the submodules entry in .git/config of the superproject, the
setting there will override the one found in .gitmodules. Both settings can be overridden on the command line by using the
"--ignore-submodule" option.
EXAMPLES
Consider the following .gitmodules file:
[submodule "libfoo"]
path = include/foo
url = git://foo.com/git/lib.git
[submodule "libbar"]
path = include/bar
url = git://bar.com/git/lib.git
This defines two submodules, libfoo and libbar. These are expected to be checked out in the paths include/foo and include/bar, and for both
submodules a URL is specified which can be used for cloning the submodules.
SEE ALSO
git-submodule(1) git-config(1)
GIT
Part of the git(1) suite
Git 1.8.3.1 06/10/2014 GITMODULES(5)