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)
I have 2 libraries in 2 different directories that I build with Makefiles.
library B depends on library A. If I modify a .cpp file in library A and run lib B's Makefile can I have B's makefile to automatically rebuild library A?
I am now rebuilding A, followed by B... but I'd like B to... (0 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)
Hi,
Can anybody help mw how to use 2 conditinal directives in makefile (with AND=&&), so far none of my tries succedded.
Getting this warning like below. I thought that C's && will work, but alas, played with (), spaces and etc..
and I have only GNU Make 3.80
ifeq ($(VAR1),15) &&... (4 Replies)
Help. My script is working fine when executed manually but the cron seems not to catch up the command when registered.
The script is as follow:
#!/bin/sh
for file in file_1.txt file_2.txt file_3.txt
do
awk '{ print "0" }' $file > tmp.tmp
mv tmp.tmp $file
done
And the cron... (2 Replies)
Hello All,
I am running source command on my project configuration file app.cfg which has conditional statements with make file systax E.g ifeq ($(APP_CMP_DIR),trunk).
When I source this file it throws error: syntax error near unexpected token... (1 Reply)
Hi Team
we have created a DNS server at RHEL6.2 environment in 10.20.203.x/24 network.
Everything is going well on linux client as nslookup, ping by host etc in entire subnet. We are getting problem in windows client as nslookup working as well but not ping. all the firewall is disabled and... (5 Replies)
I am trying to automate a script where I need to use pbrun /bin/su but for some reason it is not passing thru the pbrun as my code below.
. ~/.bash_profile
pbrun /bin/su - content
c h 1
hpsvn up file path
I am executing this from an external .sh file that is pointing to this scripts file... (14 Replies)
Hello, Newbie here,
I have a perfectly well working web service call I can issue from chrome (PC Windows 10) and get the results I want (a dimmer being turned on in Fibaro Home Center 2 at level 40)
I am not allowed to post urls but the below works with http and :// and... (3 Replies)
Hi Team,
I have written the shell script which returns the result of the disk space filesystems which has crossed the threshold limit in HTML Format. Below mentioned is the script which worked perfectly on QA system.
df -h | awk -v host=`hostname` '
BEGIN {
print "<table border="4"... (13 Replies)
Discussion started by: Harihsun
13 Replies
LEARN ABOUT REDHAT
mandoc.db
MANDOC.DB(5) File Formats Manual MANDOC.DB(5)NAME
mandoc.db - manual page database
DESCRIPTION
The mandoc.db file format is used to store information about installed manual pages to facilitate semantic searching for manuals. Each
manual page tree contains its own mandoc.db file; see FILES for examples.
Such database files are generated by makewhatis(8) and used by man(1), apropos(1) and whatis(1).
The file format uses three datatypes:
- 32-bit signed integer numbers in big endian (network) byte ordering
- NUL-terminated strings
- lists of NUL-terminated strings, terminated by a second NUL character
Numbers are aligned to four-byte boundaries; where they follow strings or lists of strings, padding with additional NUL characters occurs.
Some, but not all, numbers point to positions in the file. These pointers are measured in bytes, and the first byte of the file is
considered to be byte 0.
Each file consists of:
- One magic number, 0x3a7d0cdb.
- One version number, currently 1.
- One pointer to the macros table.
- One pointer to the final magic number.
- The pages table (variable length).
- The macros table (variable length).
- The magic number once again, 0x3a7d0cdb.
The pages table contains one entry for each physical manual page file, no matter how many hard and soft links it may have in the file
system. The pages table consists of:
- The number of pages in the database.
- For each page:
- One pointer to the list of names.
- One pointer to the list of sections.
- One pointer to the list of architectures or 0 if the page is machine-independent.
- One pointer to the one-line description string.
- One pointer to the list of filenames.
- For each page, the list of names. Each name is preceded by a single byte indicating the sources of the name. The meaning of the bits
is:
- 0x10: The name appears in a filename.
- 0x08: The name appears in a header line, i.e. in a .Dt or .TH macro.
- 0x04: The name is the first one in the title line, i.e. it appears in the first .Nm macro in the NAME section.
- 0x02: The name appears in any .Nm macro in the NAME section.
- 0x01: The name appears in an .Nm block in the SYNOPSIS section.
- For each page, the list of sections. Each section is given as a string, not as a number.
- For each architecture-dependent page, the list of architectures.
- For each page, the one-line description string taken from the .Nd macro.
- For each page, the list of filenames relative to the root of the respective manpath. This list includes hard links, soft links, and
links simulated with .so roff(7) requests. The first filename is preceded by a single byte having the following significance:
- FORM_SRC = 0x01: The file format is mdoc(7) or man(7).
- FORM_CAT = 0x02: The manual page is preformatted.
- Zero to three NUL bytes for padding.
The macros table consists of:
- The number of different macro keys, currently 36. The ordering of macros is defined in <mansearch.h> and the significance of the
macro keys is documented in apropos(1).
- For each macro key, one pointer to the respective macro table.
- For each macro key, the macro table (variable length).
Each macro table consists of:
- The number of entries in the table.
- For each entry:
- One pointer to the value of the macro key. Each value is a string of text taken from some macro invocation.
- One pointer to the list of pages.
- For each entry, the value of the macro key.
- Zero to three NUL bytes for padding.
- For each entry, one or more pointers to pages in the pages table, pointing to the pointer to the list of names, followed by the number
0.
FILES
/usr/share/man/mandoc.db The manual page database for the base system.
/usr/X11R6/man/mandoc.db The same for the X(7) Window System.
/usr/local/man/mandoc.db The same for packages(7).
A program to dump mandoc.db files in a human-readable format suitable for diff(1) is provided in the directory
/usr/src/regress/usr.bin/mandoc/db/dbm_dump/.
SEE ALSO apropos(1), man(1), whatis(1), makewhatis(8)HISTORY
A manual page database /usr/lib/whatis first appeared in 2BSD. The present format first appeared in OpenBSD 6.1.
AUTHORS
The original version of makewhatis(8) was written by Bill Joy in 1979. The present database format was designed by Ingo Schwarze
<schwarze@openbsd.org> in 2016.
Debian August 1, 2016 MANDOC.DB(5)