09-20-2005
Makefile:57: *** multiple target patterns. Stop.
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[2]: Leaving directory `/work1/patch/vds6053sun64o/vobs/jvi'
make[1]: *** [/work1/patch/vds6053sun64o/build_area/jvi/6.0.5/SunOS_64bit/opt/classes//last_javac_time_1] Error 2
make[1]: Leaving directory `/work1/patch/vds6053sun64o/vobs/jvi'
make: *** [jvi_install] Error 2
----------------------
Intrestingly there is a variable in the Make file. When I hardcode it the error vanishes.
Any clues ?
Thanks,
Nilesh
Last edited by nileshborate; 09-20-2005 at 11:24 AM..
Reason: Posting Icon
10 More Discussions You Might Find Interesting
1. 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
2. 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
3. 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
4. Shell Programming and Scripting
I'm trying to parse COBOL code to combine variables into one string. I have two variable names that get literals moved into them and I'd like to use sed, awk, or similar to find these lines and combine the variables into the final component. These variable names are always VAR1 and VAR2. For... (8 Replies)
Discussion started by: wilg0005
8 Replies
5. Solaris
Hi,
I have a small piece of Makefile script which throw's error on Sun Sparc machine, but works fine with Sun Optron, Linux, AIX machines.
FOO=Naveen
test1:FOO=Dhilip
test1:
@echo FOO is ${FOO}
test2:
@echo Me is ${FOO}
Output on Sun Sparc -
ukhml-v890new-~/test: make test1... (5 Replies)
Discussion started by: nsriram
5 Replies
6. 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
7. 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
8. Programming
Hi there,
I am new to programming on unix and have been handed a legacy system. THe makefile is relatively complicated but i have moslyt figured it out.
One issue i cannot figure out is the fact that i now need to create a second output exe. (ie multiple LIRARY_TARGETS with one makefile.)
can... (2 Replies)
Discussion started by: anthony.x.moss@
2 Replies
9. Shell Programming and Scripting
Hi,
I want to grep multiple patterns from multiple files and save to multiple outputs. As of now its outputting all to the same file when I use this command.
Input : 108 files to check for 390 patterns to check for. output I need to 108 files with the searched patterns.
Xargs -I {} grep... (3 Replies)
Discussion started by: Diya123
3 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 XFREE86
dh_auto_install
DH_AUTO_INSTALL(1) Debhelper DH_AUTO_INSTALL(1)
NAME
dh_auto_install - automatically runs make install or similar
SYNOPSIS
dh_auto_install [buildsystemoptions] [debhelperoptions] [--params]
DESCRIPTION
dh_auto_install is a debhelper program that tries to automatically install built files. It does so by running the appropriate command for
the build system it detects the package uses. For example, if there's a Makefile and it contains a install target, then this is done by
running make (or MAKE, if the environment variable is set). If there is a setup.py or Build.PL, it is used. Note that the Ant build system
does not support installation, so dh_auto_install will not install files built using Ant.
Unless --destdir option is specified, the files are installed into debian/package/ if there is only one binary package. In the multiple
binary package case, the files are instead installed into debian/tmp/, and should be moved from there to the appropriate package build
directory using dh_install(1).
DESTDIR is used to tell make where to install the files. If the Makefile was generated by MakeMaker from a Makefile.PL, it will
automatically set PREFIX=/usr too, since such Makefiles need that.
This is intended to work for about 90% of packages. If it doesn't work, or tries to use the wrong install target, you're encouraged to skip
using dh_auto_install at all, and just run make install manually.
OPTIONS
See "BUILD SYSTEM OPTIONS" in debhelper(7) for a list of common build system selection and control options.
--destdir=directory
Install files into the specified directory. If this option is not specified, destination directory is determined automatically as
described in the "DESCRIPTION" section.
-- params
Pass params to the program that is run, after the parameters that dh_auto_install usually passes.
SEE ALSO
debhelper(7)
This program is a part of debhelper.
AUTHOR
Joey Hess <joeyh@debian.org>
11.1.6ubuntu2 2018-05-10 DH_AUTO_INSTALL(1)