Sponsored Content
Operating Systems AIX Not picking up the GNU version of make Post 302515965 by Celtic_Monkey on Thursday 21st of April 2011 08:57:38 AM
Old 04-21-2011
those *make files look to be the same to me.

what says:

# gmake --version
# make --version
 

10 More Discussions You Might Find Interesting

1. UNIX Desktop Questions & Answers

checking of GNU C Complier version

Hi, How do i check the GNU C Complier my system is running? thanks jennifer (2 Replies)
Discussion started by: jennifer
2 Replies

2. UNIX for Advanced & Expert Users

Problems with gnu make

I am running a make file through the gnu make tool and i am getting the following error jsh1035c:/users/egate453/admegate/kapil/samples $ make -f GNUmakefile queue_c make -f ./GNUmakefile queue_c in_objdir=1 build_root=/users/egate453/admegate/kapil/samples make: Entering directory... (2 Replies)
Discussion started by: handak9
2 Replies

3. UNIX for Advanced & Expert Users

GNU's make error codes - list

Hi, I often encounter make errors. Many a times, a corresponding error code is also shown, like make: Error 56 (ignored) make: Error 91 (ignored) make: Error 96 (ignored) et al. I tried google'ing as well as searching this forum for what these error codes mean. I know, make... (1 Reply)
Discussion started by: vino
1 Replies

4. UNIX for Dummies Questions & Answers

What's the difference between PMake and GNU Make?

My system is ubuntu, can I use PMake ? (0 Replies)
Discussion started by: meili100
0 Replies

5. Programming

Detecting host OS in Gnu make

Is this possible? Right now I'm developing some code for Linux, Windows and OS X. To build on each of the systems I've currently got separate build targets for each platform. Ideally I'd like to set up a single make rule that can detect the appropriate target and build it. I know this is... (2 Replies)
Discussion started by: G_Morgan
2 Replies

6. SCO

GNU cpp and make on SCO

Installed GNU make and the GNU C/C++ compiler on SCO Openserver 5.0.7 recently. Only a normal user is able to run make and compile programs - root is not able to. Under root, make do run, but root can't access the compiler at all, even tho I set root's path to point to the compiler.... (0 Replies)
Discussion started by: The_Librarian
0 Replies

7. Shell Programming and Scripting

GNU make doesn't pick up changes

It's been a while since I had to write a Makefile, but I've managed to clobber this together: SRC=module1.c module2.c OBJS=$(SRC:%.c=%.o) HDR=include1.h include2.h CC=gcc CFLAGS=-Wall -ggdb -D_XOPEN_SOURCE -I. -ansi all: program program: $(OBJS) $(CC) $(CFLAGS) -o $@ $(OBJS) ... (3 Replies)
Discussion started by: pludi
3 Replies

8. Shell Programming and Scripting

extension building make GNU Linux

Hi, I do "touch poub.mlc" Download my Makefile, But when I try : make -f Makefile.txt(.txt in order my file to be accepted for upload), it says:"no rule for poub.mlo target" What is wrong in my Makefile(test yourself please before posting)? (1 Reply)
Discussion started by: synhedionn
1 Replies

9. Shell Programming and Scripting

Backward compatibility issue with GNU bash, version 4.3.42(5)

Hi, I have made a snake game on below bash version. But it is not backward compatible. Can someone suggest a version which is most commonly used and is backward compatible so that i can change my code and share again? I have attached the game script. If someone can run it please also suggest... (5 Replies)
Discussion started by: amit14august
5 Replies

10. Programming

Gnu make: default values and conditionals

I need some help. I use variables and conditionals to build with or without specic libraries. I set USEAL ?= 1 # get value from cmd, defaults to 1 (see comment) the conditional is: ifeq ($(USEAL),1) LIBS = <any libs> else LIBS = endif Its amazing that this works when invoked... (4 Replies)
Discussion started by: dodona
4 Replies
install(1)						      General Commands Manual							install(1)

NAME
install - Installs a command SYNOPSIS
install [-sS] [-c targetdir] [-g group] [-m mode] [-u owner] file [searchdir...] install [-osS] [-f targetdir] [-g group] [-m mode] [-u owner] file [searchdir...] install [-g group] [-iosS] [-m mode] [-n targetdir] [-u owner] file [searchdir...] install [-g group] [-MosS] [-m mode] [-u owner] file [searchdir...] The install command installs file in a specific place within a file system. It is most often used in makefiles. OPTIONS
Installs file in targetdir only if there is not already a copy there. If there is a copy of file in targetdir, the command issues a mes- sage to that effect and exits without overwriting the file. This option can be used alone or with the -g, -m, -s, -S, or -u options. Forces installation of file in targetdir even if a copy already exists there. If there is already a copy of file in targetdir, the command sets the new copy's mode and owner to those of the old copy. If there is not already a copy of file in targetdir, the command sets the mode to 755 and the owner to bin. This option can be used alone or with the -g, -m, -o, -s, -S, or -u options. Specifies a group other than bin for the destination file. Ignores the default directory search list. Searches for the file to be installed only in the directo- ries specified on the command line (searchdir ...). This option cannot be used with the -c, -f, or -M options. Moves file to targetdir instead of copying it. This option cannot be used with the -c, -f, -i, or -n options. Specifies a mode other than 755 for the destination file. Installs file in targetdir if there is no copy in any of the searched directories (searchdir ...). Sets the mode of the file to 755 and the owner to bin. This option cannot be used with the -c, -f, or -M options. Saves the old copy of file by renaming it OLDfile and leaving it in the directory where it was found. This option cannot be used with the -c option. Specifies an owner other than bin for the destination file. Suppresses the display of all but error messages. Causes the binary to be stripped after installation; see strip(1). DESCRIPTION
The install command copies (or moves) file into the appropriate directory, retaining the owner and permissions of the existing copy, if any. A newly created file has permission code 755, owner bin, and group bin. The install command writes a message telling you which files it is replacing or creating and where they are going. If you supply no options or search directories (searchdir ...), the install command searches the /bin, /usr/bin, /etc, /lib, and /usr/lib directories in that order for a file with the same name as file. The command overwrites the first matching file with file and issues a message indicating that it has done so. If no match is found, the command tells you and exits without taking further action. If any search directories (searchdir ...) are specified on the command line, the install command searches them before it searches the default directories. EXAMPLES
To replace a command that already exists in one of the default directories, enter: install fixit This replaces the file fixit if it is found in the /bin, /usr/bin, /etc, /lib, or /usr/lib directory. Otherwise, the file fixit is not installed. For example, if /usr/bin/fixit exists, then this file is replaced by a copy of the file fixit in the current direc- tory. To replace a command that already exists in a specified or default directory while preserving the old version, enter: install -o fixit /etc /usr/games This replaces the file fixit if it is found in the /etc or /usr/games directory, or in one of the default directories. Otherwise, the file fixit is not installed. If the file is replaced, the old version is preserved by renaming it OLDfixit in the directory in which it was found. To replace a command that already exists in a specified directory, enter: install -i fixit /u/judith/bin /u/bernice/bin /usr/games This replaces the file fixit if it is found in the /u/judith/bin, /u/bernice/bin, or /usr/games directory. Otherwise, the file is not installed. To replace a command found in a default directory, or install it in a specified directory if it is not found, enter: install -n /usr/bin fixit This replaces the file fixit if it is found in one of the default directories. If the file is not found, it is installed as /usr/bin/fixit. To install a new command, enter: install -c /usr/bin fixit This creates a new command by installing a copy of the fixit file as /usr/bin/fixit, but only if this file does not already exist. To install a command in a specified directory whether or not it already exists, enter: install -f /usr/bin -o -s fixit This forces the fixit file to be installed as /usr/bin/fixit whether or not /usr/bin/fixit already exists. The old version, if any, is preserved by renaming it to /usr/bin/OLDfixit (a result of the -o option). The messages that tell where the new command was installed are suppressed (a result of the -s option). SEE ALSO
Commands: chgrp(1), chmod(1), chown(1), cp(1), installbsd(1), make(1), mv(1), strip(1) install(1)
All times are GMT -4. The time now is 12:11 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy