Sponsored Content
Top Forums Programming Makefile No rule to make target Post 302887420 by Corona688 on Friday 7th of February 2014 11:20:30 AM
Old 02-07-2014
Your makefile has the rule tsimplex_main.o : $(MAINDIR)/tsimplex_main.cpp but tsimplex_main.cpp is either missing or not where the makefile expected it to be. make's usual reaction when it can't find a file is to try and create it, but it has no rule to make a .cpp file from scratch, so it quits.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

make and clean in a single rule in the makefile.

Hi, This stems from the following thread https://www.unix.com/showthread.php?t=18299 I have a makefile which makes either executables or a shared library. i.e. make -f unix.mak will create the executables and make -f unix.mak libolsv will create the shared library. Since these have to be... (4 Replies)
Discussion started by: vino
4 Replies

2. Solaris

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: Leaving directory `/work1/patch/vds6053sun64o/vobs/jvi' make: *** Error 2 make: Leaving directory... (0 Replies)
Discussion started by: nileshborate
0 Replies

3. Shell Programming and Scripting

Makefile debug target

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

4. Programming

Makefile: multiple target variable substitution

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

5. Shell Programming and Scripting

Makefile rule being skipped

I can't seem to get a rule in my Makefile to ever run... even if I change the rule to force make to re-enter the rule, or if I change the dependent files the rule depends on. Any ideas why the second rule is being ignored here? #MAKEFILES = $(DIRS:%=$(ROOT)/%/Makefile) #$(MAKEFILES):... (0 Replies)
Discussion started by: foureightyeast
0 Replies

6. Programming

compile fails in linux ... "No rule to make target" ... HELP

hello all, attached you can find a tool (written in C) that i really need to make it compile under linux i am able to compile and run it successfully in mac os x, but in linux the compilation fails the only thing that i did so far is to change the following #include <sys/malloc.h> to... (13 Replies)
Discussion started by: OneDreamCloser
13 Replies

7. Programming

Issue with make, no rule to make target etc.

I have been trying to split up my src directory to clear out files that are not re-compiled very often. Now I have the following setup in my trunk, trunk/bld trunk/src/ trunk/src/src_server trunk/makefile.linux In the make file, I have compile rules SOURCELOC = src # compile src c++... (4 Replies)
Discussion started by: LMHmedchem
4 Replies

8. Shell Programming and Scripting

MakeFile Backup Target

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

9. UNIX for Dummies Questions & Answers

Defining a new suffix rule in a Makefile

Hi everybody, I have a Makefile where a single suffix rule is defined: .SUFFIXES: .cpp .cpp.o: ${CXX} ${CXXFLAGS} -c -o $@ $< And I'd like to create another where an additional flag is added to compile in SMP. Right now, I have to do it like this: interface-smp.o:... (2 Replies)
Discussion started by: Zel2008
2 Replies

10. Shell Programming and Scripting

Default rule to be executed in makefile

Hi all, I want to know the entry point (default rule to be executed) in a makefile once all defined variables are evaluated. I do not have all: in my makefile and I give "make" without any parameter in command line. thanks........ (3 Replies)
Discussion started by: useless79
3 Replies
Makefile::AST::Evaluator(3pm)				User Contributed Perl Documentation			     Makefile::AST::Evaluator(3pm)

NAME
Makefile::AST::Evaluator - Evaluator and runtime for Makefile::AST instances SYNOPSIS
use Makefile::AST::Evaluator; $Makefile::AST::Evaluator::JustPrint = 0; $Makefile::AST::Evaluator::Quiet = 1; $Makefile::AST::Evaluator::IgnoreErrors = 1; $Makefile::AST::Evaluator::AlwaysMake = 1; $Makefile::AST::Evaluator::Question = 1; # $ast is a Makefile::AST instance: my $eval = Makefile::AST::Evaluator->new($ast); Makefile::AST::Evaluator->add_trigger( firing_rule => sub { my ($self, $rule, $ast_cmds) = @_; my $target = $rule->target; my $colon = $rule->colon; my @normal_prereqs = @{ $rule->normal_prereqs }; # ... } ); $eval->set_required_target($user_makefile) $eval->make($goal); DESCRIPTION
This module implementes an evaluator or a runtime for makefile ASTs represented by Makefile::AST instances. It "executes" the specified GNU make AST by the GNU makefile semantics. Note that, "execution" not necessarily mean building a project tree by firing makefile rule commands. Actually you can defining your own triggers by calling the add_trigger method. (See the "SYNOPSIS" for examples.) In other words, you can do more interesting things like plotting the call path tree of a Makefile using Graphviz, or translating the original makefile to another form (like what the makesimple script does). It's worth mentioning that, most of the construction algorithm for topological graph s (including implicit rule application) have already been implemented in Makefile::AST and its child node classes. CONFIGURE VARIABLES
This module provides several package variables (i.e. static class variables) for controlling the behavior of the evaluator. Particularly the user needs to set the $AlwaysMake variable to true and $Question to true, if she wants to use the evaluator to do special tasks like plotting dependency graphs and translating GNU makefiles to other format. Setting $AlwaysMake to true will force the evaluator to ignore the timestamps of external files appeared in the makefiles while setting $Question to true will prevent the evaluator from executing the shell commands specified in the makefile rules. Here's the detailed listing for all the config variables: $Question This variable corresponds to the command-line option "-q" or <--question> in GNU make. Its purpose is to make the evaluator enter the "questioning mode", i.e., a mode in which "make" will never try executing rule commands unless it has to, "and" echoing is suppressed at the same time. $AlwaysMake This variable corresponds to the command-line option "-B" or "--always-make". It forces re-constructing all the rule's targets related to the goal, ignoring the timestamp or existence of targets' dependencies. $Quiet It corresponds to GNU make's command-line option "-s", "--silent", or "--quiet". Its effect is to cancel the echoing of shell commands being executed. $JustPrint This variable corresponds to GNU make's command line option "-n", "--just-print", "--dry-run", or "--recon". Its effect is to print out the shell commands requiring execution but without actually executing them. $IgnoreErrors This variable corresponds to GNU make's command line option "-i" or "--ignore-errors"ieXXIt's used to ignore the errors of shell commands being executed during the make process. The default behavior is quitting as soon as a shell command without the "-" modifier fails. CLASS TRIGGERS
The "make_by_rule" method of this class defines a trigger named "firing_rule" via the Class::Trait module. Everytime the "make_by_rule" method reaches the trigger point, it will invoke the user's processing handler with the following three arguments: the self object, the Makefile::AST::Rule object, and the corresponding "Makefile::AST::Command" object in the context. By registering his own processing handlers for the "firing_rule" trigger, the user's code can reuse the evaluator to do his own cool things without traversing the makefile ASTs himself. See the "SYNOPSIS" for code examples. CODE REPOSITORY
For the very latest version of this script, check out the source from http://github.com/agentzh/makefile-parser-pm <http://github.com/agentzh/makefile-parser-pm>. There is anonymous access to all. AUTHOR
Zhang "agentzh" Yichun "<agentzh@gmail.com>" COPYRIGHT AND LICENSE
Copyright (c) 2007-2008 by Zhang "agentzh" Yichun (agentzh). This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself. SEE ALSO
Makefile::AST, Makefile::Parser::GmakeDB, pgmake-db, makesimple, Makefile::DOM. perl v5.12.4 2011-08-17 Makefile::AST::Evaluator(3pm)
All times are GMT -4. The time now is 11:02 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy