1 |
060925 Richard Fish wrote: |
2 |
> On 9/25/06, Philip Webb <purslow@×××××××××.ca> wrote: |
3 |
> Can either of you post your make.conf please? |
4 |
|
5 |
You asked (smile): |
6 |
|
7 |
# Copyright 1999-2004 Gentoo Foundation |
8 |
# Distributed under the terms of the GNU General Public License v2 |
9 |
# $Header: /var/cvsroot/gentoo-src/portage/cnf/make.conf.x86,v 1.5 2004/10/10 23:27:28 carpaski Exp $ |
10 |
# Contains local system settings for Portage system |
11 |
|
12 |
# Please review 'man make.conf' for more information. |
13 |
|
14 |
# PP 031116 |
15 |
|
16 |
CLEAN_DELAY=10 |
17 |
|
18 |
# Build-time functionality |
19 |
# ======================== |
20 |
# |
21 |
# The USE variable is used to enable optional build-time functionality. For |
22 |
# example, quite a few packages have optional X, gtk or GNOME functionality |
23 |
# that can only be enabled or disabled at compile-time. Gentoo Linux has a |
24 |
# very extensive set of USE variables described in our USE variable HOWTO at |
25 |
# http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=1 |
26 |
# |
27 |
# The available list of use flags with descriptions is in your portage tree. |
28 |
# Use 'less' to view them: --> less /usr/portage/profiles/use.desc <-- |
29 |
# |
30 |
# 'ufed' is an ncurses/dialog interface available in portage to make handling |
31 |
# useflags for you. 'emerge app-portage/ufed' |
32 |
# |
33 |
# Example: |
34 |
#USE="X gtk gnome -alsa" |
35 |
|
36 |
# PP 041110 : suppress dft use flags fr /etc/make.profile/make.defaults : |
37 |
# sound (alsa arts avi encode esd mad mikmod oggvorbis oss quicktime xmms) |
38 |
# sql (berkdb libg++ mysql postgres) f77 nls |
39 |
# PP 050501 : '-alsa' added for Gnomelib |
40 |
# PP 050831 : '-vorbis' added for Mplayer |
41 |
# PP 050905 : 'usb' added for scanner |
42 |
# PP 050906 : '-flac -mp3 -ogg -sox' added to remove further sound |
43 |
# PP 050910 : 'nvidia' added for Nvidia |
44 |
# PP 051119 : 'pop' added for Mutt |
45 |
# PP 051204 : '-gnome' added for efficiency |
46 |
# PP 060320 : 'fam' added for Gamin |
47 |
|
48 |
#USE="fam nvidia pop usb -alsa -arts -avi -berkdb -encode -esd -flac -f77 |
49 |
# -gnome -libg++ -mad -mikmod -mp3 -mysql -nls -ogg -oss -postgres |
50 |
# -quicktime -sox -vorbis -xmms" |
51 |
|
52 |
# PP 060507 : reorg'd using 2006.0 & "-*" |
53 |
# PP 060603 : drop 'pam' |
54 |
# PP 060701 : add 'nptl nptlonly' for glibc-2.4 |
55 |
# PP 060702 : chg 'qt' -> 'qt3' ('qt' ~ longer valid) |
56 |
# PP 060705 : drop 'mozilla' |
57 |
USE="-* apm bitmap-fonts bonobo bzip2 cdr crypt cups dri foomaticdb |
58 |
gdbm gif gnutls gpm gtk gtk2 imagemagick imlib java javascript jpeg kde |
59 |
libwww lm_sensors mime motif mpeg ncurses nptl nptlonly |
60 |
nsplugin nvidia opengl pcre pdf perl plotutils png pop python |
61 |
qt3 readline scanner session slang ssl |
62 |
tiff truetype truetype-fonts type1-fonts unicode usb X xml xv zlib" |
63 |
|
64 |
# PP 060915 : add 2 lines for mod-X |
65 |
INPUT_DEVICES="keyboard mouse" |
66 |
VIDEO_CARDS="nv nvidia vesa" |
67 |
|
68 |
# Host Setting |
69 |
# ============ |
70 |
# |
71 |
# Change this line as appropriate (i686, i586, i486 or i386). |
72 |
# All modern systems (even Athlons) should use "i686-pc-linux-gnu". |
73 |
# All K6's are i586. |
74 |
CHOST="i686-pc-linux-gnu" |
75 |
|
76 |
# Host and optimization settings |
77 |
# ============================== |
78 |
# |
79 |
# For optimal performance, enable a CFLAGS setting appropriate for your CPU. |
80 |
# |
81 |
# Please note that if you experience strange issues with a package, it may be |
82 |
# due to gcc's optimizations interacting in a strange way. Please test the |
83 |
# package (and in some cases the libraries it uses) at default optimizations |
84 |
# before reporting errors to developers. |
85 |
# |
86 |
# -mcpu=<cpu-type> means optimize code for the particular type of CPU without |
87 |
# breaking compatibility with other CPUs. |
88 |
# |
89 |
# -march=<cpu-type> means to take full advantage of the ABI and instructions |
90 |
# for the particular CPU; this will break compatibility with older CPUs (for |
91 |
# example, -march=athlon-xp code will not run on a regular Athlon, and |
92 |
# -march=i686 code will not run on a Pentium Classic. |
93 |
# |
94 |
# CPU types supported in gcc-3.2 and higher: athlon-xp, athlon-mp, |
95 |
# athlon-tbird, athlon, k6, k6-2, k6-3, i386, i486, i586 (Pentium), i686 |
96 |
# (PentiumPro), pentium, pentium-mmx, pentiumpro, pentium2 (Celeron), |
97 |
# pentium3, and pentium4. |
98 |
# |
99 |
# Note that Gentoo Linux 1.4 and higher include at least gcc-3.2. |
100 |
# |
101 |
# CPU types supported in gcc-2.95*: k6, i386, i486, i586 (Pentium), i686 |
102 |
# (Pentium Pro), pentium, pentiumpro Gentoo Linux 1.2 and below use gcc-2.95* |
103 |
# |
104 |
# CRITICAL WARNINGS: ****************************************************** # |
105 |
# K6 markings are deceptive. Avoid setting -march for them. See Bug #24379. # |
106 |
# Pentium-M CPU's should not enable sse2 until at least gcc-3.4. Bug 50616. # |
107 |
# ************************************************************************* # |
108 |
# |
109 |
# Decent examples: |
110 |
# |
111 |
#CFLAGS="-march=pentium3 -O3 -pipe" |
112 |
#CFLAGS="-mcpu=athlon-xp -O3 -pipe" |
113 |
CFLAGS="-O2 -march=athlon-xp -pipe" # PP 031008 |
114 |
|
115 |
# If you set a CFLAGS above, then this line will set your default C++ flags to |
116 |
# the same settings. |
117 |
CXXFLAGS="${CFLAGS}" |
118 |
|
119 |
# Advanced Masking |
120 |
# ================ |
121 |
# |
122 |
# Gentoo is using a new masking system to allow for easier stability testing |
123 |
# on packages. KEYWORDS are used in ebuilds to mask and unmask packages based |
124 |
# on the platform they are set for. A special form has been added that |
125 |
# indicates packages and revisions that are expected to work, but have not yet |
126 |
# been approved for the stable set. '~arch' is a superset of 'arch' which |
127 |
# includes the unstable, in testing, packages. Users of the 'x86' architecture |
128 |
# would add '~x86' to ACCEPT_KEYWORDS to enable unstable/testing packages. |
129 |
# '~ppc', '~sparc' are the unstable KEYWORDS for their respective platforms. |
130 |
# |
131 |
# Please note that this is not for development, alpha, beta, nor cvs release |
132 |
# packages. "Broken" packages will not be added to testing and should not be |
133 |
# requested to be added. Alternative routes are available to developers |
134 |
# for experimental packages, and it is at their discretion to use them. |
135 |
# |
136 |
# DO NOT PUT ANYTHING BUT YOUR SPECIFIC ~ARCHITECTURE IN THE LIST. |
137 |
# IF YOU ARE UNSURE OF YOUR ARCH, OR THE IMPLICATIONS, DO NOT MODIFY THIS. |
138 |
# |
139 |
#ACCEPT_KEYWORDS="~arch" |
140 |
|
141 |
# Portage Directories |
142 |
# =================== |
143 |
# |
144 |
# Each of these settings controls an aspect of portage's storage and file |
145 |
# system usage. If you change any of these, be sure it is available when |
146 |
# you try to use portage. *** DO NOT INCLUDE A TRAILING "/" *** |
147 |
# |
148 |
# PORTAGE_TMPDIR is the location portage will use for compilations and |
149 |
# temporary storage of data. This can get VERY large depending upon |
150 |
# the application being installed. |
151 |
#PORTAGE_TMPDIR=/var/tmp |
152 |
PORTAGE_TMPDIR=/z/tmp # PP 031018 |
153 |
# |
154 |
# PORTDIR is the location of the portage tree. This is the repository |
155 |
# for all profile information as well as all ebuilds. This directory |
156 |
# itself can reach 200M. WE DO NOT RECOMMEND that you change this. |
157 |
#PORTDIR=/usr/portage |
158 |
# |
159 |
# DISTDIR is where all of the source code tarballs will be placed for |
160 |
# emerges. The source code is maintained here unless you delete |
161 |
# it. The entire repository of tarballs for gentoo is 9G. This is |
162 |
# considerably more than any user will ever download. 2-3G is |
163 |
# a large DISTDIR. |
164 |
#DISTDIR=${PORTDIR}/distfiles |
165 |
# |
166 |
# PKGDIR is the location of binary packages that you can have created |
167 |
# with '--buildpkg' or '-b' while emerging a package. This can get |
168 |
# upto several hundred megs, or even a few gigs. |
169 |
#PKGDIR=${PORTDIR}/packages |
170 |
# |
171 |
# PORT_LOGDIR is the location where portage will store all the logs it |
172 |
# creates from each individual merge. They are stored as NNNN-$PF.log |
173 |
# in the directory specified. This is disabled until you enable it by |
174 |
# providing a directory. Permissions will be modified as needed IF the |
175 |
# directory exists, otherwise logging will be disabled. NNNN is the |
176 |
# increment at the time the log is created. Logs are thus sequential. |
177 |
# PP 050207 |
178 |
PORT_LOGDIR=/var/log/emerge-logs |
179 |
|
180 |
# |
181 |
# PORTDIR_OVERLAY is a directory where local ebuilds may be stored |
182 |
# without concern they wb deleted by rsync updates. Default not defined. |
183 |
# PP 060310 |
184 |
PORTDIR_OVERLAY=/usr/local/portage |
185 |
|
186 |
# Fetching files |
187 |
# ============== |
188 |
# |
189 |
# If you need to set a proxy for wget or lukemftp, add the appropriate "export |
190 |
# ftp_proxy=<proxy>" and "export http_proxy=<proxy>" lines to /etc/profile if |
191 |
# all users on your system should use them. |
192 |
# |
193 |
# Portage uses wget by default. Here are some settings for some alternate |
194 |
# downloaders -- note that you need to merge these programs first before they |
195 |
# will be available. |
196 |
# |
197 |
# Default fetch command (5 tries, passive ftp for firewall compatibility) |
198 |
#FETCHCOMMAND="/usr/bin/wget -t 5 --passive-ftp \${URI} -P \${DISTDIR}" |
199 |
#RESUMECOMMAND="/usr/bin/wget -c -t 5 --passive-ftp \${URI} -P \${DISTDIR}" |
200 |
# |
201 |
# Using wget, ratelimiting downloads |
202 |
#FETCHCOMMAND="/usr/bin/wget -t 5 --passive-ftp --limit-rate=200k \${URI} -P \${DISTDIR}" |
203 |
#RESUMECOMMAND="/usr/bin/wget -c -t 5 --passive-ftp --limit-rate=200k \${URI} -P \${DISTDIR}" |
204 |
# |
205 |
# Lukemftp (BSD ftp): |
206 |
#FETCHCOMMAND="/usr/bin/lukemftp -s -a -o \${DISTDIR}/\${FILE} \${URI}" |
207 |
#RESUMECOMMAND="/usr/bin/lukemftp -s -a -R -o \${DISTDIR}/\${FILE} \${URI}" |
208 |
# |
209 |
# Prozilla (turbo downloader) |
210 |
#FETCHCOMMAND='/usr/bin/proz --no-getch -s ${URI} -P ${DISTDIR}' |
211 |
# |
212 |
# Portage uses GENTOO_MIRRORS to specify mirrors to use for source retrieval. |
213 |
# The list is a space separated list which is read left to right. If you use |
214 |
# another mirror we highly recommend leaving the default mirror at the end of |
215 |
# the list so that portage will fall back to it if the files cannot be found |
216 |
# on your specified mirror. We _HIGHLY_ recommend that you change this setting |
217 |
# to a nearby mirror by merging and using the 'mirrorselect' tool. |
218 |
# PP 041114 try by hand : Osuosl is slow, but works : |
219 |
#GENTOO_MIRRORS="http://gentoo.osuosl.org/" |
220 |
# PP 051113 : next line generated by Mirrorselect : |
221 |
GENTOO_MIRRORS="http://gentoo.mirrors.pair.com/ http://adelie.polymtl.ca/ http://prometheus.cs.wmich.edu/gentoo http://gentoo.chem.wisc.edu/gentoo/ http://gentoo.seren.com/gentoo" |
222 |
# |
223 |
# Portage uses PORTAGE_BINHOST to specify mirrors for prebuilt-binary packages. |
224 |
# The list is a single entry specifying the full address of the directory |
225 |
# serving the tbz2's for your system. Running emerge with either '--getbinpkg' |
226 |
# or '--getbinpkgonly' will cause portage to retrieve the metadata from all |
227 |
# packages in the directory specified, and use that data to determine what will |
228 |
# be downloaded and merged. '-g' or '-gK' are the recommend parameters. Please |
229 |
# consult the man pages and 'emerge --help' for more information. For FTP, the |
230 |
# default connection is passive -- If you require an active connection, affix |
231 |
# an asterisk (*) to the end of the host:port string before the path. |
232 |
#PORTAGE_BINHOST="http://grp.mirror.site/gentoo/grp/1.4/i686/athlon-xp/" |
233 |
# This ftp connection is passive ftp. |
234 |
#PORTAGE_BINHOST="ftp://login:pass@××××××××××.site/pub/grp/i686/athlon-xp/" |
235 |
# This ftp connection is active ftp. |
236 |
#PORTAGE_BINHOST="ftp://login:pass@××××××××××.site:21*/pub/grp/i686/athlon-xp/" |
237 |
|
238 |
# Synchronizing Portage |
239 |
# ===================== |
240 |
# |
241 |
# Each of these settings affects how Gentoo synchronizes your Portage tree. |
242 |
# Synchronization is handled by rsync and these settings allow some control |
243 |
# over how it is done. |
244 |
# |
245 |
# |
246 |
# SYNC is the server used by rsync to retrieve a localized rsync mirror |
247 |
# rotation. This allows you to select servers that are geographically |
248 |
# close to you, yet still distribute the load over a number of servers. |
249 |
# Please do not single out specific rsync mirrors. Doing so places undue |
250 |
# stress on particular mirrors. Instead you may use one of the following |
251 |
# continent specific rotations: |
252 |
# |
253 |
# Default: "rsync://rsync.gentoo.org/gentoo-portage" |
254 |
# North America: "rsync://rsync.namerica.gentoo.org/gentoo-portage" |
255 |
# South America: "rsync://rsync.samerica.gentoo.org/gentoo-portage" |
256 |
# Europe: "rsync://rsync.europe.gentoo.org/gentoo-portage" |
257 |
# Asia: "rsync://rsync.asia.gentoo.org/gentoo-portage" |
258 |
# Australia: "rsync://rsync.au.gentoo.org/gentoo-portage" |
259 |
SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage" |
260 |
# |
261 |
# RSYNC_RETRIES sets the number of times portage will attempt to retrieve |
262 |
# a current portage tree before it exits with an error. This allows |
263 |
# for a more successful retrieval without user intervention most times. |
264 |
#RSYNC_RETRIES="3" |
265 |
# |
266 |
# RSYNC_TIMEOUT sets the length of time rsync will wait before it times out |
267 |
# on a connection. Most users will benefit from this setting as it will |
268 |
# reduce the amount of 'dead air' they experience when they run across |
269 |
# the occasional, unreachable mirror. Dialup users might want to set this |
270 |
# value up around the 300 second mark. |
271 |
#RSYNC_TIMEOUT=180 |
272 |
|
273 |
# Advanced Features |
274 |
# ================= |
275 |
# |
276 |
# MAKEOPTS provides extra options that may be passed to 'make' when a |
277 |
# program is compiled. Presently the only use is for specifying |
278 |
# the number of parallel makes (-j) to perform. The suggested number |
279 |
# for parallel makes is CPUs+1. |
280 |
#MAKEOPTS="-j2" |
281 |
# |
282 |
# PORTAGE_NICENESS provides a default increment to emerge's niceness level. |
283 |
# Note: This is an increment. Running emerge in a niced environment will |
284 |
# reduce it further. Default is unset. |
285 |
# PP 040918 uncomment next line |
286 |
PORTAGE_NICENESS=3 |
287 |
# |
288 |
# AUTOCLEAN enables portage to automatically clean out older or overlapping |
289 |
# packages from the system after every successful merge. This is the |
290 |
# same as running 'emerge -c' after every merge. Set with: "yes" or "no". |
291 |
# This does not affect the unpacked source. See 'noclean' below. |
292 |
#AUTOCLEAN="yes" |
293 |
# |
294 |
# FEATURES are settings that affect the functionality of portage. Most of |
295 |
# these settings are for developer use, but some are available to non- |
296 |
# developers as well. |
297 |
# |
298 |
# 'autoaddcvs' causes portage to automatically try to add files to cvs |
299 |
# that will have to be added later. Done at generation times |
300 |
# and only has an effect when 'cvs' is also set. |
301 |
# 'buildpkg' causes binary packages to be created of all packages that |
302 |
# are being merged. |
303 |
# 'ccache' enables ccache support via CC. |
304 |
# PP 041106 : Ccache is useful if emerge/system crashes |
305 |
# needs pkg installed to work (done) |
306 |
# 'collision-protect' |
307 |
# prevents packages from overwriting files that are owned by |
308 |
# another package or by no package at all. |
309 |
# 'cvs' causes portage to enable all cvs features (commits, adds), |
310 |
# and to apply all USE flags in SRC_URI for digests -- for |
311 |
# developers only. |
312 |
# 'digest' causes digests to be generated for all packages being merged. |
313 |
# 'distcc' enables distcc support via CC. |
314 |
# 'distlocks' enables distfiles locking using fcntl or hardlinks. This |
315 |
# is enabled by default. Tools exist to help clean the locks |
316 |
# after crashes: /usr/lib/portage/bin/clean_locks. |
317 |
# 'fixpackages' allows portage to fix binary packages that are stored in |
318 |
# PKGDIR. This can consume a lot of time. 'fixpackages' is |
319 |
# also a script that can be run at any given time to force |
320 |
# the same actions. |
321 |
# 'gpg' enables basic verification of Manifest files using gpg. |
322 |
# This features is UNDER DEVELOPMENT and reacts to features |
323 |
# of strict and severe. Heavy use of gpg sigs is coming. |
324 |
# 'keeptemp' prevents the clean phase from deleting the temp files ($T) |
325 |
# from a merge. |
326 |
# 'keepwork' prevents the clean phase from deleting the WORKDIR. |
327 |
# 'maketest' causes ebuilds to perform testing phases if they are capable |
328 |
# of it. Some packages support this automaticaly via makefiles. |
329 |
# 'noauto' causes ebuild to perform only the action requested and |
330 |
# not any other required actions like clean or unpack -- for |
331 |
# debugging purposes only. |
332 |
# 'noclean' prevents portage from removing the source and temporary files |
333 |
# after a merge -- for debugging purposes only. |
334 |
# 'nostrip' prevents the stripping of binaries. |
335 |
# 'notitles' disables xterm titlebar updates (which contain status info). |
336 |
# 'sandbox' enables sandboxing when running emerge and ebuild. |
337 |
# 'strict' causes portage to react strongly to conditions that are |
338 |
# potentially dangerous, like missing/incorrect Manifest files. |
339 |
# 'userpriv' allows portage to drop root privileges while it is compiling, |
340 |
# as a security measure. As a side effect this can remove |
341 |
# sandbox access violations for users. |
342 |
# 'usersandbox' enables sandboxing while portage is running under userpriv. |
343 |
#FEATURES="sandbox buildpkg ccache distcc userpriv usersandbox notitles noclean noauto cvs keeptemp keepwork autoaddcvs" |
344 |
#FEATURES="sandbox ccache distcc distlocks autoaddcvs" |
345 |
FEATURES="userpriv" |
346 |
# |
347 |
# CCACHE_SIZE sets the space use limitations for ccache. The default size is |
348 |
# 2G, and will be set if not defined otherwise and ccache is in features. |
349 |
# Portage will set the default ccache dir if it is not present in the |
350 |
# user's environment, for userpriv it sets: ${PORTAGE_TMPDIR}/ccache |
351 |
# (/var/tmp/ccache), and for regular use the default is /root/.ccache. |
352 |
# Sizes are specified with 'G' 'M' or 'K'. |
353 |
# '2G' for 2 gigabytes, '2048M' for 2048 megabytes (same as 2G). |
354 |
#CCACHE_SIZE="2G" |
355 |
# |
356 |
# DISTCC_DIR sets the temporary space used by distcc. |
357 |
#DISTCC_DIR="${PORTAGE_TMPDIR}/.distcc" |
358 |
# |
359 |
# RSYNC_EXCLUDEFROM is a file that portage will pass to rsync when it updates |
360 |
# the portage tree. Specific chunks of the tree may be excluded from |
361 |
# consideration. This may cause dependency failures if you are not careful. |
362 |
# The file format is one pattern per line, blanks and ';' or '#' lines are |
363 |
# comments. See 'man rsync' for more details on the exclude-from format. |
364 |
#RSYNC_EXCLUDEFROM=/etc/portage/rsync_excludes |
365 |
|
366 |
# PP 041106 : 1 line commented : |
367 |
# 'man make.conf' : /etc KDE protected by dft |
368 |
#CONFIG_PROTECT="/etc /usr/share /usr/kde" |
369 |
|
370 |
# PP 060402 : 1 line added fr emerge output : |
371 |
EMERGE_DEFAULT_OPTS="--alphabetical" |
372 |
|
373 |
# PP 060627 : 2 lines fr .example |
374 |
PORTAGE_ELOG_CLASSES="info warn error log" |
375 |
PORTAGE_ELOG_SYSTEM="save" |
376 |
|
377 |
-- |
378 |
========================,,============================================ |
379 |
SUPPORT ___________//___, Philip Webb : purslow@××××××××××××××.ca |
380 |
ELECTRIC /] [] [] [] [] []| Centre for Urban & Community Studies |
381 |
TRANSIT `-O----------O---' University of Toronto |
382 |
-- |
383 |
gentoo-user@g.o mailing list |