Sponsored Content
Full Discussion: gmake
Top Forums UNIX for Dummies Questions & Answers gmake Post 4557 by mib on Thursday 26th of July 2001 10:06:25 AM
Old 07-26-2001
"gmake" is the FSF's implementation of "make. GNU Make has many powerful macro features for use in makefiles, beyond what other Make versions have.

I thinK the very reason for using GNU make may be, the source of GNU make is available to be built on any platform, and GNU make is highly portable. It runs on DOS, Windows, Amiga, and VMS in addition to the normal UNIX platforms. To have a highly portable build environment its best to write your makefiles using gmake.

You can view gmake's features in its documentation:

info -f make -n Features


HTH
 

10 More Discussions You Might Find Interesting

1. AIX

Where i can find gmake software for AIX 5.2

Where i can find gmake software for AIX 5.2 Thanks Bala (1 Reply)
Discussion started by: Balamurugan
1 Replies

2. AIX

gmake For AIX 5.3

hello everybody i will be very thankful if someone tells me where i can find the gmake for AIX 5.3 (2 Replies)
Discussion started by: eternalflame
2 Replies

3. UNIX for Advanced & Expert Users

CPAM_TWW -gmake utilities

Hi CPAM-TWW, We need to know Whether CPAM-TWW ( cross platform application Management) package comes along With HP-UX11i . if so , Please get Which package needs to be triggered during installation ( We are more intrested on TWWgmake and TWWutilites( 3rd party software The Written Word)) ... (0 Replies)
Discussion started by: vasanthan
0 Replies

4. Programming

what is the distinguish between gmake and make?

I am working on solaris 9. and use gmake to compile and linke c/c++ program. anybody can tell me the distinguish between gmake and make? :confused: (10 Replies)
Discussion started by: robin.zhu
10 Replies

5. Programming

after gmake size of library gets changes

Hello, I have source code of c. When i compiled it using gmake my library gets created on AIX. But without changing the source code, if i try to do gmake each and every time then every time size of created library gets changed. Can anyone tell me why it's happening? Am i missing something in my... (3 Replies)
Discussion started by: mustus
3 Replies

6. Programming

GMAKE error returns - What does that mean ?

I am using xmake which I guess calls gmake which ... whatever. I get an error in my compiling and want to know what the error number means. For example, the message might be "Error 139". Rather then post the exact code fragment and exact output, I want to find the a list of error codes and... (1 Reply)
Discussion started by: intcwrtr
1 Replies

7. UNIX for Dummies Questions & Answers

gmake on Mac

I am using my teminal on Mac to run some files with gmake, (I used unix before,but now I am trying to run it frm my mac) and I get the error message: -bash: gmake: command not found Any idea what the problem might be? Thanks! (10 Replies)
Discussion started by: cosmologist
10 Replies

8. Programming

Make and gmake issues

Hello I am working on a CPP code written for SUN CC 5.5 and make we used make to compile the code then it compilation went smooth now i am using gmake: I have a make file like this WSROOT=.. include $(WSROOT)/etc/wsmkinclude.common all: @for subdir in */Makefile; \ do \... (1 Reply)
Discussion started by: Revathi R
1 Replies

9. Solaris

Make and gmake issues

Hello I am working on a CPP code written for SUN CC 5.5 and make we used make to compile the code then it compilation went smooth now i am using gmake: I have a make file like this WSROOT=.. include $(WSROOT)/etc/wsmkinclude.common all: @for subdir in */Makefile; \ do \... (1 Reply)
Discussion started by: Revathi R
1 Replies

10. UNIX for Dummies Questions & Answers

Gmake

hi with regard that i am new with linux , i don't have any information about GNU make? is it a part of linux or it must be installed in linux separately? thanks in advance for you attention best regard fereshte (1 Reply)
Discussion started by: komijani
1 Replies
REMAKE(1)							LOCAL USER COMMANDS							 REMAKE(1)

NAME
remake - A patched GNU make with a debuger, better tracing and error reporting SYNOPSIS
remake [ -f makefile ] [ options ] ... [ targets ] ... WARNING
This man page is an extract of the documentation of GNU remake ( make + debugger). It is updated only occasionally, because the GNU project does not use nroff. For complete, current documentation, refer to the Info file make.info and mdb.info which are made from the Texinfo source files make.texi. and mdb.texi The latter describes debugger behavior. DESCRIPTION
The purpose of the make utility is to determine automatically which pieces of a large program need to be recompiled, and issue the commands to recompile them. See documentation on GNU make for more information. However in this patched version we add a debugger which can be entered either initially (option -X or --debugger) or on an error (--debug- ger=error). We also add better tracing facilities (option -x) and we report postion information better. When an error is encountered more information is given automatically. See also the home <http://bashdb.sf.net/remake> page for more information. OPTIONS
-b, -m These options are ignored for compatibility with other versions of make. -B, --always-make Unconditionally make all targets. -C dir, --directory=dir Change to directory dir before reading the makefiles or doing anything else. If multiple -C options are specified, each is inter- preted relative to the previous one: -C / -C etc is equivalent to -C /etc. This is typically used with recursive invocations of make. -d Print debugging information in addition to normal processing. The debugging information says which files are being considered for remaking, which file-times are being compared and with what results, which files actually need to be remade, which implicit rules are considered and which are applied---everything interesting about how make decides what to do. --debug[=FLAGS] Print debugging information in addition to normal processing. If the FLAGS are omitted, then the behavior is the same as if -d was specified. FLAGS may be a for all debugging output (same as using -d), b for basic debugging, v for more verbose basic debugging, i for showing implicit rules, j for details on invocation of commands, and m for debugging while remaking makefiles. --debugger[=FLAGS] Enter the debugger. If the FLAGS are omitted, then the behavior is the same as if --debugger=full was specified. FLAGS may be a for all debugging output (same as using -d), error the debugger is only entered on encountering an error. It may be possible to quit the debugger and continue processing. So the overall effect could be like the " --keep-going" switch. fatal the debugger is only entered on encountering a fatal error. preread the debugger is entered after command-line options are parsed but before andy Makefiles have been read. It also sets step-tracing mode. preaction Enters the debugger after command-line options are parsed and after Makefiles have been read, but before any action is performed. It also sets step-tracing mode. full for basic debugging, -e, --environment-overrides Give variables taken from the environment precedence over variables from makefiles. +-f file, --file=file, --makefile=FILE Use file as a makefile. -i, --ignore-errors Ignore all errors in commands executed to remake files. -I dir, --include-dir=dir Specifies a directory dir to search for included makefiles. If several -I options are used to specify several directories, the direc- tories are searched in the order specified. Unlike the arguments to other flags of make, directories given with -I flags may come directly after the flag: -Idir is allowed, as well as -I dir. This syntax is allowed for compatibility with the C preprocessor's -I flag. -j [jobs], --jobs[=jobs] Specifies the number of jobs (commands) to run simultaneously. If there is more than one -j option, the last one is effective. If the -j option is given without an argument, remake will not limit the number of jobs that can run simultaneously. -k, --keep-going Continue as much as possible after an error. While the target that failed, and those that depend on it, cannot be remade, the other dependencies of these targets can be processed all the same. -l [load], --load-average[=load] Specifies that no new jobs (commands) should be started if there are others jobs running and the load average is at least load (a floating-point number). With no argument, removes a previous load limit. -L, --check-symlink-times Use the latest mtime between symlinks and target. -n, --just-print, --dry-run, --recon Print the commands that would be executed, but do not execute them. -o file, --old-file=file, --assume-old=file Do not remake the file file even if it is older than its dependencies, and do not remake anything on account of changes in file. Essentially the file is treated as very old and its rules are ignored. -p, --print-data-base Print the data base (rules and variable values) that results from reading the makefiles; then execute as usual or as otherwise speci- fied. This also prints the version information given by the -v switch (see below). To print the data base without trying to remake any files, use remake -p -f/dev/null. -q, --question ``Question mode''. Do not run any commands, or print anything; just return an exit status that is zero if the specified targets are already up to date, nonzero otherwise. -r, --no-builtin-rules Eliminate use of the built-in implicit rules. Also clear out the default list of suffixes for suffix rules. -R, --no-builtin-variables Don't define any built-in variables. -s, --silent, --quiet Silent operation; do not print the commands as they are executed. -S, --no-keep-going, --stop Cancel the effect of the -k option. This is never necessary except in a recursive make where -k might be inherited from the top-level make via MAKEFLAGS or if you set -k in MAKEFLAGS in your environment. -t, --touch Touch files (mark them up to date without really changing them) instead of running their commands. This is used to pretend that the commands were done, in order to fool future invocations of remake. -v, --version Print the version of the make program plus a copyright, a list of authors and a notice that there is no warranty. -w, --print-directory Print a message containing the working directory before and after other processing. This may be useful for tracking down errors from complicated nests of recursive make commands. --no-print-directory Turn off -w, even if it was turned on implicitly. -W file, --what-if=file, --new-file=file, --assume-new=file Pretend that the target file has just been modified. When used with the -n flag, this shows you what would happen if you were to mod- ify that file. Without -n, it is almost the same as running a touch command on the given file before running make, except that the modification time is changed only in the imagination of make. -x, --trace [=FLAGS] Sets up execution tracing. If FLAGS are omitted, then the behavior is the same as if " --trace=full" was specified. full normal trac- ing read show in addition status on reading in makefiles full the most verbose tracing. --warn-undefined-variables Warn when an undefined variable is referenced. EXIT STATUS
GNU remake exits with a status of zero if all makefiles were successfully parsed and no targets that were built failed. A status of one will be returned if the -q flag was used and make determines that a target needs to be rebuilt. A status of two will be returned if any errors were encountered. An exit status of 77 can be given when quitting from the debugger out of a recursive invocation. SEE ALSO
The GNU Remake Manual and the The GNU Remake Debugger Manual BUGS
See the chapter `Problems and Bugs' in The GNU Remake Manual. AUTHOR
This manual page contributed by Dennis Morse of Stanford University. It has been reworked by Roland McGrath. Further updates contributed by Mike Frysinger and Rocky Bernstein. GNU
25 February 2007 REMAKE(1)
All times are GMT -4. The time now is 11:31 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy