Difference between pages "Make.conf" and "Test"

From Funtoo
(Difference between pages)
Jump to navigation Jump to search
m (add unpacking sources in ram, format with file template)
 
 
Line 1: Line 1:
== What is the make.conf file? What is its purpose? ==
== Badabing ==
Make.conf is portage's and Funtoo's main configuration file. It contains many variables that define how a package will installed in a Funtoo system. You can customize portage internal variables, such as, portage tree location, sources tarball location, overlays, to name a few. You can customize hardware specs, such as TMPFS, disk limits, GCC compilation flags to achieve best performance, etc. A great deal of this customization is done through the make.conf file. This page will attempt to explain the uses of the make.conf file, different variables that can be added to it, and their uses.


== Where does this file reside? ==
{{#ask: [[Category:Person]]
The <code>make.conf</code> file is found at <code>/etc/portage/make.conf</code> and <code>/etc/make.conf</code> though <code>/etc/make.conf</code> is its deprecated location.
| limit=20
| order=random
}}


to edit:
== Table test ==
<console>
<div class="table-responsive"><table class="table"><tr><td>Hello</td></tr><tr><td>Hello</td></tr><tr><td>Hello</td></tr></table></div>
###i## nano /etc/portage/make.conf
</console>


== Variables ==
== Testing error on Show ==


{{file|name=/etc/portage/make.conf|lang=|desc=example make.conf variables|body=
* {{#show:User:JanZhou|?full name}}
* CFLAGS="-march=amdfam10 -O2 -pipe"
* {{#show:User:Drobbins|?full name}}
* CXXFLAGS="-march=amdfam10 -O2 -pipe"
 
* INPUT_DEVICES="evdev"
 
* VIDEO_CARDS="vesa nouveau"
{{DISPLAYTITLE:Bob Boblaw}}
* MAKEOPTS="-j 2"
[[Category:Test]]
* USE="mmx sse"
 
* PYTHON_ABIS="2.7 3.3"
Adding some text
* PYTHON_TARGETS="2.7 3.3"
* RUBY_TARGETS="ruby21"
* ACCEPT_LICENSE="*"
}}


== Compile Packages in RAM ==
== Testing External Data ==
To use tmpfs to unpack sources in ram:


{{file|name=/etc/portage/make.conf|lang=|desc=unpack sources in ram|body=
PORTAGE_TMPDIR="/run"
}}


== Video_Cards ==
{{#get_web_data:url=http://auth.funtoo.org:9093/static/members.xml|format=xml|use xpath|data=ircnick=/members/user/ircnick,fullname=/members/user/fullname}}


several options for the video cards variable exist.  see [[Video]]
{{#display_external_table:template=MemberDisplay|data=ircnick,fullname}}


== Makeopts ==
Daniel Robbins:drobbins:bdfl
MAKEOPTS can be used to define how many parallel compilations should occur when you compile a package, which can speed up compilation significantly. A rule of thumb is the number of CPUs (or CPU threads) in your system plus one. If for example you have a dual core processor without [[wikipedia:Hyper-threading|hyper-threading]], then you would set MAKEOPTS to 3:


{{file|name=/etc/portage/make.conf|lang=|desc=set portage to use 3 threads|body=
{{file|name=foobar|lang=python|desc=foobarosity|body=
MAKEOPTS="-j3"
import system
}}
}}


If you are unsure about how many processors/threads you have then use /proc/cpuinfo to help you.
{{file|name=/etc/foo.conf|desc=My foo.conf file|body=
<console>
# /etc/host.conf:
(chroot) # ##i##grep "processor" /proc/cpuinfo | wc -l
# $Header: /var/cvsroot/gentoo/src/patchsets/glibc/extra/etc/host.conf,v 1.1 2006/09/29 23:52:23 vapier Exp $
16
 
</console>
# The  file /etc/host.conf contains configuration information specific to
# the resolver library.  It should contain one configuration keyword  per
# line,  followed by appropriate configuration information.  The keywords
# recognized are order, trim, mdns, multi, nospoof, spoof, and reorder.


Set MAKEOPTS to this number plus one:


{{file|name=/etc/portage/make.conf|lang=|desc=set portage to use 17 threads|body=
MAKEOPTS="-j17"
}}


USE flags define what functionality is enabled when packages are built. It is not recommended to add a lot of them during installation; you should wait until you have a working, bootable system before changing your USE flags. A USE flag prefixed with a minus ("<tt>-</tt>") sign tells Portage not to use the flag when compilingA Funtoo guide to USE flags will be available in the future. For now, you can find out more information about USE flags in the [http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?part=2&chap=2 Gentoo Handbook].
# This keyword specifies how host lookups are to be performed. It
# should be followed by one or more lookup methods, separated by
# commasValid methods are bind, hosts, and nis.
#
order hosts, bind


== Linguas ==
LINGUAS tells Portage which local language to compile the system and applications in (those who use LINGUAS variable like OpenOffice). It is not usually necessary to set this if you use English. If you want another language such as French (fr) or German (de), set LINGUAS appropriately:


{{file|name=/etc/portage/make.conf|lang=|desc=set system language to french|body=
# Valid  values are on and off.  If set to on, the resolv+ library
LINGUAS="fr"
# will return all valid addresses for a host that appears  in  the
# /etc/hosts  file,  instead  of  only  the first.  This is off by
# default, as it may cause a substantial performance loss at sites
# with large hosts files.
#
multi on
}}
}}
[[Category:System]]

Revision as of 02:50, September 24, 2014

Badabing

{{#ask: | limit=20 | order=random }}

Table test

Hello
Hello
Hello

Testing error on Show

  • {{#show:User:JanZhou|?full name}}
  • {{#show:User:Drobbins|?full name}}

Adding some text

Testing External Data

Error while fetching data from URL http://auth.funtoo.org:9093/static/members.xml: $2.
Error fetching URL: Failed to connect to auth.funtoo.org port 9093: Connection refused
There was a problem during the HTTP request: 0 Error
Could not get URL http://auth.funtoo.org:9093/static/members.xml after 3 tries.


Daniel Robbins:drobbins:bdfl

   foobar (python source code) - foobarosity
import system
   /etc/foo.conf - My foo.conf file
# /etc/host.conf:
# $Header: /var/cvsroot/gentoo/src/patchsets/glibc/extra/etc/host.conf,v 1.1 2006/09/29 23:52:23 vapier Exp $

# The  file /etc/host.conf contains configuration information specific to
# the resolver library.  It should contain one configuration keyword  per
# line,  followed by appropriate configuration information.  The keywords
# recognized are order, trim, mdns, multi, nospoof, spoof, and reorder.



# This keyword specifies how host lookups are to be performed. It
# should be followed by one or more lookup methods, separated by
# commas.  Valid methods are bind, hosts, and nis.
#
order hosts, bind


# Valid  values are on and off.  If set to on, the resolv+ library
# will return all valid addresses for a host that appears  in  the
# /etc/hosts  file,  instead  of  only  the first.  This is off by
# default, as it may cause a substantial performance loss at sites
# with large hosts files.
#
multi on