01-24-2011
which version of make are you using on the two sun boxes ?
Also what version of O/S ? (Any patches installed that affect make ?)
10 More Discussions You Might Find Interesting
1. Solaris
Hi,
I am getting the following error while building on Solaris 64 , while I am trying to build.
Error Snippet :-
----------------------
Makefile:57: *** multiple target patterns. Stop.
make: Leaving directory `/work1/patch/vds6053sun64o/vobs/jvi'
make: *** Error 2
make: Leaving directory... (0 Replies)
Discussion started by: nileshborate
0 Replies
2. Shell Programming and Scripting
I've seen a few other threads like this, but they either went unanswered or failed to answer my question.
How do I set an environment variable in a Makefile?
What I'm trying to do is use GNU make to automate an ant build.
In order to run ant, I've got to first set a few environment... (1 Reply)
Discussion started by: Bags
1 Replies
3. HP-UX
I receive an error while installing Oracle 9i:
Error in invoking target install of makefile
/opt/oracle/product/9.2.0/sqlplus/lib/ins_sqlplus.mk
Furthermore:
$ whoami
oracle
$ echo $ORACLE_HOME
/opt/oracle/product/9.2.0
$ pwd
/opt/oracle/product/9.2.0/sqlplus/lib
$ ll
total... (5 Replies)
Discussion started by: chris2005
5 Replies
4. Shell Programming and Scripting
Hello,
I'm having a problem with a makefile script i'm trying to write.
I want to compile a C++ program in two possible ways: "make"
(default target, main) and "make debug". When i supply the debug
target, exactly the same as main should be built, but then with the
DEBUG flag (-g -D... (2 Replies)
Discussion started by: StevenR
2 Replies
5. Shell Programming and Scripting
Hi
I need to modify entire file starting from the 3 line. file looks like this
filename : exp
first line
second
1,"wes","est","ws"
1,"was","qwe","qwa"
also i have to replace the third content from 3 line by a counter . so the output should look like this:
first line
second... (12 Replies)
Discussion started by: ciba
12 Replies
6. Programming
Greetings!
Basically, I would like to properly handle this with gnu make:
alltools: my_tool mysecond_tool mythird_tool etc_tool
%_tool: dir1/%_tool.vf dir2/%_tool/subdir2/%_tool.ver
<tab>@echo done
%.vf:
<tab>RUN_VF $*
%.ver:
<tab>RUN_VER $*
So, if I were to do something like:... (0 Replies)
Discussion started by: Harlinator
0 Replies
7. Shell Programming and Scripting
Goal: I'm trying to create a PHONY target inside my Makefile so that when I run the command "make backup",
It will move all the files that end in "~" into the specified backup folder.
Here is my code currently, and I'll explain the problem after:
.PHONY: backup
backup:
@mkdir -p... (2 Replies)
Discussion started by: Xploit
2 Replies
8. Programming
I am writing a Makefile for Cobol on Linux.My sample Makefile looks like below.
I do not want to Hardcode Program names in Makefile.Is there any way we can mention directories in Target and Prerequisites instead of File names sothat Makefile Pickup all the files in mentioned path as below.... (8 Replies)
Discussion started by: kiranksb
8 Replies
9. Shell Programming and Scripting
Hi,
I need to use rsync to delete multiple files(only specified files not all) using --delete option, these files are located in different target folders.
Instead of running rsync command multiple times for each file, can we achieve this with one time execution?
your help is much... (0 Replies)
Discussion started by: MVEERA
0 Replies
10. Programming
I am trying to create a makefile to build a program and am getting the following error:
make -f tsimplex.mk
make: *** No rule to make target `/main/tsimplex_main.cpp', needed by `tsimplex_main.o'. Stop.
OPSYS = $(shell uname -s )
TARGET = tsimplex
ROOTDIR = ../../..
GTSDIR =... (1 Reply)
Discussion started by: kristinu
1 Replies
LEARN ABOUT DEBIAN
stg-sink
STG-SINK(1) StGit Manual STG-SINK(1)
NAME
stg-sink - Send patches deeper down the stack
SYNOPSIS
stg sink [-t <target patch>] [-n] [<patches>]
DESCRIPTION
This is the opposite operation of linkstg:float[]: move the specified patches down the stack. It is for example useful to group stable
patches near the bottom of the stack, where they are less likely to be impacted by the push of another patch, and from where they can be
more easily committed or pushed.
If no patch is specified on command-line, the current patch gets sunk. By default patches are sunk to the bottom of the stack, but the --to
option allows to place them under any applied patch.
Sinking internally involves popping all patches (or all patches including <target patch>), then pushing the patches to sink, and then
(unless --nopush is also given) pushing back into place the formerly-applied patches.
OPTIONS
-n, --nopush
Do not push back on the stack the formerly-applied patches. Only the patches to sink are pushed.
-t TARGET, --to TARGET
Specify a target patch to place the patches below, instead of sinking them to the bottom of the stack.
-k, --keep
Keep the local changes.
STGIT
Part of the StGit suite - see linkman:stg[1]
StGit 03/13/2012 STG-SINK(1)