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)
Hi, I'm trying to run the module load command in a Makefile and i'm getting the following error:
make: module: command not found
Why is this? Is there any way to run this command in a Makefile?
NOTE: command - module load msjava/sunjdk/1.5.0 works fine outside of the Makefile (2 Replies)
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)
Greetings!
I'm fairly new to the unix world and I hope someone here can help me with my question. I'm using a Makefile to run a few programs and the final output is several .eps files. However I need them to be .pdf files, so I want to use epstopdf to convert the files.
Since I'm already... (6 Replies)
Hi All
I am creating a makefile and I want to do a clean section.
In the clean section I would like to check if the file exists and then delete it.
I always have an error 'unexpected end of file'
What's wrong in it?
Thanks
msntn
firstCpp: first.cpp
g++ -o first first.cpp
clean:
... (1 Reply)
Hi!
I've got a build process where scripts create multiple targets from their sources. But here I'm running into a conceptual problem of GNU make: If one has multiple targets in a dependency, make applies the rules once for every target that is out of sync - which is correct for normal... (3 Replies)
Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted!
1. The problem statement, all variables and given/known data:
Basically, the prompt is make a makefile with various sub makefiles in their respective subdirectories. All code... (1 Reply)
I have the following part of a makefile and want to simplify it
using rules rather than having to code the same two blocks
when I need ti build another program.
An having difficulty doing it
all: 1dvel2 1dvel 2dvel
... (8 Replies)
I am trying to create executables for the following files
Currently, I am making 9 different directories for for each. I would like to make 1 directory but everytime I try it does not work.
CROSS_COMPILE?=
# CROSS_COMPILE used to = arm-arago-linux-gnueabi... (1 Reply)
i don't know where to put this question hence it is here.
Presently, i have X unix machines which each of them running a set of executables with various unique configurations.
i would like to have run multiple set of machines the same set of executeables but each running different... (0 Replies)
Discussion started by: lchunleo
0 Replies
LEARN ABOUT DEBIAN
mm-config
MM-CONFIG(1) Shared Memory Library MM-CONFIG(1)NAME
mm-config - OSSP mm library configuration/build utility
VERSION
OSSP mm 1.4.1 (10-Aug-2006)
SYNOPSIS
mm-config [--help] [--version] [--cflags] [--ldflags] [--libs]
DESCRIPTION
The mm-config program is a little helper utility for easy configuring and building applications based on the mm(3) library. It can be used
to query the C compiler and linker flags which are required to correctly compile and link the application against the mm(3) library.
OPTIONS
mm-config accepts the following options:
--help
Prints the short usage information.
--version
Prints the version number and date of the installed mm(3) library.
--cflags
Prints the C compiler flags which are needed to compile the mm(3)-based application. The output is usually added to the "CFLAGS" vari-
able of the applications "Makefile".
--ldflags
Prints the linker flags ("-L") which are needed to link the application with the mm(3) library. The output is usually added to the
"LDFLAGS" variable of the applications "Makefile".
--libs
Prints the library flags ("-l") which are needed to link the application with the mm(3) library. The output is usually added to the
"LIBS" variable of the applications "Makefile".
EXAMPLE
CC=cc
CFLAGS=-O `mm-config --cflags`
LDFLAGS=`mm-config --ldflags`
LIBS=-lm `mm-config --libs`
all: foo
foo: foo.o
$(CC) $(LDFLAGS) -o foo foo.o $(LIBS)
foo.o: foo.c
$(CC) $(CFLAGS) -c foo.c
SEE ALSO mm(3).
AUTHOR
Ralf S. Engelschall
rse@engelschall.com
www.engelschall.com
10-Aug-2006 MM 1.4.1 MM-CONFIG(1)