04-26-2016
Quote:
Originally Posted by
rajujayanthy
I am new to Solaris and compilation using make files.
You might be new, but SunOS 2.5.1 is more archaeology that CS nowadays.
Quote:
1. Why is "Makefile" being used as a command? What does it signify? It is not defined anywhere in any other make file also.
There is no evidence in the posted material Makefile is used as a command. Nowhere is it executed. That would be quite surprising anyway.
Quote:
2. What is a .mac file in Solaris? what is it's purpose?
No specific purpose, there are no .mac type with Solaris, the developers might have chosen that extension for macros or whatever.
Quote:
3. What is the use of .def file in SOlaris? What is it's purpose?
Same as the above. The best guess would be some defines.
Last edited by jlliagre; 04-26-2016 at 05:10 PM..
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
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
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
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
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
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
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
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
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
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
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 DEBIAN
wml::mod::makemaker
wml::mod::MakeMaker(3) EN Tools wml::mod::MakeMaker(3)
NAME
wml::mod::MakeMaker - A Makefile generator
SYNOPSIS
#!wml -o Makefile
#use wml::mod::MakeMaker
<write-makefile [attributes]>
DESCRIPTION
This include file provides an easy way to write a Makefile to distribute your own WML modules. It is inspired by the "ExtUtils::MakeMaker"
Perl module.
Default targets
make all
This is the default target. It will build all include files and their documentation.
make install
Install include files and documentation in the locations given by ``wml -V2''.
make clean
Remove files generated by make.
make distclean
Like make clean, plus remove the Makefile too.
make dist
Build a distribution. Should only be used by the module maintainer. If there is a MANIFEST file, then the list of files to include is
taken from this file. Otherwise the tarball contains all source files, plus MakeMaker.wml, Makefile.wml, shtool and README if these
files exist.
Overriding default targets
To build the Makefile, all targets are put in separate buffers during pass 3, and those buffers are diverted by pass 5. You can override
this defaukt target by redefining buffer contents. Buffer names are explicit:
MK_ALL MK_INSTALL MK_CLEAN MK_DISTCLEAN MK_CONFIG MK_RELEASE
Defining new targets
The MK_USER is empty and devoted to this task.
ATTRIBUTES
The first three attributes are mandatory.
package
The name of the package
version
Its version number
modules
List of modules to build and install. This is a space separated list of filenames. Modules should reside in a sub-directory to be
compliant with actual file hierarchy. For instance, the declaration
modules="math/log.tmpl math/exp.tmpl"
tells that after compilation, there are two modules which are "math/log.tmpl" and "math/exp.tmpl". This modules will be installed to
"LibDir/include/math/log.tmpl" and "LibDir/include/math/exp.tmpl".
These modules will then be called in a WML file by
#use tmpl::math::log
#use tmpl::math::exp
Source files for these modules are obtained by replacing the suffix by .src.
src-ext
Defines an alternate suffix for the source files.
man-ext
Section number of the manual in which man files are put. Default is 3.
extradistfiles
Space separated list of files to include in a distribution. By default, all source files plus MakeMaker.wml, Makefile.wml, README and
shtool are included in a distribution.
EXAMPLE
<write-makefile
package="log"
version="3.14"
modules="math/log.tmpl"
source-ext="exp"
>
This will build the tmpl::math::log include module from the math/log.exp source file. This source file will also produce the
tmpl::math::log(3) manpage.
NOTES
Please do _not_ use a ".wml" suffix for your modules, they should be reserved for official WML modules shipped with WML. You may instead
put your initials or anything else.
AUTHOR
Denis Barbier
barbier@engelschall.com
REQUIRES
Internal: P1, P2, P3, P5
External: --
EN Tools 2014-04-16 wml::mod::MakeMaker(3)