summaryrefslogtreecommitdiff
path: root/doc/pkgsrc.html
diff options
context:
space:
mode:
authorrillig <rillig@pkgsrc.org>2005-11-24 10:08:00 +0000
committerrillig <rillig@pkgsrc.org>2005-11-24 10:08:00 +0000
commit1f6b1c5e5ffbd5619710d44813be0ad90a93541c (patch)
tree5055e551c870f20c1a7e46b31e853c4dc4b0998d /doc/pkgsrc.html
parent2330f610f920b52395d0816ecdbf28d8ede3b68a (diff)
downloadpkgsrc-1f6b1c5e5ffbd5619710d44813be0ad90a93541c.tar.gz
regen.
Diffstat (limited to 'doc/pkgsrc.html')
-rw-r--r--doc/pkgsrc.html63
1 files changed, 44 insertions, 19 deletions
diff --git a/doc/pkgsrc.html b/doc/pkgsrc.html
index c14430f4828..eb2e9d88d15 100644
--- a/doc/pkgsrc.html
+++ b/doc/pkgsrc.html
@@ -12960,22 +12960,22 @@ nbftp% <strong class="userinput"><code>chmod 755 .</code></strong>
these macros are usually ones that describe the target
CPU and operating system. Depending of which of the
macros are defined, you can write code that uses
- features unique to a specific platform. The best way to
- handle these differences is to use the GNU autotools
- (automake, autoconf, etc.) to check for specific
- features (like the existence of a header file, a
- function or a library).</p>
-
- <p>If that is not possible you can use the predefined
- macros below to configure your code to the platform it
- runs on. Almost every operating system, hardware
- architecture and compiler has its own macro. For
- example, if the macros <code class=
- "varname">__GNUC__</code>, <code class=
- "varname">__i386__</code> and <code class=
+ features unique to a specific platform. Generally you
+ should rather use the GNU autotools (automake,
+ autoconf, etc.) to check for specific features (like
+ the existence of a header file, a function or a
+ library), but sometimes this is not possible or
+ desired.</p>
+
+ <p>In that case you can use the predefined macros below
+ to configure your code to the platform it runs on.
+ Almost every operating system, hardware architecture
+ and compiler has its own macro. For example, if the
+ macros <code class="varname">__GNUC__</code>,
+ <code class="varname">__i386__</code> and <code class=
"varname">__NetBSD__</code> are all defined, you know
- that you are using NetBSD on an Intel CPU, and your
- compiler is GCC.</p>
+ that you are using NetBSD on an i386 compatible CPU,
+ and your compiler is GCC.</p>
<div class="sect3" lang="en" xml:lang="en">
<div class="titlepage">
@@ -13072,12 +13072,29 @@ nbftp% <strong class="userinput"><code>chmod 755 .</code></strong>
<div class="variablelist">
<dl>
- <dt><span class="term">SunPro 5.7 + Solaris 8 +
- SPARC</span></dt>
+ <dt><span class="term">GCC 3.3.3 + SuSE Linux 9.1 +
+ i386</span></dt>
<dd>
- <p>__SVR4, __sparc, __sun, __unix, sparc, sun,
- unix.</p>
+ <p>__ELF__, __gnu_linux__, __i386, _i386__,
+ __linux, __linux__, __unix, __unix__, i386,
+ linux, unix.</p>
+ </dd>
+
+ <dt><span class="term">GCC 2.95 + NetBSD 1.6.2 +
+ i386</span></dt>
+
+ <dd>
+ <p>__ELF__, __NetBSD__, __i386, _i386__,
+ i386.</p>
+ </dd>
+
+ <dt><span class="term">GCC 3.3.3 + NetBSD 2.0 +
+ i386</span></dt>
+
+ <dd>
+ <p>__ELF__, __NetBSD__, __i386, _i386__,
+ i386.</p>
</dd>
<dt><span class="term">GCC 4 + Solaris 8 +
@@ -13088,6 +13105,14 @@ nbftp% <strong class="userinput"><code>chmod 755 .</code></strong>
__SVR4, __svr4__, __unix, __unix__, sparc, sun,
unix.</p>
</dd>
+
+ <dt><span class="term">SunPro 5.7 + Solaris 8 +
+ SPARC</span></dt>
+
+ <dd>
+ <p>__SVR4, __sparc, __sun, __unix, sparc, sun,
+ unix.</p>
+ </dd>
</dl>
</div>
</div>