aboutsummaryrefslogtreecommitdiffstats
path: root/cnf/make.conf.example.ppc64.diff
diff options
context:
space:
mode:
authorBrian Dolbec <dolsen@gentoo.org>2014-03-26 06:52:42 -0700
committerBrian Dolbec <dolsen@gentoo.org>2014-03-26 06:52:42 -0700
commit276611668673967d8dd76caebb1e427dd10b3ff2 (patch)
tree479b3b5dccbc0dfd96c617908eb21946e6785eeb /cnf/make.conf.example.ppc64.diff
parentMerge branch 'master' of git+ssh://git.overlays.gentoo.org/proj/portage into public_api (diff)
downloadgentoo-portage-276611668673967d8dd76caebb1e427dd10b3ff2.tar.xz
gentoo-portage-276611668673967d8dd76caebb1e427dd10b3ff2.zip
Merge branch 'master' of git+ssh://git.overlays.gentoo.org/proj/portage into public_apipublic_api
Diffstat (limited to 'cnf/make.conf.example.ppc64.diff')
-rw-r--r--cnf/make.conf.example.ppc64.diff69
1 files changed, 69 insertions, 0 deletions
diff --git a/cnf/make.conf.example.ppc64.diff b/cnf/make.conf.example.ppc64.diff
new file mode 100644
index 000000000..961508e8f
--- /dev/null
+++ b/cnf/make.conf.example.ppc64.diff
@@ -0,0 +1,69 @@
+--- make.conf.example
++++ make.conf.example
+@@ -22,6 +22,13 @@
+ # Example:
+ #USE="X gtk gnome -alsa"
+
++# Host Setting
++# ============
++#
++# All PowerPC64 systems should use this host setting:
++
++CHOST="powerpc64-unknown-linux-gnu"
++
+ # Host and optimization settings
+ # ==============================
+ #
+@@ -39,9 +46,38 @@
+ # -frecord-gcc-switches, since otherwise the check could result in false
+ # positive results.
+ #
+-# Please refer to the GCC manual for a list of possible values.
++# -mtune=<cpu-type> for PowerPC64 systems instructs the gcc compiler that
++# it can use instruction scheduling specific for that type of processor
++# specified
++#
++# -mcpu=<cpu-type> for PowerPC64 systems selects the type of processor you want
++# to optimize your code for. Code generated under those options will run best
++# on that processor.
++#
++# -mcpu=<cpu-type> and -mtune=<cpu-type> should both be specified
++#
++# GCC 3.x supports many ppc64 processor types including: power3, power4,
++# 970 (aka G5), and power5.
++#
++# RS64 processors should specify power3.
+ #
+-#CFLAGS="-O2 -pipe"
++# Additional options of interest:
++#
++# -maltivec enables optional altivec support and should be used
++# only for 970 processors. It also requires that you have
++# the alitvec option compiled into your kernel to take full advantage of this
++# feature. Note: you should also include -mabi=altivec flag if using this option.
++#
++# -O3 for the most part seems ok but should be used with caution as
++# for instance app-editors/vim has problems if it is used. -O2 is a
++# good selection.
++#
++#Example CFLAGS setting
++#CFLAGS="-O2 -pipe -mcpu=970 -mtune=970 -maltivec -mabi=altivec"
++#
++#or
++#
++#CFLAGS="-O2 -pipe -mcpu=power3 -mtune=power3"
+ #
+ # If you set a CFLAGS above, then this line will set your default C++ flags to
+ # the same settings.
+@@ -76,7 +112,10 @@
+ # DO NOT PUT ANYTHING BUT YOUR SPECIFIC ~ARCHITECTURE IN THE LIST.
+ # IF YOU ARE UNSURE OF YOUR ARCH, OR THE IMPLICATIONS, DO NOT MODIFY THIS.
+ #
+-#ACCEPT_KEYWORDS="~arch"
++# Note: this really shouldn't be enabled until _AFTER_ you bootstrap and emerge
++# system. If you want the testing things update after these steps are completed.
++#
++#ACCEPT_KEYWORDS="ppc64"
+
+ # ACCEPT_LICENSE is used to mask packages based on licensing restrictions.
+ # It may contain both license and group names, where group names are