pkgsrc-Changes-HG archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
[pkgsrc/trunk]: pkgsrc/doc regen.
details: https://anonhg.NetBSD.org/pkgsrc/rev/28889b811e0c
branches: trunk
changeset: 508973:28889b811e0c
user: rillig <rillig%pkgsrc.org@localhost>
date: Wed Mar 01 17:22:08 2006 +0000
description:
regen.
diffstat:
doc/pkgsrc.html | 378 ++++++++++++++++++++++++++++++++++++++++---------------
doc/pkgsrc.txt | 171 ++++++++++++++++++-------
2 files changed, 398 insertions(+), 151 deletions(-)
diffs (truncated from 725 to 300 lines):
diff -r a9b49e0adcc2 -r 28889b811e0c doc/pkgsrc.html
--- a/doc/pkgsrc.html Wed Mar 01 17:16:21 2006 +0000
+++ b/doc/pkgsrc.html Wed Mar 01 17:22:08 2006 +0000
@@ -180,18 +180,17 @@
<dd>
<dl>
- <dt><span class="sect1"><a href=
- "#getting-started">4.1. Working with binary
- packages</a></span></dt>
+ <dt><span class="sect1"><a href="#using-pkg">4.1.
+ Using binary packages</a></span></dt>
<dd>
<dl>
<dt><span class="sect2"><a href=
- "#where-to-get-binary-packages">4.1.1. Where to
- get binary packages</a></span></dt>
-
- <dt><span class="sect2"><a href=
- "#how-to-use-binary-packages">4.1.2. How to use
+ "#finding-binary-packages">4.1.1. Finding
+ binary packages</a></span></dt>
+
+ <dt><span class="sect2"><a href=
+ "#installing-binary-packages">4.1.2. Installing
binary packages</a></span></dt>
<dt><span class="sect2"><a href=
@@ -1223,7 +1222,7 @@
<li>
<p><a href="http://www.DragonFlyBSD.org/"; target=
- "_top">DragonFlyBSD</a></p>
+ "_top">DragonFly BSD</a></p>
</li>
<li>
@@ -1514,18 +1513,17 @@
<dd>
<dl>
- <dt><span class="sect1"><a href=
- "#getting-started">4.1. Working with binary
- packages</a></span></dt>
+ <dt><span class="sect1"><a href="#using-pkg">4.1.
+ Using binary packages</a></span></dt>
<dd>
<dl>
<dt><span class="sect2"><a href=
- "#where-to-get-binary-packages">4.1.1. Where to
- get binary packages</a></span></dt>
-
- <dt><span class="sect2"><a href=
- "#how-to-use-binary-packages">4.1.2. How to use
+ "#finding-binary-packages">4.1.1. Finding binary
+ packages</a></span></dt>
+
+ <dt><span class="sect2"><a href=
+ "#installing-binary-packages">4.1.2. Installing
binary packages</a></span></dt>
<dt><span class="sect2"><a href=
@@ -1958,7 +1956,7 @@
</li>
<li>
- <p>DragonFlyBSD</p>
+ <p>DragonFly BSD</p>
</li>
<li>
@@ -2883,6 +2881,14 @@
<span class="emphasis"><em>not</em></span>
supported.</p>
+ <p>Whichever compiler you use, please ensure the
+ compiler tools and your $prefix are in your
+ <code class="varname">PATH</code>. This includes
+ <code xmlns="http://www.w3.org/TR/xhtml1/transitional";
+ class="filename">/usr/ccs/{bin,lib}</code> and e.g.
+ <code xmlns="http://www.w3.org/TR/xhtml1/transitional";
+ class="filename">/usr/pkg/{bin,sbin}</code>.</p>
+
<div class="sect3" lang="en">
<div class="titlepage">
<div>
@@ -2960,22 +2966,6 @@
CXX= CC
CPP= /usr/ccs/lib/cpp
</pre>
-
- <p>You may also want to build 64-bit binaries,
- e.g.:</p>
- <pre class="programlisting">
- CFLAGS= -xtarget=ultra -xarch=v9
-</pre>
-
- <p>Whichever compiler you use, please ensure the
- compiler tools and your $prefix are in your
- <code class="varname">PATH</code>. This includes
- <code xmlns=
- "http://www.w3.org/TR/xhtml1/transitional"; class=
- "filename">/usr/ccs/{bin,lib}</code> and e.g.
- <code xmlns=
- "http://www.w3.org/TR/xhtml1/transitional"; class=
- "filename">/usr/pkg/{bin,sbin}</code>.</p>
</div>
<div class="sect3" lang="en">
@@ -2983,7 +2973,89 @@
<div>
<div>
<h4 class="title"><a name=
- "plat.sunos.problems"></a>3.2.7.3. Common
+ "solaris-sunpro-64"></a>3.2.7.3. Buildling
+ 64-bit binaries with SunPro</h4>
+ </div>
+ </div>
+ </div>
+
+ <p>Building 64-bit binaries is a little trickier.
+ First, you need to bootstrap pkgsrc in 64-bit mode.
+ One problem here is that while building one of the
+ programs in the bootstrap kit (<code xmlns=
+ "http://www.w3.org/TR/xhtml1/transitional"; class=
+ "filename">bmake</code>), the <code class=
+ "varname">CFLAGS</code> variable is not honored, even
+ if it is set in the environment. To work around this
+ bug, you can create a simple shell script called
+ <code xmlns=
+ "http://www.w3.org/TR/xhtml1/transitional"; class=
+ "filename">cc64</code> and put it somewhere in the
+ <code class="varname">PATH</code>:</p>
+ <pre class="programlisting">
+ #! /bin/sh
+ exec /opt/SUNWspro/bin/cc -xtarget=ultra -xarch=v9 ${1+"$@"}
+</pre>
+
+ <p>Then, pass the definition for <code class=
+ "varname">CC</code> in the environment of the
+ <span><strong class=
+ "command">bootstrap</strong></span> command:</p>
+ <pre class="programlisting">
+ <code class="prompt">$</code> <strong class=
+"userinput"><code>cd bootstrap</code></strong>
+ <code class="prompt">$</code> <strong class=
+"userinput"><code>CC=cc64 ./bootstrap</code></strong>
+</pre>
+
+ <p>After bootstrapping, there are two alternative
+ ways, depending on whether you want to find bugs in
+ packages or get your system ready quickly. If you
+ just want a running system, add the following lines
+ to your <code xmlns=
+ "http://www.w3.org/TR/xhtml1/transitional"; class=
+ "filename">mk.conf</code> file:</p>
+ <pre class="programlisting">
+ CC= cc64
+ CXX= CC64
+ PKGSRC_COMPILER= sunpro
+</pre>
+
+ <p>This way, all calls to the compiler will be
+ intercepted by the above wrapper and therefore get
+ the necessary ABI options automatically. (Don't
+ forget to create the shell script <code xmlns=
+ "http://www.w3.org/TR/xhtml1/transitional"; class=
+ "filename">CC64</code>, too.)</p>
+
+ <p>To find packages that ignore the user-specified
+ <code class="varname">CFLAGS</code> and <code class=
+ "varname">CXXFLAGS</code>, add the following lines to
+ your <code xmlns=
+ "http://www.w3.org/TR/xhtml1/transitional"; class=
+ "filename">mk.conf</code> file:</p>
+ <pre class="programlisting">
+ CC= cc
+ CXX= CC
+ PKGSRC_COMPILER= sunpro
+ CFLAGS= -xtarget=ultra -xarch=v9
+ CXXFLAGS= -xtarget=ultra -xarch=v9
+ LDFLAGS= -xtarget=ultra -xarch=v9
+</pre>
+
+ <p>Packages that don't use the flags provided in the
+ configuration file will try to build 32-bit binaries
+ and fail during linking. Detecting this is useful to
+ prevent bugs on other platforms where the error would
+ not show up but pass silently.</p>
+ </div>
+
+ <div class="sect3" lang="en">
+ <div class="titlepage">
+ <div>
+ <div>
+ <h4 class="title"><a name=
+ "plat.sunos.problems"></a>3.2.7.4. Common
problems</h4>
</div>
</div>
@@ -3026,17 +3098,17 @@
<p><b>Table of Contents</b></p>
<dl>
- <dt><span class="sect1"><a href="#getting-started">4.1.
- Working with binary packages</a></span></dt>
+ <dt><span class="sect1"><a href="#using-pkg">4.1. Using
+ binary packages</a></span></dt>
<dd>
<dl>
<dt><span class="sect2"><a href=
- "#where-to-get-binary-packages">4.1.1. Where to get
- binary packages</a></span></dt>
-
- <dt><span class="sect2"><a href=
- "#how-to-use-binary-packages">4.1.2. How to use
+ "#finding-binary-packages">4.1.1. Finding binary
+ packages</a></span></dt>
+
+ <dt><span class="sect2"><a href=
+ "#installing-binary-packages">4.1.2. Installing
binary packages</a></span></dt>
<dt><span class="sect2"><a href=
@@ -3070,69 +3142,161 @@
</dl>
</div>
- <div class="sect1" lang="en">
- <div class="titlepage">
- <div>
- <div>
- <h2 class="title" style="clear: both"><a name=
- "getting-started"></a>4.1. Working with binary
+ <p>Basically, there are two ways of using pkgsrc. The first
+ is to only install the package tools and to use binary
+ packages that someone else has prepared. This is the
+ “<span class="quote">pkg</span>” in pkgsrc. The
+ second way is to install the “<span class=
+ "quote">src</span>” of pkgsrc, too. Then you are able
+ to build your own packages, and you can still use binary
+ packages from someone else.</p>
+
+ <div class="sect1" lang="en">
+ <div class="titlepage">
+ <div>
+ <div>
+ <h2 class="title" style="clear: both"><a name=
+ "using-pkg"></a>4.1. Using binary
packages</h2>
</div>
</div>
</div>
- <p>This section describes how to find, retrieve and
- install a precompiled binary package that someone else
- already prepared for your type of machine.</p>
-
- <div class="sect2" lang="en">
- <div class="titlepage">
- <div>
- <div>
- <h3 class="title"><a name=
- "where-to-get-binary-packages"></a>4.1.1. Where
- to get binary packages</h3>
- </div>
- </div>
- </div>
-
- <p>Precompiled packages are stored on ftp.NetBSD.org
- and its mirrors in the directory <code xmlns=
- "http://www.w3.org/TR/xhtml1/transitional"; class=
- "filename">/pub/NetBSD/packages/<OSVERSION>/<ARCH>/</code>
- for anonymous FTP access. <code class=
- "varname">OSVERSION</code> is the NetBSD version
- (<span><strong class="command">uname
- -r</strong></span>), <code class="varname">ARCH</code>
- is the architecture (<span><strong class=
- "command">uname -p</strong></span>). In that directory,
- there is a subdirectory for each category plus a
+ <p>To use binary packages, you need some tools to manage
+ them. On NetBSD, these tools are already installed. On
+ all other operating systems, you need to install them
+ first. For the following platforms, prebuilt versions of
+ the package tools are available and can simply be
+ downloaded and unpacked in the <code xmlns=
+ "http://www.w3.org/TR/xhtml1/transitional"; class=
+ "filename">/</code> directory:</p>
+
+ <div class="informaltable">
+ <a name="binary-bootstrap-kits"></a>
+
+ <table border="1">
+ <colgroup>
+ <col />
+ <col />
+ </colgroup>
Home |
Main Index |
Thread Index |
Old Index