📄 fixed-headers.html
字号:
<html lang="en">
<head>
<title>Using the GNU Compiler Collection (GCC)</title>
<meta http-equiv="Content-Type" content="text/html">
<meta name="description" content="Using the GNU Compiler Collection (GCC)">
<meta name="generator" content="makeinfo 4.3">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home">
<!--
Copyright © 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998,
1999, 2000, 2001, 2002, 2003 Free Software Foundation, Inc.
<p>Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2 or
any later version published by the Free Software Foundation; with the
Invariant Sections being "GNU General Public License" and "Funding
Free Software", the Front-Cover texts being (a) (see below), and with
the Back-Cover Texts being (b) (see below). A copy of the license is
included in the section entitled "GNU Free Documentation License".
<p>(a) The FSF's Front-Cover Text is:
<p>A GNU Manual
<p>(b) The FSF's Back-Cover Text is:
<p>You have freedom to copy and modify this GNU Manual, like GNU
software. Copies published by the Free Software Foundation raise
funds for GNU development.-->
</head>
<body>
<div class="node">
<p>
Node:<a name="Fixed%20Headers">Fixed Headers</a>,
Next:<a rel="next" accesskey="n" href="Standard-Libraries.html#Standard%20Libraries">Standard Libraries</a>,
Previous:<a rel="previous" accesskey="p" href="Incompatibilities.html#Incompatibilities">Incompatibilities</a>,
Up:<a rel="up" accesskey="u" href="Trouble.html#Trouble">Trouble</a>
<hr><br>
</div>
<h3 class="section">Fixed Header Files</h3>
<p>GCC needs to install corrected versions of some system header files.
This is because most target systems have some header files that won't
work with GCC unless they are changed. Some have bugs, some are
incompatible with ISO C, and some depend on special features of other
compilers.
<p>Installing GCC automatically creates and installs the fixed header
files, by running a program called <code>fixincludes</code> (or for certain
targets an alternative such as <code>fixinc.svr4</code>). Normally, you
don't need to pay attention to this. But there are cases where it
doesn't do the right thing automatically.
<ul>
<li>If you update the system's header files, such as by installing a new
system version, the fixed header files of GCC are not automatically
updated. The easiest way to update them is to reinstall GCC. (If
you want to be clever, look in the makefile and you can find a
shortcut.)
<li>On some systems, in particular SunOS 4, header file directories contain
machine-specific symbolic links in certain places. This makes it
possible to share most of the header files among hosts running the
same version of SunOS 4 on different machine models.
<p>The programs that fix the header files do not understand this special
way of using symbolic links; therefore, the directory of fixed header
files is good only for the machine model used to build it.
<p>In SunOS 4, only programs that look inside the kernel will notice the
difference between machine models. Therefore, for most purposes, you
need not be concerned about this.
<p>It is possible to make separate sets of fixed header files for the
different machine models, and arrange a structure of symbolic links so
as to use the proper set, but you'll have to do this by hand.
</p><li>On Lynxos, GCC by default does not fix the header files. This is
because bugs in the shell cause the <code>fixincludes</code> script to fail.
<p>This means you will encounter problems due to bugs in the system header
files. It may be no comfort that they aren't GCC's fault, but it
does mean that there's nothing for us to do about them.
</ul>
</body></html>
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -