Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: SunOS 5.5.1 usage of Makefile command in make file
Operating Systems Solaris SunOS 5.5.1 usage of Makefile command in make file Post 302971839 by rajujayanthy on Tuesday 26th of April 2016 08:32:16 AM
Old 04-26-2016
SunOS 5.5.1 usage of Makefile command in make file
I am new to Solaris and compilation using make files.
I have a code base which is organized into different folders. At the root folder is a master make file and in the sub directories, there are make files for that particular folder.

In the make files present in subdirectories, I am seeing that "Makefile" is being used as a command for generating .obj files. For e.g.
Code:
 abc.obj : abc.asm \
 ../kernal/xxx.def \
 ../kernal/yyy.def \
 ../kernal/zzz.def \
 ../kernal/queue.def \
 Makefile \
 aaa.def \
 bbb.asm \
 ccc.asm \
 ddd.mac

Some other line
Code:
 abc.obj : abc.asm Makefile $(BB_INCS) xxx.def

Below are my questions.

1. Why is "Makefile" being used as a command? What does it signify? It is not defined anywhere in any other make file also.
2. What is a .mac file in Solaris? what is it's purpose?
3. What is the use of .def file in SOlaris? What is it's purpose?
 

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. UNIX for Advanced & Expert Users

Migration of binary file from Sunos 5.8 to Sunos 5.9

I have compiled binary file using "cc" on SunOS 5.8 and the same binary file i have copied to SunOS 5.9 and it is giving me core dump error.I want to know whether migration of compiled code from lower version to higer version created this problem. how can i solve this problem.I am pasting the core... (1 Reply)
Discussion started by: Arvind Maurya
1 Replies

3. Solaris

Questions about make -C in SunOS

I am using a SunOS to compile a project. The Makefile contains commands "$(MAKE) -C $$dir". However, in "man make" there is no -C option. I tried using MAKE=gmake but it failed too. My questions: 1. The make options for this SunOS is different from the gnu make options. Is it because of the... (4 Replies)
Discussion started by: yzhang
4 Replies

4. Programming

A question about Makefile run by GNU make

Hello everybody, Currently I'm learning how to build projects (C programming) with GNU make. I have a problem with one Makefile and I would appreciate if you could kindly give me a hand. Here is the environment: OS: Redhat linux 5 compiler: gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-44)... (2 Replies)
Discussion started by: dariyoosh
2 Replies

5. Shell Programming and Scripting

Memory Usage Monitor on Linux/SunOS Servers

ok, so i'm trying to write a shell script (not perl) that monitors memory usage on a server. but i'm confused as to what fields exactly determines that yes, memory is low on a particular server. it sounds simple enough, but it really isn't. what do I look for in the field below? ... (1 Reply)
Discussion started by: SkySmart
1 Replies

6. Shell Programming and Scripting

Need help with a script to make makefile

How do we create a shell script that creates a makefile? what if we want to use the #include header files too? (2 Replies)
Discussion started by: sslokhan
2 Replies

7. Programming

Makefile No rule to make target

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

8. Shell Programming and Scripting

Bash script from makefile - it is called each time i call make

I've created a tag in the makefile: mytag: $(shell ${PWD}/script.sh) When i do: make clean - the script is executed When i perform make or make mytag the script is again executed with the output: make: Nothing to be done for mytag What i want ? I want script.sh to be executed only... (0 Replies)
Discussion started by: Pufo
0 Replies

9. Solaris

Makefile on SunOS 5.11 Openindiana Hipster

SOLVED NOW Solution: Using bmake was the key. Ran into some few errors when using the compilers and the trick here was to first install the pkg system/header and then assign the working compiler in command line like this: bmake CC=/path/to/relevant/gcc CXX=/path/to/relevant/g++... (0 Replies)
Discussion started by: sometimespeter
0 Replies

10. Programming

Makefile instructions to create directories (CentOS7 , GNU Make 3.82)

Hello, My makefiles are set up to generate an environment specific build directory based on the local configuration and some values passed to make. It generally looks like, # compilers, may be passed to make CC++ = g++ FCOMP = gfortran # version of program, may be passed to make ver =... (4 Replies)
Discussion started by: LMHmedchem
4 Replies

LEARN ABOUT MINIX

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)
All times are GMT -4. The time now is 03:31 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy