10-10-2001
i can't use 'make' in my computer?
I need to compile a file,but 'make' does
not work.please tell me how to use it or
need which tools?
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I write a sh script that zip and copy to tape all files that older then 2 hours.
1. The way I choose is - touch a file with "now - 2 hours", then use fine with '! -newer'
2. Do you have any other idea to do it ?
tnx. (1 Reply)
Discussion started by: yairon
1 Replies
2. Shell Programming and Scripting
I wonder how I shall read the result below, especially 'what'
shown below.
The result was shown when I entered 'w'.
E.g what is TOP? What is gosh ( what does selmgr mean?)?
login@ idle JCPU PCPU what
6:15am 7:04 39 39 TOP
6:34am 6:45 45 45 TOP
6:41am ... (1 Reply)
Discussion started by: Aelgen
1 Replies
3. UNIX for Advanced & Expert Users
Can anybody help me?
I am developing a utility for automating message paging to a BT alphanumeric pager.
I am using a USR 56K Fax-modem connected to /dev/cuab on a Sun Ultra-10. I am using the UNIX 'tip' utility to connect to the modem and I have configured the modem as follows: Baud Rate:... (2 Replies)
Discussion started by: mybeat
2 Replies
4. Filesystems, Disks and Memory
Hi, guys, I have a big problem.
I've got a sun solaris 4.1.4 workstation, and the /var/adm/message file will add one row every few seconds. It soon becomes a large file.
I wander if there are some mistakes configuring the workstation.
the /var/adm/message is as follow:
... (1 Reply)
Discussion started by: cloudsmell
1 Replies
5. UNIX for Dummies Questions & Answers
Hi, guys, I have a big problem.
I've got a sun solaris 4.1.4 workstation, and the /var/adm/message file will add one row every few seconds. It becomes a large file in a short time.
I wander if there are some mistakes configuring the workstation.
the /var/adm/message is as follow:
... (3 Replies)
Discussion started by: cloudsmell
3 Replies
6. UNIX for Dummies Questions & Answers
echo 'it's friday'
why appear the > (3 Replies)
Discussion started by: yls177
3 Replies
7. IP Networking
Hey all,
I've bought a few bits from Belkin who seem quite happy to support FreeBSD! Last time I bought a UPS from them and it's still going well :D
I saw this on their website that the 16bit PCMCIA card was supported under FreeBSD:
http://www.belkin.com/network/F5D5020.html
I went to my... (0 Replies)
Discussion started by: WIntellect
0 Replies
8. Email Antispam Techniques and Email Filtering
Here is a crude procmail recipe that I quickly created (NOT a procmail recipe expert, btw) that has been catching lots of spam (current second after the charset_spam recipe posted earlier):
:0B
* .*If.you.do.not.wish.to.receive...*
more_spam
:0B
* You.requested.to.receive.this.mailing... (0 Replies)
Discussion started by: Neo
0 Replies
9. UNIX for Advanced & Expert Users
Somehow someone created a file named '-ov' in the root directory.
Given the name, the how was probably the result of some cpio command they bozo'ed.
I've tried a number of different ways to get rid of it using * and ? wildcards, '\' escape patterns etc.. They all fail with " illegal option --... (3 Replies)
Discussion started by: GSalisbury
3 Replies
10. Shell Programming and Scripting
Hopefully this doesn't come off as too much of a "newbie" question or a flamebait. But I have recently begun working with a Sun Solaris box after having spent the past five years working with RedHat. From what i can tell, thing look fairly similar and the 'man' command is some help. But I've... (7 Replies)
Discussion started by: deckard
7 Replies
make(3erl) Erlang Module Definition make(3erl)
NAME
make - A Make Utility for Erlang
DESCRIPTION
The module make provides a set of functions similar to the UNIX type Make functions.
EXPORTS
all() -> up_to_date | error
all(Options) -> up_to_date | error
Types Options = [Option]
Option = noexec | load | netload | <compiler option>
This function first looks in the current working directory for a file named Emakefile (see below) specifying the set of modules to
compile and the compile options to use. If no such file is found, the set of modules to compile defaults to all modules in the cur-
rent working directory.
Traversing the set of modules, it then recompiles every module for which at least one of the following conditions apply:
* there is no object file, or
* the source file has been modified since it was last compiled, or,
* an include file has been modified since the source file was last compiled.
As a side effect, the function prints the name of each module it tries to compile. If compilation fails for a module, the make pro-
cedure stops and error is returned.
Options is a list of make- and compiler options. The following make options exist:
* noexec
No execution mode. Just prints the name of each module that needs to be compiled.
* load
Load mode. Loads all recompiled modules.
* netload
Net load mode. Loads all recompiled modules an all known nodes.
All items in Options that are not make options are assumed to be compiler options and are passed as-is to compile:file/2 . Options
defaults to [] .
files(ModFiles) -> up_to_date | error
files(ModFiles, Options) -> up_to_date | error
Types ModFiles = [Module | File]
Module = atom()
File = string()
Options = [Option]
Option = noexec | load | netload | <compiler option>
files/1,2 does exactly the same thing as all/0,1 but for the specified ModFiles , which is a list of module or file names. The file
extension .erl may be omitted.
The Emakefile (if it exists) in the current directory is searched for compiler options for each module. If a given module does not
exist in Emakefile or if Emakefile does not exist, the module is still compiled.
EMAKEFILE
make:all/0,1 and make:files/1,2 looks in the current working directory for a file named Emakefile . If it exists, Emakefile should contain
elements like this:
Modules.
{Modules,Options}.
Modules is an atom or a list of atoms. It can be
* a module name, e.g. file1
* a module name in another directory, e.g. ../foo/file3
* a set of modules specified with a wildcards, e.g. 'file*'
* a wildcard indicating all modules in current directory, i.e. '*'
* a list of any of the above, e.g. ['file*','../foo/file3','File4']
Options is a list of compiler options.
Emakefile is read from top to bottom. If a module matches more than one entry, the first match is valid. For example, the following Emake-
file means that file1 shall be compiled with the options [debug_info,{i,"../foo"}] , while all other files in the current directory shall
be compiled with only the debug_info flag.
{'file1',[debug_info,{i,"../foo"}]}.
{'*',[debug_info]}.
Ericsson AB tools 2.6.6.3 make(3erl)