Annotation of htdocs/docs/pkgsrc/platforms.html, revision 1.3
1.1 dsieger 1: <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
2: <html>
3: <head>
4: <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
5: <title>Chapter 3. Using pkgsrc on systems other than NetBSD</title>
1.2 rillig 6: <link rel="stylesheet" href="/global.css" type="text/css">
1.1 dsieger 7: <meta name="generator" content="DocBook XSL Stylesheets VX.X.X">
8: <link rel="start" href="index.html" title="The pkgsrc guide">
9: <link rel="up" href="users-guide.html" title="Part I. The pkgsrc user's guide">
10: <link rel="prev" href="getting.html" title="Chapter 2. Where to get pkgsrc and how to keep it up-to-date">
11: <link rel="next" href="using.html" title="Chapter 4. Using pkgsrc">
12: </head>
13: <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
14: <div class="navheader">
15: <table width="100%" summary="Navigation header">
16: <tr><th colspan="3" align="center">Chapter 3. Using pkgsrc on systems other than NetBSD</th></tr>
17: <tr>
18: <td width="20%" align="left">
19: <a accesskey="p" href="getting.html">Prev</a> </td>
20: <th width="60%" align="center">Part I. The pkgsrc user's guide</th>
21: <td width="20%" align="right"> <a accesskey="n" href="using.html">Next</a>
22: </td>
23: </tr>
24: </table>
25: <hr>
26: </div>
27: <div class="chapter" lang="en">
28: <div class="titlepage"><div><div><h2 class="title">
29: <a name="platforms"></a>Chapter 3. Using pkgsrc on systems other than NetBSD</h2></div></div></div>
30: <div class="toc">
31: <p><b>Table of Contents</b></p>
32: <dl>
33: <dt><span class="sect1"><a href="platforms.html#binarydist">3.1. Binary distribution</a></span></dt>
34: <dt><span class="sect1"><a href="platforms.html#bootstrapping-pkgsrc">3.2. Bootstrapping pkgsrc</a></span></dt>
35: <dt><span class="sect1"><a href="platforms.html#platform-specific-notes">3.3. Platform-specific notes</a></span></dt>
36: <dd><dl>
37: <dt><span class="sect2"><a href="platforms.html#darwin">3.3.1. Darwin (Mac OS X)</a></span></dt>
38: <dt><span class="sect2"><a href="platforms.html#freebsd">3.3.2. FreeBSD</a></span></dt>
39: <dt><span class="sect2"><a href="platforms.html#interix">3.3.3. Interix</a></span></dt>
40: <dt><span class="sect2"><a href="platforms.html#irix">3.3.4. IRIX</a></span></dt>
41: <dt><span class="sect2"><a href="platforms.html#linux">3.3.5. Linux</a></span></dt>
42: <dt><span class="sect2"><a href="platforms.html#openbsd">3.3.6. OpenBSD</a></span></dt>
43: <dt><span class="sect2"><a href="platforms.html#solaris">3.3.7. Solaris</a></span></dt>
44: </dl></dd>
45: </dl>
46: </div>
47: <div class="sect1" lang="en">
48: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
49: <a name="binarydist"></a>3.1. Binary distribution</h2></div></div></div>
50: <p>
51: We provide a bootstrap kit in both source and binary form for other
52: platforms than NetBSD, consisting of the pkg administration tools and other
53: tools required to use pkgsrc and build packages.
54: </p>
55: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
56: <h3 class="title">Note</h3>
57: <p>
58: Older binary snapshots are available in the
59: <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/packages/bootstrap-pkgsrc/archive/" target="_top">bootstrap-pkgsrc/archive</a>
60: directory on ftp.NetBSD.org.</p>
61: </div>
62: <div class="table">
63: <a name="binary-kits"></a><p class="title"><b>Table 3.1. Binary kits and available packages</b></p>
64: <div class="table-contents"><table summary="Binary kits and available packages" border="1">
65: <colgroup>
66: <col>
67: <col>
68: <col>
69: <col>
70: </colgroup>
71: <thead><tr>
72: <th>Platform</th>
73: <th>Latest snapshot</th>
74: <th>Binary kit</th>
75: <th>Binary packages</th>
76: </tr></thead>
77: <tbody>
78: <tr>
79: <td class="osname">Darwin 5.5/powerpc (Mac OS X 10.1.5)</td>
80: <td class="date">20021209</td>
81: <td class="kit-url"><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/packages/bootstrap-pkgsrc/bootstrap-pkgsrc-Darwin-5.5-powerpc-20021209.tar.gz" target="_top">binary kit</a></td>
82: <td class="binary-pkgs-url"> </td>
83: </tr>
84: <tr>
85: <td class="osname">Darwin 6.6/powerpc (Mac OS X 10.2.6)</td>
86: <td class="date">20030623</td>
87: <td class="kit-url"><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/packages/bootstrap-pkgsrc/bootstrap-pkgsrc-Darwin-6.6-powerpc-20030623.tar.gz" target="_top">binary kit</a></td>
88: <td class="binary-pkgs-url"> </td>
89: </tr>
90: <tr>
91: <td class="osname">Darwin 7.6/powerpc (Mac OS X 10.3.6)</td>
92: <td class="date">20041219</td>
93: <td class="kit-url"><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/packages/bootstrap-pkgsrc/bootstrap-pkgsrc-Darwin-7.6.0-powerpc-20041219.tar.gz" target="_top">binary kit</a></td>
94: <td class="binary-pkgs-url"><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/packages/Darwin-7.6/" target="_top">binary packages</a></td>
95: </tr>
96: <tr>
97: <td class="osname">Darwin 7.8/powerpc (Mac OS X 10.3.8)</td>
98: <td class="date">20050320</td>
99: <td class="kit-url"><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/packages/bootstrap-pkgsrc/bootstrap-pkgsrc-Darwin-7.8.0-powerpc-20050320.tar.gz" target="_top">binary kit</a></td>
100: <td class="binary-pkgs-url"> </td>
101: </tr>
102: <tr>
103: <td class="osname">Darwin 8.1/powerpc (Mac OS X 10.4.1)</td>
104: <td class="date">20050625</td>
105: <td class="kit-url"><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/packages/bootstrap-pkgsrc/bootstrap-pkgsrc-Darwin-8.1.0-powerpc-20050625.tar.gz" target="_top">binary kit</a></td>
106: <td class="binary-pkgs-url"><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/packages/Darwin-8.1/powerpc/current/" target="_top">binary packages</a></td>
107: </tr>
108: <tr>
109: <td class="osname">Debian GNU Linux/i386</td>
110: <td class="date">20031023</td>
111: <td class="kit-url"><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/packages/bootstrap-pkgsrc/bootstrap-pkgsrc-Linux-2.4.22-debian-i386-20031023.tar.gz" target="_top">binary kit</a></td>
112: <td class="binary-pkgs-url"> </td>
113: </tr>
114: <tr>
115: <td class="osname">Fedora Core 2 Linux/i386</td>
116: <td class="date">20050618</td>
117: <td class="kit-url"><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/packages/bootstrap-pkgsrc/bootstrap-pkgsrc-Linux-2.6.10-i386-fc2-20050618.tar.gz" target="_top">binary kit</a></td>
118: <td class="binary-pkgs-url"> </td>
119: </tr>
120: <tr>
121: <td class="osname">Fedora Core 4 Linux/i386</td>
122: <td class="date">20060105</td>
123: <td class="kit-url"><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/packages/bootstrap-pkgsrc/bootstrap-pkgsrc-Linux-2.6.11-i386-fc4-20060105.tar.gz" target="_top">binary kit</a></td>
124: <td class="binary-pkgs-url"> </td>
125: </tr>
126: <tr>
127: <td class="osname">FreeBSD 3.5/i386</td>
128: <td class="date">20030411</td>
129: <td class="kit-url"><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/packages/bootstrap-pkgsrc/bootstrap-pkgsrc-FreeBSD-3.5-STABLE-i386-20030411.tar.gz" target="_top">binary kit</a></td>
130: <td class="binary-pkgs-url"> </td>
131: </tr>
132: <tr>
133: <td class="osname">FreeBSD 4.7/i386</td>
134: <td class="date">20021211</td>
135: <td class="kit-url"><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/packages/bootstrap-pkgsrc/bootstrap-pkgsrc-FreeBSD-4.7-RELEASE-i386-20021211.tar.gz" target="_top">binary kit</a></td>
136: <td class="binary-pkgs-url"> </td>
137: </tr>
138: <tr>
139: <td class="osname">FreeBSD 5.0/i386</td>
140: <td class="date">20030411</td>
141: <td class="kit-url"><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/packages/bootstrap-pkgsrc/bootstrap-pkgsrc-FreeBSD-5.0-RELEASE-i386-20030411.tar.gz" target="_top">binary kit</a></td>
142: <td class="binary-pkgs-url"> </td>
143: </tr>
144: <tr>
145: <td class="osname">FreeBSD 5.1/i386</td>
146: <td class="date">20030630</td>
147: <td class="kit-url"><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/packages/bootstrap-pkgsrc/bootstrap-pkgsrc-FreeBSD-5.1-RELEASE-i386-20030630.tar.gz" target="_top">binary kit</a></td>
148: <td class="binary-pkgs-url"> </td>
149: </tr>
150: <tr>
151: <td class="osname">FreeBSD 5.2.1/i386</td>
152: <td class="date">20040227</td>
153: <td class="kit-url"><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/packages/bootstrap-pkgsrc/bootstrap-pkgsrc-FreeBSD-5.2.1-RELEASE-i386-20040227.tar.gz" target="_top">binary kit</a></td>
154: <td class="binary-pkgs-url"> </td>
155: </tr>
156: <tr>
157: <td class="osname">FreeBSD 5.3/i386</td>
158: <td class="date">20050119</td>
159: <td class="kit-url"><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/packages/bootstrap-pkgsrc/bootstrap-pkgsrc-FreeBSD-5.3-RELEASE-i386-20050119.tar" target="_top">binary kit</a></td>
160: <td class="binary-pkgs-url"> </td>
161: </tr>
162: <tr>
163: <td class="osname">HP-UX 11.11/hppa</td>
164: <td class="date">20070421</td>
165: <td class="kit-url"><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/packages/bootstrap-pkgsrc/bootstrap-pkgsrc-HPUX-B.11.11-hppa-20070421.tar.gz" target="_top">binary kit</a></td>
166: <td class="binary-pkgs-url"> </td>
167: </tr>
168: <tr>
169: <td class="osname">Interix 3.5</td>
170: <td class="date">20061106</td>
171: <td class="kit-url"><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/packages/bootstrap-pkgsrc/bootstrap-pkgsrc-Interix-3.5-i386-20061106.tar.gz" target="_top">binary kit</a></td>
172: <td class="binary-pkgs-url"> </td>
173: </tr>
174: <tr>
175: <td class="osname">IRIX 6.5 n32-bit ABI</td>
176: <td class="date">20040911</td>
177: <td class="kit-url"><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/packages/bootstrap-pkgsrc/bootstrap-pkgsrc-IRIX-6.5-mips-20040911.tar.gz" target="_top">binary kit</a></td>
178: <td class="binary-pkgs-url"><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/packages/IRIX-6.5/n32/" target="_top">binary packages</a></td>
179: </tr>
180: <tr>
181: <td class="osname">IRIX 6.5 64-bit ABI</td>
182: <td class="date">20040912</td>
183: <td class="kit-url"><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/packages/bootstrap-pkgsrc/bootstrap-pkgsrc-IRIX64-6.5-mips-20040912.tar.gz" target="_top">binary kit</a></td>
184: <td class="binary-pkgs-url"><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/packages/IRIX-6.5/64/" target="_top">binary packages</a></td>
185: </tr>
186: <tr>
187: <td class="osname">OpenBSD 3.2/i386</td>
188: <td class="date">20030420</td>
189: <td class="kit-url"><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/packages/bootstrap-pkgsrc/bootstrap-pkgsrc-OpenBSD-3.2-i386-20030420.tar.gz" target="_top">binary kit</a></td>
190: <td class="binary-pkgs-url"> </td>
191: </tr>
192: <tr>
193: <td class="osname">OpenBSD 3.3/i386</td>
194: <td class="date">20030503</td>
195: <td class="kit-url"><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/packages/bootstrap-pkgsrc/bootstrap-pkgsrc-OpenBSD-3.3-i386-20030503.tar.gz" target="_top">binary kit</a></td>
196: <td class="binary-pkgs-url"> </td>
197: </tr>
198: <tr>
199: <td class="osname">OpenBSD 3.5/i386</td>
200: <td class="date">20040703</td>
201: <td class="kit-url"><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/packages/bootstrap-pkgsrc/bootstrap-pkgsrc-OpenBSD-3.5-i386-20040703.tar.gz" target="_top">binary kit</a></td>
202: <td class="binary-pkgs-url"> </td>
203: </tr>
204: <tr>
205: <td class="osname">OSF1 5.1/alpha</td>
206: <td class="date">20070420</td>
207: <td class="kit-url"><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/packages/bootstrap-pkgsrc/bootstrap-pkgsrc-OSF1-V5.1-alpha-20070420.tar.gz" target="_top">binary kit</a></td>
208: <td class="binary-pkgs-url"> </td>
209: </tr>
210: <tr>
211: <td class="osname">Slackware Linux 8.1/i386</td>
212: <td class="date">20030417</td>
213: <td class="kit-url"><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/packages/bootstrap-pkgsrc/bootstrap-pkgsrc-Linux-2.4.18-slackware-20030417.tar.gz" target="_top">binary kit</a></td>
214: <td class="binary-pkgs-url"> </td>
215: </tr>
216: <tr>
217: <td class="osname">Slackware Linux 9/i386</td>
218: <td class="date">20040703</td>
219: <td class="kit-url"><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/packages/bootstrap-pkgsrc/bootstrap-pkgsrc-Linux-2.4.22-i386-slackware9-20040703.tar.gz" target="_top">binary kit</a></td>
220: <td class="binary-pkgs-url"> </td>
221: </tr>
222: <tr>
223: <td class="osname">Solaris 8/sparc</td>
224: <td class="date">20050220</td>
225: <td class="kit-url"><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/packages/bootstrap-pkgsrc/bootstrap-pkgsrc-SunOS-5.8-sparc-20050220.tar.gz" target="_top">binary kit</a></td>
226: <td class="binary-pkgs-url"> </td>
227: </tr>
228: <tr>
229: <td class="osname">Solaris 8/i386</td>
230: <td class="date">20050220</td>
231: <td class="kit-url"><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/packages/bootstrap-pkgsrc/bootstrap-pkgsrc-SunOS-5.8-i386-20050220.tar.gz" target="_top">binary kit</a></td>
232: <td class="binary-pkgs-url"> </td>
233: </tr>
234: <tr>
235: <td class="osname">Solaris 9/sparc</td>
236: <td class="date">20060713</td>
237: <td class="kit-url"><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/packages/bootstrap-pkgsrc/bootstrap-pkgsrc-SunOS-5.9-sparc-pkgsrc-2006Q2.tar.gz" target="_top">binary kit</a></td>
238: <td class="binary-pkgs-url"> </td>
239: </tr>
240: <tr>
241: <td class="osname">Solaris 9/i386</td>
242: <td class="date">20030411</td>
243: <td class="kit-url"><a href="ftp://ftp.NetBSD.org/pub/pkgsrc/packages/bootstrap-pkgsrc/bootstrap-pkgsrc-SunOS-5.9-i386-20030411.tar.gz" target="_top">binary kit</a></td>
244: <td class="binary-pkgs-url"> </td>
245: </tr>
246: </tbody>
247: </table></div>
248: </div>
249: <br class="table-break"><p>
250: Simply download the binary kit for your platform, and extract it into
251: <code class="filename">/</code> e.g.
252: </p>
253: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>cd /</code></strong>
254: <code class="prompt">#</code> <strong class="userinput"><code>gzip -c -d /tmp/bootstrap-pkgsrc-SunOS-5.9-sparc-20031023.tar.gz \
255: | tar -xpf -</code></strong></pre>
256: <p>
257: Of course, as with any binary distributions, you should verify the
258: checksum against the <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/packages/bootstrap-pkgsrc/SUM" target="_top">SUM</a>
259: or <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/packages/bootstrap-pkgsrc/CKSUM" target="_top">CKSUM</a>
260: file and inspect the contents before extracting it.
261: </p>
262: </div>
263: <div class="sect1" lang="en">
264: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
265: <a name="bootstrapping-pkgsrc"></a>3.2. Bootstrapping pkgsrc</h2></div></div></div>
266: <p>Installing the bootstrap kit from source should be as simple as:</p>
267: <pre class="screen">
268: <code class="prompt">#</code> <strong class="userinput"><code>env CVS_RSH=ssh cvs -d anoncvs@anoncvs.NetBSD.org:/cvsroot checkout pkgsrc</code></strong>
269: <code class="prompt">#</code> <strong class="userinput"><code>cd pkgsrc/bootstrap</code></strong>
270: <code class="prompt">#</code> <strong class="userinput"><code>./bootstrap</code></strong>
271: </pre>
272: <p>See <a href="getting.html" title="Chapter 2. Where to get pkgsrc and how to keep it up-to-date">Chapter 2, <i>Where to get pkgsrc and how to keep it up-to-date</i></a> for other ways to get
273: pkgsrc before bootstrapping. The given
274: <span><strong class="command">bootstrap</strong></span> command will use the defaults of
275: <code class="filename">/usr/pkg</code> for the
276: <span class="emphasis"><em>prefix</em></span> where programs will be installed in,
277: and <code class="filename">/var/db/pkg</code> for the package database
278: directory where pkgsrc will do its internal bookkeeping.
279: However, these can also be set using command-line
280: arguments.</p>
281: <p>Binary packages for the pkgsrc tools and an initial set of packages is
282: available for supported platforms. An up-to-date list of these can be
283: found on <a href="http://www.pkgsrc.org/" target="_top">www.pkgsrc.org</a>.
284: Note that this only works for privileged builds that install
285: into <code class="filename">/usr/pkg</code>.</p>
286: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
287: <h3 class="title">Note</h3>
288: <p>The bootstrap installs a <span><strong class="command">bmake</strong></span> tool.
289: Use this <span><strong class="command">bmake</strong></span> when building via pkgsrc.
290: For examples in this guide, use <span><strong class="command">bmake</strong></span>
291: instead of “<span class="quote">make</span>”.</p>
292: </div>
293: </div>
294: <div class="sect1" lang="en">
295: <div class="titlepage"><div><div><h2 class="title" style="clear: both">
296: <a name="platform-specific-notes"></a>3.3. Platform-specific notes</h2></div></div></div>
297: <p>Here are some platform-specific notes you should be aware of.</p>
298: <div class="sect2" lang="en">
299: <div class="titlepage"><div><div><h3 class="title">
300: <a name="darwin"></a>3.3.1. Darwin (Mac OS X)</h3></div></div></div>
301: <p>Darwin 5.x and up are supported. There are two methods of using
302: pkgsrc on Mac OS X, by using a <a href="platforms.html#platform.osx-image" title="3.3.1.1. Using a disk image">disk
303: image</a>, or a <a href="platforms.html#platform.osx-part" title="3.3.1.2. Using a UFS or HFSX partition">UFS or HFSX
304: partition</a>.</p>
305: <p>Before you start, you will need to download and install the Mac OS X Developer
306: Tools from Apple's Developer Connection. See <a href="http://developer.apple.com/macosx/" target="_top">http://developer.apple.com/macosx/</a>
307: for details. Also, make sure you install X11 for Mac OS X and the X11 SDK
308: from <a href="http://www.apple.com/macosx/x11/download/" target="_top">http://www.apple.com/macosx/x11/download/</a>
309: if you intend to build packages that use the X11 Window System.</p>
310: <p>If you already have a UFS or HFSX partition, or have a spare partition
311: that you can format as UFS or HFSX, it is recommended to use that instead of
312: the disk image. It'll be somewhat faster and will mount automatically
313: at boot time, where you must manually mount a disk image.</p>
314: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
315: <h3 class="title">Note</h3>
316: <p>You cannot use an ordinary HFS+ file system for pkgsrc, because pkgsrc currently
317: requires the file system to be case-sensitive. You can, however, use a case-sensitive HFS+ (aka HFSX) file system as found in Darwin 7.0 and newer.</p>
318: </div>
319: <div class="sect3" lang="en">
320: <div class="titlepage"><div><div><h4 class="title">
321: <a name="platform.osx-image"></a>3.3.1.1. Using a disk image</h4></div></div></div>
322: <p>Create the disk image:</p>
323: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>cd pkgsrc/bootstrap</code></strong>
324: <code class="prompt">#</code> <strong class="userinput"><code>./darwindiskimage create ~/Documents/NetBSD 1024</code></strong> # megabytes - season to taste
325: <code class="prompt">#</code> <strong class="userinput"><code>./darwindiskimage mount ~/Documents/NetBSD</code></strong>
326: <code class="prompt">#</code> <strong class="userinput"><code>sudo chown `id -u`:`id -g` /Volumes/NetBSD</code></strong></pre>
327: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
328: <h3 class="title">Note</h3>
329: <p>darwindiskimage will mount the filesystem nosuid, which will cause problems for packages that depend on setgid. In the case of UFS, it will also mount the filesystem asynchronous, which is somewhat dangerous according to the mount(8) man page. In the case of HFSX, it will disable journalling.</p>
330: </div>
331: <p>Allow suid:</p>
332: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>sudo mount -u -o suid /Volumes/NetBSD</code></strong></pre>
333: </div>
334: <div class="sect3" lang="en">
335: <div class="titlepage"><div><div><h4 class="title">
336: <a name="platform.osx-part"></a>3.3.1.2. Using a UFS or HFSX partition</h4></div></div></div>
337: <p>By default, <code class="filename">/usr</code> will be on your root file
338: system, normally HFS+. It is possible to use the default
339: <span class="emphasis"><em>prefix</em></span> of <code class="filename">/usr/pkg</code>
340: by symlinking <code class="filename">/usr/pkg</code> to a directory on a UFS
341: or HFSX file system. Obviously, another symlink is required if you want to
342: place the package database directory outside the
343: <span class="emphasis"><em>prefix</em></span>. e.g.</p>
344: <pre class="screen"><code class="prompt">#</code> <strong class="userinput"><code>./bootstrap --pkgdbdir /usr/pkg/pkgdb</code></strong></pre>
345: <p>If you created your partitions at the time of installing Mac OS X
346: and formatted the target partition as UFS or HFSX, it should automatically
347: mount on <code class="filename">/Volumes/<volume name></code> when the
348: machine boots. If you are (re)formatting a partition as UFS or HFSX, you need
349: to ensure that the partition map correctly reflects
350: “<span class="quote">Apple_UFS</span>” or “<span class="quote">Apple_HFSX</span>” and not “<span class="quote">Apple_HFS</span>”.</p>
351: <p>The problem is that none of the disk tools will let you touch a
352: disk that is booted from. You can unmount the partition, but even if
353: you newfs it, the partition type will be incorrect and the
354: automounter won't mount it. It can be mounted manually, but it won't
355: appear in Finder.</p>
356: <p>You'll need to boot off of the OS X Installation (User) CD. When
357: the Installation program starts, go up to the menu and select Disk
358: Utility. Now, you will be able to select the partition you want
359: to be UFS or HFSX, and Format it Apple UFS or HFSX. Quit the Disk Utility, quit the
360: installer which will reboot your machine. The new UFS or HFSX file system
361: will appear in Finder.</p>
362: <p>Be aware that the permissions on the new file system will be writable
363: by root only.</p>
364: <p>This note is as of 10.2 (Jaguar) and applies to earlier versions.
365: Hopefully Apple will fix Disk Utility in 10.3 (Panther).</p>
366: </div>
367: </div>
368: <div class="sect2" lang="en">
369: <div class="titlepage"><div><div><h3 class="title">
370: <a name="freebsd"></a>3.3.2. FreeBSD</h3></div></div></div>
371: <p>FreeBSD 4.7 and 5.0 have been tested and are supported,
372: other versions may work.</p>
373: <p>Care should be taken so that the tools that this kit installs do not conflict
374: with the FreeBSD userland tools. There are several steps:</p>
375: <div class="orderedlist"><ol type="1">
376: <li><p>FreeBSD stores its ports pkg database in
377: <code class="filename">/var/db/pkg</code>. It is therefore
378: recommended that you choose a different location (e.g.
379: <code class="filename">/usr/pkgdb</code>) by
380: using the --pkgdbdir option to the bootstrap script.</p></li>
381: <li>
382: <p>If you do not intend to use the FreeBSD ports tools, it's probably a
383: good idea to move them out of the way to avoid confusion, e.g.</p>
384: <pre class="screen">
385: <code class="prompt">#</code> <strong class="userinput"><code>cd /usr/sbin</code></strong>
386: <code class="prompt">#</code> <strong class="userinput"><code>mv pkg_add pkg_add.orig</code></strong>
387: <code class="prompt">#</code> <strong class="userinput"><code>mv pkg_create pkg_create.orig</code></strong>
388: <code class="prompt">#</code> <strong class="userinput"><code>mv pkg_delete pkg_delete.orig</code></strong>
389: <code class="prompt">#</code> <strong class="userinput"><code>mv pkg_info pkg_info.orig</code></strong>
390: </pre>
391: </li>
1.3 ! rillig 392: <li><p>An example <a href="configuring.html#mk.conf"><code class="filename">mk.conf</code></a> file will be placed in
1.1 dsieger 393: <code class="filename">/etc/mk.conf.example</code> file
394: when you use the bootstrap script.</p></li>
395: </ol></div>
396: </div>
397: <div class="sect2" lang="en">
398: <div class="titlepage"><div><div><h3 class="title">
399: <a name="interix"></a>3.3.3. Interix</h3></div></div></div>
400: <p>Interix is a POSIX-compatible subsystem for the Windows NT kernel,
401: providing a Unix-like environment with a tighter kernel integration than
402: available with Cygwin. It is part of the Windows Services for Unix
403: package, available for free for any licensed copy of Windows 2000, XP
404: (not including XP Home), or 2003. SFU can be downloaded from <a href="http://www.microsoft.com/windows/sfu/" target="_top">http://www.microsoft.com/windows/sfu/</a>.</p>
405: <p>Services for Unix 3.5 has been tested. 3.0 or 3.1 may work, but
406: are not officially supported. (The main difference in 3.0/3.1 is lack
407: of pthreads, but other parts of libc may also be lacking.)</p>
408: <p>Services for Unix Applications (aka SUA) is an integrated component
409: of Windows Server 2003 R2 and Windows Vista. As of this writing, SUA's
410: Interix 5.x subsystem has not yet been tested with pkgsrc.</p>
411: <div class="sect3" lang="en">
412: <div class="titlepage"><div><div><h4 class="title">
413: <a name="platform.interix-sfu-install"></a>3.3.3.1. When installing Interix/SFU</h4></div></div></div>
414: <p>At an absolute minimum, the following packages must be installed from
415: the Windows Services for Unix 3.5 distribution in order to use pkgsrc:</p>
416: <div class="itemizedlist"><ul type="disc">
417: <li><p>Utilities -> Base Utilities</p></li>
418: <li><p>Interix GNU Components -> (all)</p></li>
419: <li><p>Remote Connectivity</p></li>
420: <li><p>Interix SDK</p></li>
421: </ul></div>
422: <p>When using pkgsrc on Interix, DO NOT install the Utilities subcomponent
423: "UNIX Perl". That is Perl 5.6 without shared module support, installed to
424: /usr/local, and will only cause confusion. Instead, install Perl 5.8 from
425: pkgsrc (or from a binary package).</p>
426: <p>The Remote Connectivity subcomponent "Windows Remote Shell Service" does
427: not need to be installed, but Remote Connectivity itself should be
428: installed in order to have a working inetd.</p>
429: <p>During installation you may be asked whether to enable setuid
430: behavior for Interix programs, and whether to make pathnames default to
431: case-sensitive. Setuid should be enabled, and case-sensitivity MUST be
432: enabled. (Without case-sensitivity, a large number of packages including
433: perl will not build.)</p>
434: <p>NOTE: Newer Windows service packs change the way binary execution
435: works (via the Data Execution Prevention feature). In order to use
436: pkgsrc and other gcc-compiled binaries reliably, a hotfix containing
437: POSIX.EXE, PSXDLL.DLL, PSXRUN.EXE, and PSXSS.EXE (899522 or newer)
438: must be installed. Hotfixes are available from Microsoft through a
439: support contract; however, a NetBSD developer has made most Interix
440: hotfixes available for personal use from <a href="http://www.duh.org/interix/hotfixes.php" target="_top">http://www.duh.org/interix/hotfixes.php</a>.</p>
441: <p>In addition to the hotfix noted above, it may be necessary to
442: disable Data Execution Prevention entirely to make Interix functional.
443: This may happen only with certain types of CPUs; the cause is not fully
444: understood at this time. If gcc or other applications still segfault
445: repeatedly after installing one of the hotfixes note above, the
446: following option can be added to the appropriate "boot.ini" line on the
447: Windows boot drive: /NoExecute=AlwaysOff
448: (WARNING, this will disable DEP completely, which may be a security
449: risk if applications are often run as a user in the Administrators
450: group!)</p>
451: </div>
452: <div class="sect3" lang="en">
453: <div class="titlepage"><div><div><h4 class="title">
454: <a name="platform.interix-sfu-postinstall"></a>3.3.3.2. What to do if Interix/SFU is already installed</h4></div></div></div>
455: <p>If SFU is already installed and you wish to alter these settings to work
456: with pkgsrc, note the following things.</p>
457: <div class="itemizedlist"><ul type="disc">
458: <li><p>To uninstall UNIX Perl, use Add/Remove Programs, select Microsoft
459: Windows Services for UNIX, then click Change. In the installer, choose
460: Add or Remove, then uncheck Utilities->UNIX Perl.</p></li>
461: <li>
462: <p>To enable case-sensitivity for the file system, run REGEDIT.EXE, and
463: change the following registry key:</p>
464: <p>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\kernel</p>
465: <p>Set the DWORD value "obcaseinsensitive" to 0; then reboot.</p>
466: </li>
467: <li>
468: <p>To enable setuid binaries (optional), run REGEDIT.EXE, and change the
469: following registry key:</p>
470: <p>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Services for UNIX</p>
471: <p>Set the DWORD value "EnableSetuidBinaries" to 1; then reboot.</p>
472: </li>
473: </ul></div>
474: </div>
475: <div class="sect3" lang="en">
476: <div class="titlepage"><div><div><h4 class="title">
477: <a name="platform.interix-notes"></a>3.3.3.3. Important notes for using pkgsrc</h4></div></div></div>
478: <p>The package manager (either the pkgsrc "su" user, or the user
479: running "pkg_add") must be a member of the local Administrators
480: group. Such a user must also be used to run the bootstrap. This is
481: slightly relaxed from the normal pkgsrc requirement of "root".</p>
482: <p>The package manager should use a umask of 002. "make install" will
483: automatically complain if this is not the case. This ensures that
484: directories written in /var/db/pkg are Administrators-group writeable.</p>
485: <p>The popular Interix binary packages from http://www.interopsystems.com/
486: use an older version of pkgsrc's pkg_* tools. Ideally, these should
487: NOT be used in conjunction with pkgsrc. If you choose to use them at
488: the same time as the pkgsrc packages, ensure that you use the proper
489: pkg_* tools for each type of binary package.</p>
490: <p>The TERM setting used for DOS-type console windows (including those
491: invoked by the csh and ksh startup shortcuts) is "interix". Most systems
492: don't have a termcap/terminfo entry for it, but the following .termcap
493: entry provides adequate emulation in most cases:</p>
494: <pre class="programlisting">
495: interix:kP=\E[S:kN=\E[T:kH=\E[U:dc@:DC@:tc=pcansi:
496: </pre>
497: </div>
498: <div class="sect3" lang="en">
499: <div class="titlepage"><div><div><h4 class="title">
500: <a name="platform.interix-limits"></a>3.3.3.4. Limitations of the Interix platform</h4></div></div></div>
501: <p>Though Interix suffices as a familiar and flexible substitute
502: for a full Unix-like platform, it has some drawbacks that should
503: be noted for those desiring to make the most of Interix.</p>
504: <div class="itemizedlist"><ul type="disc">
505: <li>
506: <p><span class="strong"><strong>X11:</strong></span></p>
507: <p>Interix comes with the standard set of X11R6 client libraries,
508: and can run X11 based applications, but it does
509: <span class="emphasis"><em>not</em></span> come with an X server. Some options are
510: <a href="http://www.starnet.com/products/xwin32/" target="_top">StarNet X-Win32</a>,
511: <a href="http://connectivity.hummingbird.com/products/nc/exceed/" target="_top">Hummingbird Exceed</a>
512: (available in a trimmed version for Interix from Interop Systems as the
513: <a href="http://www.interopsystems.com/InteropXserver.htm" target="_top">Interop X Server</a>),
514: and the free X11 server included with
515: <a href="http://x.cygwin.com/" target="_top">Cygwin</a>.</p>
516: </li>
517: <li>
518: <p><span class="strong"><strong>X11 acceleration:</strong></span></p>
519: <p>Because Interix runs in a completely different NT subsystem from
520: Win32 applications, it does not currently support various X11
521: protocol extensions for acceleration (such as MIT-SHM or DGA).
522: Most interactive applications to a local X server will run
523: reasonably fast, but full motion video and other graphics
524: intensive applications may require a faster-than-expected CPU.</p>
525: </li>
526: <li>
527: <p><span class="strong"><strong>Audio:</strong></span></p>
528: <p>Interix has no native support for audio output. For audio
529: support, pkgsrc uses the <span><strong class="command">esound</strong></span> client/server
530: audio system on Interix. Unlike on most platforms, the
531: <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/audio/esound/README.html" target="_top"><code class="filename">audio/esound</code></a> package does
532: <span class="emphasis"><em>not</em></span> contain the <span><strong class="command">esd</strong></span>
533: server component. To output audio via an Interix host, the
534: <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/emulators/cygwin_esound/README.html" target="_top"><code class="filename">emulators/cygwin_esound</code></a> package
535: must also be installed.</p>
536: </li>
537: <li>
538: <p><span class="strong"><strong>CD/DVDs, USB, and SCSI:</strong></span></p>
539: <p>Direct device access is not currently supported in Interix, so it
540: is not currently possible to access CD/DVD drives, USB devices,
541: or SCSI devices through non-filesystem means. Among other things,
542: this makes it impossible to use Interix directly for CD/DVD
543: burning.</p>
544: </li>
545: <li>
546: <p><span class="strong"><strong>Tape drives:</strong></span></p>
547: <p>Due to the same limitations as for CD-ROMs and SCSI devices, tape
548: drives are also not directly accessible in Interix. However,
549: support is in work to make tape drive access possible by using
550: Cygwin as a bridge (similarly to audio bridged via Cygwin's
551: esound server).</p>
552: </li>
553: </ul></div>
554: </div>
555: <div class="sect3" lang="en">
556: <div class="titlepage"><div><div><h4 class="title">
557: <a name="platform.interix-knownissues"></a>3.3.3.5. Known issues for pkgsrc on Interix</h4></div></div></div>
558: <p>It is not necessary, in general, to have a "root" user on the
559: Windows system; any member of the local Administrators group will
560: suffice. However, some packages currently assume that the user
561: named "root" is the privileged user. To accommodate these, you
562: may create such a user; make sure it is in the local group
563: Administrators (or your language equivalent).</p>
564: <p><span><strong class="command">pkg_add</strong></span> creates directories of mode
565: 0755, not 0775, in <code class="filename">$PKG_DBDIR</code>. For the
566: time being, install packages as the local Administrator (or
567: your language equivalent), or run the following command after
568: installing a package to work around the issue:</p>
569: <pre class="screen">
570: <code class="prompt">#</code> <strong class="userinput"><code>chmod -R g+w $PKG_DBDIR</code></strong>
571: </pre>
572: </div>
573: </div>
574: <div class="sect2" lang="en">
575: <div class="titlepage"><div><div><h3 class="title">
576: <a name="irix"></a>3.3.4. IRIX</h3></div></div></div>
577: <p>You will need a working C compiler, either gcc or SGI's MIPS and MIPSpro
578: compiler (cc/c89). Please set the <code class="varname">CC</code> environment variable
579: according to your preference. If you do not have a license for the MIPSpro
580: compiler suite, you can download a gcc tardist file from <a href="http://freeware.sgi.com/" target="_top">http://freeware.sgi.com/</a>.</p>
581: <p>Please note that you will need IRIX 6.5.17 or higher, as this is the earliest
582: version of IRIX providing support for <a href="http://netbsd.gw.com/cgi-bin/man-cgi?if_indextoname+3+NetBSD-current"><span class="citerefentry"><span class="refentrytitle">if_indextoname</span>(3)</span></a>, <a href="http://netbsd.gw.com/cgi-bin/man-cgi?if_nametoindex+3+NetBSD-current"><span class="citerefentry"><span class="refentrytitle">if_nametoindex</span>(3)</span></a>,
583: etc.</p>
584: <p>At this point in time, pkgsrc only supports one ABI at a time. That is, you cannot
585: switch between the old 32-bit ABI, the new 32-bit ABI and the 64-bit ABI. If
586: you start out using "abi=n32", that's what all your packages will be built
587: with.</p>
588: <p>Therefore, please make sure that you have no conflicting
589: <code class="varname">CFLAGS</code> in your environment or the
1.3 ! rillig 590: <a href="configuring.html#mk.conf"><code class="filename">mk.conf</code></a>. Particularly, make sure that you do not
1.1 dsieger 591: try to link n32 object files with lib64 or vice versa. Check your
592: <code class="filename">/etc/compiler.defaults</code>!</p>
593: <p>If you have the actual pkgsrc tree mounted via NFS from a different host,
594: please make sure to set <code class="varname">WRKOBJDIR</code> to a local directory,
595: as it appears that IRIX linker occasionally runs into issues when trying to
596: link over a network-mounted file system.</p>
597: <p>The bootstrapping process should set all the right options for programs such
598: as imake(1), but you may want to set some options depending on your local
599: setup. Please see <code class="filename">pkgsrc/mk/defaults/mk.conf</code> and, of
600: course, your compiler's man pages for details.</p>
601: <p>If you are using SGI's MIPSPro compiler, please set
602:
603: </p>
604: <pre class="programlisting">
605: PKGSRC_COMPILER= mipspro
606: </pre>
607: <p>
608:
1.3 ! rillig 609: in <a href="configuring.html#mk.conf"><code class="filename">mk.conf</code></a>. Otherwise, pkgsrc will assume you
1.1 dsieger 610: are using gcc and may end up passing invalid flags to the compiler. Note that
611: bootstrap should create an appropriate <code class="filename">mk.conf.example</code> by
612: default.</p>
613: <p>If you have both the MIPSPro compiler chain installed as well as gcc,
614: but want to make sure that MIPSPro is used, please set your <code class="varname">PATH</code>
615: to <span class="emphasis"><em>not</em></span> include the location of gcc (often
616: <code class="filename">/usr/freeware/bin</code>), and (important) pass the
617: '--preserve-path' flag.</p>
618: </div>
619: <div class="sect2" lang="en">
620: <div class="titlepage"><div><div><h3 class="title">
621: <a name="linux"></a>3.3.5. Linux</h3></div></div></div>
622: <p>Some versions of Linux (for example Debian GNU/Linux) need
623: either libtermcap or libcurses (libncurses). Installing the
624: distributions libncurses-dev package (or equivalent) should fix
625: the problem.</p>
626: <p>pkgsrc supports both gcc (GNU Compiler Collection) and icc
627: (Intel C++ Compiler). gcc is the default. icc 8.0 and 8.1 on
628: i386 have been tested.</p>
629: <p>To bootstrap using icc, assuming the default icc installation
630: directory:</p>
631: <pre class="programlisting">
632: env CC=/opt/intel_cc_80/bin/icc LDFLAGS=-static-libcxa \
633: ac_cv___attribute__=yes ./bootstrap
634: </pre>
635: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
636: <h3 class="title">Note</h3>
637: <p>icc 8.1 needs the `-i-static' argument instead of -static-libcxa.</p>
638: </div>
639: <p>icc supports __attribute__, but the GNU configure test uses a nested
640: function, which icc does not support. #undef'ing __attribute__ has the
641: unfortunate side-effect of breaking many of the Linux header files, which
642: cannot be compiled properly without __attribute__. The test must be
643: overridden so that __attribute__ is assumed supported by the
644: compiler.</p>
645: <p>After bootstrapping, you should set <code class="varname">PKGSRC_COMPILER</code>
1.3 ! rillig 646: in <a href="configuring.html#mk.conf"><code class="filename">mk.conf</code></a>:</p>
1.1 dsieger 647: <pre class="programlisting">
648: PKGSRC_COMPILER= icc
649: </pre>
650: <p>The default installation directory for icc is
651: <code class="filename">/opt/intel_cc_80</code>, which
652: is also the pkgsrc default. If you have installed it into a different
653: directory, set <code class="varname">ICCBASE</code> in
1.3 ! rillig 654: <a href="configuring.html#mk.conf"><code class="filename">mk.conf</code></a>:</p>
1.1 dsieger 655: <pre class="programlisting">
656: ICCBASE= /opt/icc
657: </pre>
658: <p>pkgsrc uses the static linking method of the runtime libraries
659: provided by icc, so binaries can be run on other systems which do not
660: have the shared libraries installed.</p>
661: <p>Libtool, however, extracts a list of libraries from the
662: <a href="http://netbsd.gw.com/cgi-bin/man-cgi?ld+1+NetBSD-current"><span class="citerefentry"><span class="refentrytitle">ld</span>(1)</span></a> command run when linking a C++ shared library and
663: records it, throwing away the -Bstatic and -Bdynamic options
664: interspersed between the libraries. This means that
665: libtool-linked C++ shared libraries will have a runtime
666: dependency on the icc libraries until this is fixed in
667: libtool.</p>
668: </div>
669: <div class="sect2" lang="en">
670: <div class="titlepage"><div><div><h3 class="title">
671: <a name="openbsd"></a>3.3.6. OpenBSD</h3></div></div></div>
672: <p>OpenBSD 3.0 and 3.2 are tested and supported.</p>
673: <p>Care should be taken so that the tools that this kit installs do not conflict
674: with the OpenBSD userland tools. There are several steps:</p>
675: <div class="orderedlist"><ol type="1">
676: <li><p>OpenBSD stores its ports pkg database in
677: <code class="filename">/var/db/pkg</code>. It is therefore
678: recommended that you choose a different location (e.g.
679: <code class="filename">/usr/pkgdb</code>) by
680: using the --pkgdbdir option to the bootstrap script.</p></li>
681: <li>
682: <p>If you do not intend to use the OpenBSD ports tools, it's probably a
683: good idea to move them out of the way to avoid confusion, e.g.</p>
684: <pre class="screen">
685: <code class="prompt">#</code> <strong class="userinput"><code>cd /usr/sbin</code></strong>
686: <code class="prompt">#</code> <strong class="userinput"><code>mv pkg_add pkg_add.orig</code></strong>
687: <code class="prompt">#</code> <strong class="userinput"><code>mv pkg_create pkg_create.orig</code></strong>
688: <code class="prompt">#</code> <strong class="userinput"><code>mv pkg_delete pkg_delete.orig</code></strong>
689: <code class="prompt">#</code> <strong class="userinput"><code>mv pkg_info pkg_info.orig</code></strong>
690: </pre>
691: </li>
692: <li>
1.3 ! rillig 693: <p>An example <a href="configuring.html#mk.conf"><code class="filename">mk.conf</code></a> file will be placed in
1.1 dsieger 694: <code class="filename">/etc/mk.conf.example</code> file
695: when you use the bootstrap script. OpenBSD's make program uses
1.3 ! rillig 696: <a href="configuring.html#mk.conf"><code class="filename">mk.conf</code></a>
1.1 dsieger 697: as well. You can work around this by enclosing all the pkgsrc-specific parts
698: of the file with:</p>
699: <pre class="programlisting">
700: .ifdef BSD_PKG_MK
701: # pkgsrc stuff, e.g. insert defaults/mk.conf or similar here
702: .else
703: # OpenBSD stuff
704: .endif
705: </pre>
706: </li>
707: </ol></div>
708: </div>
709: <div class="sect2" lang="en">
710: <div class="titlepage"><div><div><h3 class="title">
711: <a name="solaris"></a>3.3.7. Solaris</h3></div></div></div>
712: <p>Solaris 2.6 through 9 are supported on both x86 and sparc.
713: You will need a working C compiler. Both gcc 2.95.3 and
714: Sun WorkShop 5 have been tested.</p>
715: <p>The following packages are required on Solaris 8 for the bootstrap
716: process and to build packages.</p>
717: <div class="itemizedlist"><ul type="disc">
718: <li><p>SUNWsprot</p></li>
719: <li><p>SUNWarc</p></li>
720: <li><p>SUNWbtool</p></li>
721: <li><p>SUNWtoo</p></li>
722: <li><p>SUNWlibm</p></li>
723: </ul></div>
724: <p>Please note that the use of GNU binutils on Solaris is
725: <span class="emphasis"><em>not</em></span> supported, as of June 2006.</p>
726: <p>Whichever compiler you use, please ensure the compiler tools and
727: your $prefix are in your <code class="varname">PATH</code>. This includes
728: <code class="filename">/usr/ccs/{bin,lib}</code>
729: and e.g. <code class="filename">/usr/pkg/{bin,sbin}</code>.</p>
730: <div class="sect3" lang="en">
731: <div class="titlepage"><div><div><h4 class="title">
732: <a name="solaris-gcc-note"></a>3.3.7.1. If you are using gcc</h4></div></div></div>
733: <p>It makes life much simpler if you only use the same gcc consistently
734: for building all packages.</p>
735: <p>It is recommended that an external gcc be used only for bootstrapping,
736: then either build gcc from
737: <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/lang/gcc/README.html" target="_top"><code class="filename">lang/gcc</code></a> or install a binary gcc
738: package, then remove gcc used during bootstrapping.</p>
739: <p>Binary packages of gcc can be found through <a href="http://www.sunfreeware.com/" target="_top">http://www.sunfreeware.com/</a>.</p>
740: </div>
741: <div class="sect3" lang="en">
742: <div class="titlepage"><div><div><h4 class="title">
743: <a name="solaris-sun-workshop-note"></a>3.3.7.2. If you are using Sun WorkShop</h4></div></div></div>
744: <p>You will need at least the following packages installed (from WorkShop
745: 5.0)</p>
746: <div class="itemizedlist"><ul type="disc">
747: <li><p>SPROcc
748: - Sun WorkShop Compiler C 5.0</p></li>
749: <li><p>SPROcpl
750: - Sun WorkShop Compiler C++ 5.0</p></li>
751: <li><p>SPROild
752: - Sun WorkShop Incremental Linker</p></li>
753: <li><p>SPROlang
754: - Sun WorkShop Compilers common components</p></li>
755: </ul></div>
756: <p>You should set the following variables in your
1.3 ! rillig 757: <a href="configuring.html#mk.conf"><code class="filename">mk.conf</code></a> file:</p>
1.1 dsieger 758: <pre class="programlisting">
759: CC= cc
760: CXX= CC
761: CPP= cc -E
762: CXXCPP= CC -E
763: </pre>
764: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
765: <h3 class="title">Note</h3>
766: <p>The <code class="varname">CPP</code> setting might break some
767: packages that use the C preprocessor for processing things other
768: than C source code.</p>
769: </div>
770: </div>
771: <div class="sect3" lang="en">
772: <div class="titlepage"><div><div><h4 class="title">
773: <a name="solaris-sunpro-64"></a>3.3.7.3. Building 64-bit binaries with SunPro</h4></div></div></div>
774: <p>To build 64-bit packages, you just need to have the
1.3 ! rillig 775: following lines in your <a href="configuring.html#mk.conf"><code class="filename">mk.conf</code></a> file:</p>
1.1 dsieger 776: <pre class="programlisting">
777: PKGSRC_COMPILER= sunpro
778: ABI= 64
779: </pre>
780: <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
781: <h3 class="title">Note</h3>
782: <p>This setting has been tested for the SPARC
783: architecture. Intel and AMD machines need some more
784: work.</p>
785: </div>
786: </div>
787: <div class="sect3" lang="en">
788: <div class="titlepage"><div><div><h4 class="title">
789: <a name="plat.sunos.problems"></a>3.3.7.4. Common problems</h4></div></div></div>
790: <p>Sometimes, when using <span><strong class="command">libtool</strong></span>,
791: <code class="filename">/bin/ksh</code> crashes with a segmentation fault.
792: The workaround is to use another shell for the configure
793: scripts, for example by installing <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/shells/bash/README.html" target="_top"><code class="filename">shells/bash</code></a> and adding the following lines
1.3 ! rillig 794: to your <a href="configuring.html#mk.conf"><code class="filename">mk.conf</code></a>:</p>
1.1 dsieger 795: <pre class="programlisting">
796: CONFIG_SHELL= ${LOCALBASE}/bin/bash
797: WRAPPER_SHELL= ${LOCALBASE}/bin/bash
798: </pre>
799: <p>Then, rebuild the <a href="ftp://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/devel/libtool-base/README.html" target="_top"><code class="filename">devel/libtool-base</code></a> package.</p>
800: </div>
801: </div>
802: </div>
803: </div>
804: <div class="navfooter">
805: <hr>
806: <table width="100%" summary="Navigation footer">
807: <tr>
808: <td width="40%" align="left">
809: <a accesskey="p" href="getting.html">Prev</a> </td>
810: <td width="20%" align="center"><a accesskey="u" href="users-guide.html">Up</a></td>
811: <td width="40%" align="right"> <a accesskey="n" href="using.html">Next</a>
812: </td>
813: </tr>
814: <tr>
815: <td width="40%" align="left" valign="top">Chapter 2. Where to get pkgsrc and how to keep it up-to-date </td>
816: <td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td>
817: <td width="40%" align="right" valign="top"> Chapter 4. Using pkgsrc</td>
818: </tr>
819: </table>
820: </div>
821: </body>
822: </html>
CVSweb <webmaster@jp.NetBSD.org>