Sponsored Content
Top Forums Programming i can't use 'make' in my computer? Post 8389 by dsun5 on Wednesday 10th of October 2001 08:43:10 PM
Old 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

How to subtract 2 hours from 'date' in shell ( /bin/sh ) script ?

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

Clearify what it means under 'WHAT' when hit the 'w'-command

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

Terminal 'Local Echo' lost on Modem Dial-out

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

HELP! The '/var/adm/message' file increase every few seconds???

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

HELP! The '/var/adm/message' file increase every few seconds???

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

quoting echo 'it's friday'

echo 'it's friday' why appear the > (3 Replies)
Discussion started by: yls177
3 Replies

7. IP Networking

BELKIN 'F5D5020' 16bit PCMCIA - FreeBSD HOWTO

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

Procmail recipe: blocking 'unsubscribe and opt-out' messages....

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

How to remove a file with a leading dash '-' in it's name?

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

What are the differences between 'bash' and 'sh'

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
CCONTROL(1)															       CCONTROL(1)

NAME
ccontrol - wrapper to control distcc, ccache and more SYNOPSIS
gcc ... cc ... c++ ... make ... ld ... ccontrol [--section=<section>] <name> ... ccontrol [--section=<section>] DESCRIPTION
The ccontrol(1) program takes over the roles of the compiler and linker, and reads a configuration file to decide what to do before invoking them. This is particularly useful for centralized control over commands and options, such as enabling distcc(1) and ccache(1). When ccontrol(1) is invoked under its own name with no arguments, it prints out the settings which apply in this directory (unless --section is specified). Versions are named after the last person to report a bug. OPTIONS
Normally ccontrol(1) is invoked as a symboling link to cc, make, etc, so it can identify what is being invoked by examining its own name. It can also be invoked under its own name, in which case ccontrol-specific arguments can be supplied. The first non-option argument will be used to identify the invocation, eg. "ccontrol gcc ...". The following options are supported, when invoked as ccontrol: --section=<section> This is treated as the "current directory" for the purposes of evaluating the configuration file. As all real directories must begin with a "/" using an argument which does not, is a good way of overriding configuration for this particular invocation. CONFIGURATION FILE
ccontrol's configuration file is $HOME/.ccontrol/config. If this cannot be read (and written), your compilations will all fail. It is normal to have several different configuration files in this directory, and make default a symbolic link. SYNTAX
A configuration file consists of sections, led by a "[path]" header and followed by indented "name = value" entries. The first section is usually labelled "[*]" to set up the defaults. At the very least, you must set the "cc", "c++", "make" and "ld" values. ccontrol will read every section which matches the current directory, so you can override values on a per-directory basis. The "[path]" header of each section is a shell-style wildcard (see glob(7)) which indicates the directory or directories it applies to. Usually this will end in a "*" to include all subdirectories. All paths beginning with "~" are relative to the user's home directory. A path may be specified as a directory, in which case ccontrol will append the program name to the directory. The following settings are available: cc Followed by = specifies the path of the compiler to be invoked when ccontrol is invoked as "cc" or "gcc". ccontrol will fail to compile C programs if this is not set. c++ Followed by = specifies the path of the compiler to be invoked when ccontrol is invoked as "c" or "g". ccontrol will fail to compile C++ programs if this is not set. ld Followed by = specifies the path of the linker to be invoked when ccontrol is invoked as "ld". ccontrol will fail to link programs if this is not set. make Followed by = specifies the path of the binary to be invoked when ccontrol is invoked as "make". ccontrol will fail to make if this is not set. ccache Followed by = specifies the path of "ccache", and indicates that ccache is to be used where appropriate. If followed by disable, or not set, ccache will not be used. distcc Followed by = specifies the path of "distcc", and indicates that distcc is to be used where appropriate. If followed by disable, or not set, or distcc-hosts is not set, distcc will not be used. distcc-hosts Followed by = specifies the distcc servers to use, as per the DISTCC_HOSTS environment variable in distcc(1). Followed by disable disables distcc. distc++-hosts The same as distcc-hosts, but only applies to Ccompilations. If not set, distcc-hosts is used. You can thus disable distcc for C compilations by setting "distc++-hosts disable". cpus Followed by = and a number of CPUs, set to the number of CPUs you have (the default is "1"). ccontrol uses this to tune the degree of parallelism. no-parallel Followed by = and a space-separated list of wildcards, suppresses parallel make for any make target matching one of those. This option is needed because ccontrol(1) usually forces make(1) to perform all actions in parallel, but this can be confusing when an error occurs, and breaks poorly-written makefiles. Followed by disable, enables parallel make for all targets: this is useful to re-enable parallel make in a subdirectory. nice Followed by = and a priority level from -19 to 20, causes ccontrol to try to set its priority to this value. Default is 10. include Followed by = specifies a file to include at the current point. The effect is exactly as if the contents of the included file were literally inserted. Can be used at file level to include sections. Can also be used within sections to include section fragments. add make Followed by = specifies an argument to be added to each invocation of make. This can be specified multiple times to add multiple arguments. Followed by disable removes any arguments previously specified. add env Followed by = specifies an environment variable to be set, such as "add env = CCACHE_DIR=/tmp". This can be specified multiple times to set multiple environment variables. Followed by disable removes any arguments previously specified. verbose By itself, indicates that ccontrol(1) is to spit lots of crap out to standard error about what it's doing to your innocent command line. lock-file Specify a particular lock file to use. EXAMPLES
This is the minimal configuration file: [*] cc = /usr/bin/gcc c++ = /usr/bin/g++ ld = /usr/bin/ld make = /usr/bin/make If you have multiple locations (such as a laptop) it is common to have a "global" file which is included from every configuration file, like so: # Configuration file for when I'm at work. Lots of distcc hosts! include = ~/.ccontrol/global [*] distcc-hosts = snab swarm1 swarm3 swarm4 swarm5 fandango2 mingo distc++-hosts = snab mingo Here is a complete configuration file with several common scenarios: [*] cc = /usr/bin/gcc-4.0 c++ = /usr/bin/g++-4.0 ld = /usr/bin/ld make = /usr/bin/make # Comment this back in for debugging # verbose distcc = /usr/bin/distcc distcc-hosts = snab swarm1 swarm3 swarm4 swarm5 fandango2 mingo distc++-hosts = snab mingo ccache = /usr/bin/ccache # make check should not generally be run in parallel no-parallel = check # Wesnoth doesn't compile with g++ 4.0 [*wesnoth*] c++ = /usr/bin/g++-3.4 # Stupid third-party modules don't build in parallel. [/usr/src/modules/*] no-parallel = * # Using distcc when testing module-init-tools causes strange effects. [*module-init-tools*/tests/*] distcc disable BUGS
The ~/.ccontrol/config file must be writable: ccontrol(1) needs to get an exclusive write lock on it, which means it needs to open the file for writing. Use include to include read-only files. ccontrol will not immediately notice a change in included files, only in the toplevel file (ccontrol re-reads the config file if it changed while ccontrol was trying to grab a lock). The Linux (< 2.6.15) cpufreq ondemand governor (common on laptops) will not increase CPU speed when using ccontrol(1), because ccontrol re-nices compilations. This can make builds 2-3 times slower. Either use another governor, or tell ondemand to ignore nice values: echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/ignore_nice If your code doesn't compile, ccontrol can only make it not compile faster. AUTHOR
Written by Rusty Russell <rusty@rustcorp.com.au[1]> LICENSE
Copyright (C) 2005 Rusty Russell. Free use of this software is granted under the terms of the GNU General Public License (GPL). SEE ALSO
make(1), cc(1), c++(1), ld(1), distcc(1), ccache(1), glob(7), cpufreq-set(1) AUTHOR
Rusty Russell <rusty@rustcorp.com.au> Author. NOTES
1. rusty@rustcorp.com.au mailto:rusty@rustcorp.com.au v0.9 5 January 2006 CCONTROL(1)
All times are GMT -4. The time now is 10:43 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy