hello!
i want to create a Makefile on the freebsd 4.5,so i vi the hello.c
#include
int main(int argc, char** argv)
{
printf(''Hello, GNU!\n'');
return 0;
}
#autoscan
#cp configure.scan configure.in
#vi configure.in
modify:AC_OUTPUT AC_OUTPUT(Makefile)
#aclocal
#autoconf... (0 Replies)
All,
I am facing problem with one makefile compilation. The following is the error I am getting
<Code>
/applns/ora10/rdbms/bin/proc sqlcheck=semantics userid=/ CHAR_MAP=VARCHAR2 DBMS=V7 DEFINE=UNIX DEFINE=SUN_SRC_COMPAT iname=mm5900.pc
sh: /applns/ora10/rdbms/bin/proc: not found
*** Error... (1 Reply)
All,
I am facing problem with one makefile compilation. The following is the error I am getting, Before proceeding to this I want to let you know all, only last week onwards I started working in solaris10, the same code is working in solaris 9. I dont know any link has to be created, or any path... (3 Replies)
Hi all,
I am trying to create an executable, but when the .pc file converting to .c file I am getting lots of warning message like
of these 3 lines.
Any idea why I am getting these lines?
Any configuration issues?
What exactly needs to be done to solve these warning messages?
... (0 Replies)
Hi ,
Please answer my query:
I want to create a common make file for one of mylibrary such that it should work on both Sun as well as Linux on 32 and 64 bit system.
The flow is sth like this:
..............
..............
if$(OS) == solaris
BINDIR= ../../lib/solaris/64
else
BINDIR=... (1 Reply)
Now I am using the HP-UX11.11 version.
The scripts are runninh in KSH shell.
While I wan to call one executable of any Pro*C file, I have got the following error, however the executable is running fine directly.
testpri Started at 10.05.200923:40
/usr/lib/dld.sl: Bad magic number for... (0 Replies)
Hello everybody,
I'm unable to make my shell script an executable file.
The details are as follows:
PATH includes my $HOME/bin i.e. /rchome/rc1/bin
HOME directory is /rchome/rc1
script name is prep_mig.sh permissions set are 755
It's executing if I give below command
sh prep_mig.sh
but... (4 Replies)
Can anyone give me a makefile that creates 3 exe?for example, let's suppose i have the following files:
blah1.c
blah1.h
blah2.c
blah2.h
blah3.c
blah3.h
i've searched and searched but so far i was not able to complete it. (4 Replies)
Hey there,
This is gotta be a stupid question, if there ever was one, but I am learning a lot by asking such questions.
Now I am trying to build this humungous library, which has all kinds a dependencies, which I realize as it makes, and i download all those dependent libs.
The compilation is... (1 Reply)
Hello experts,
I would like to know if is possible to create a default acl rule to a directory.
in this directory all files created should have executable permissions by the group IT.
i tried setfacl -m d:g:it:rwx /files
tried to change the mask setfacl -m m::rwx /files
but i still... (3 Replies)
Discussion started by: berveglieri
3 Replies
LEARN ABOUT MOJAVE
shape_stdrul
SHAPE_STDRUL(7) Miscellaneous Information Manual SHAPE_STDRUL(7)NAME
shape stdrul - shapeTools RMS general version selection rules
DESCRIPTION
The shape release management system requires a set of standard version selection rules to be accessible project wide. These are defined in
the stdrules file, which is to be included into the Shapefiles of any part of the system controlled by the shapeTools release management
system. Version selection rules drive the binding of component names in the Shapefile to specific versions during a build or release
process (or better: any process performed by invocation of shape(1) ). Some functions of shape_RMS allow definition of the version binding
rule being active by defining the VERSIONS macro on the command line. This may be set to any of the rule names listed below.
If you want to introduce new version selection rules for project wide use, you may add them to the stdrules file. You should be very care-
ful, when altering this file. Do not remove any of the rules defined in the original version of stdrules (as it comes from the shapeTools
distribution tape) because these are essential for the release management system. When altering one of the original selection rules, you
should be very concious of what you are doing, as you may affect the operationality of shape RMS. For a description of the syntax of rule
definitions, see the shape(1) manual.
The standard version selection rules are:
most_recent
For each component select a busy version if available, the most recent saved version otherwise.
last_proposed
Use the last proposed version of each component. This rule fails, if no proposed version is available
last_released
Select versions from the last generated release.
last_prereleased
Select versions from the last generated prerelease.
recent_release
Select versions included in the last release or prerelease, whichever is newer.
from_release
Select versions from a specific release or prerelease. When using this rule the value of the macro RELEASENAME has to be set to
the name of the desired (pre)release.
extern Always select a busy version (a regular UNIX file). This rule should be applied to all extern components that are not under con-
trol of the shapeTools version control system.
FILES
$(SHAPELIBPATH)/stdrules
SEE ALSO shape_RMS(1), shape(1)21.8.119SHAPE_STDRUL(7)