summaryrefslogtreecommitdiff
path: root/doc/guide
diff options
context:
space:
mode:
authorsevan <sevan@pkgsrc.org>2016-07-03 19:15:50 +0000
committersevan <sevan@pkgsrc.org>2016-07-03 19:15:50 +0000
commitcd141763e199542900d92ca0e82e5d17b7a33bac (patch)
treed6d473bd406f1efa1f5fd458c6737ef917471312 /doc/guide
parentf7dac646aee347ea6ffb90c8a61a2e3a282693bf (diff)
downloadpkgsrc-cd141763e199542900d92ca0e82e5d17b7a33bac.tar.gz
Remove Solaris section, bootstrap/README.Solaris provides extensive information
Diffstat (limited to 'doc/guide')
-rw-r--r--doc/guide/files/platforms.xml111
1 files changed, 1 insertions, 110 deletions
diff --git a/doc/guide/files/platforms.xml b/doc/guide/files/platforms.xml
index d2611eca435..305879cb20d 100644
--- a/doc/guide/files/platforms.xml
+++ b/doc/guide/files/platforms.xml
@@ -1,4 +1,4 @@
-<!-- $NetBSD: platforms.xml,v 1.95 2016/07/03 15:26:27 sevan Exp $ -->
+<!-- $NetBSD: platforms.xml,v 1.96 2016/07/03 19:15:50 sevan Exp $ -->
<chapter id="platforms">
<title>Using pkgsrc on systems other than &os;</title>
@@ -326,114 +326,5 @@ ICCBASE= /opt/intel/cc/10.1.008
libtool.</para>
</sect2>
-
- <sect2 id="solaris">
- <title>Solaris</title>
-
- <para>Solaris 2.6 through 10 are supported on both x86 and sparc.
- You will need a working C compiler. Both gcc 4.5.3 and
- Sun WorkShop 5 have been tested.</para>
-
- <para>The following packages are required on Solaris 8 for the bootstrap
- process and to build packages.</para>
-
- <itemizedlist>
- <listitem><para>SUNWsprot</para></listitem>
- <listitem><para>SUNWarc</para></listitem>
- <listitem><para>SUNWbtool</para></listitem>
- <listitem><para>SUNWtoo</para></listitem>
- <listitem><para>SUNWlibm</para></listitem>
- </itemizedlist>
-
- <para>Please note that the use of GNU binutils on Solaris is
- <emphasis>not</emphasis> supported, as of June 2006.</para>
-
- <para>Whichever compiler you use, please ensure the compiler tools and
- your $prefix are in your <varname>PATH</varname>. This includes
- <filename>/usr/ccs/{bin,lib}</filename>
- and e.g. <filename>/usr/pkg/{bin,sbin}</filename>.</para>
-
- <sect3 id="solaris-gcc-note">
- <title>If you are using gcc</title>
-
- <para>It makes life much simpler if you only use the same gcc consistently
- for building all packages.</para>
-
- <para>It is recommended that an external gcc be used only for bootstrapping,
- then either build gcc from
- <filename role="pkg">lang/gcc46</filename> or install a binary gcc
- package, then remove gcc used during bootstrapping.</para>
-
- <para>Binary packages of gcc can be found through <ulink
- url="http://www.sunfreeware.com/"/>.</para>
- </sect3>
-
- <sect3 id="solaris-sun-workshop-note">
- <title>If you are using Sun WorkShop</title>
-
- <para>You will need at least the following packages installed (from WorkShop
- 5.0)</para>
-
- <itemizedlist>
- <listitem><para>SPROcc
- - Sun WorkShop Compiler C 5.0</para></listitem>
- <listitem><para>SPROcpl
- - Sun WorkShop Compiler C++ 5.0</para></listitem>
- <listitem><para>SPROild
- - Sun WorkShop Incremental Linker</para></listitem>
- <listitem><para>SPROlang
- - Sun WorkShop Compilers common components</para></listitem>
- </itemizedlist>
-
- <para>You should set the following variables in your
- &mk.conf; file:</para>
-
-<programlisting>
-CC= cc
-CXX= CC
-CPP= cc -E
-CXXCPP= CC -E
-</programlisting>
-
- <note><para>The <varname>CPP</varname> setting might break some
- packages that use the C preprocessor for processing things other
- than C source code.</para></note>
-
- </sect3>
- <sect3 id="solaris-sunpro-64">
- <title>Building 64-bit binaries with SunPro</title>
-
- <para>To build 64-bit packages, you just need to have the
- following lines in your &mk.conf; file:</para>
-
-<programlisting>
-PKGSRC_COMPILER= sunpro
-ABI= 64
-</programlisting>
-
- <note><para>This setting has been tested for the SPARC
- architecture. Intel and AMD machines need some more
- work.</para></note>
-
- </sect3>
- <sect3 id="plat.sunos.problems"><title>Common problems</title>
-
- <para>Sometimes, when using <command>libtool</command>,
- <filename>/bin/ksh</filename> crashes with a segmentation fault.
- The workaround is to use another shell for the configure
- scripts, for example by installing <filename
- role="pkg">shells/bash</filename> and adding the following lines
- to your &mk.conf;:</para>
-
- <programlisting>
-CONFIG_SHELL= ${LOCALBASE}/bin/bash
-WRAPPER_SHELL= ${LOCALBASE}/bin/bash
- </programlisting>
-
- <para>Then, rebuild the <filename
- role="pkg">devel/libtool-base</filename> package.</para>
-
- </sect3>
- </sect2>
</sect1>
</chapter>