Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
llvm-epi-0.8
Manage
Activity
Members
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Model registry
Analyze
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
This is an archived project. Repository and other project resources are read-only.
Show more breadcrumbs
Roger Ferrer
llvm-epi-0.8
Commits
50e5924e
Commit
50e5924e
authored
12 years ago
by
Dmitri Gribenko
Browse files
Options
Downloads
Patches
Plain Diff
Documentation: fix typo: stdard -> stdarg
llvm-svn: 174613
parent
90ccd44e
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
clang/docs/FAQ.rst
+2
-2
2 additions, 2 deletions
clang/docs/FAQ.rst
with
2 additions
and
2 deletions
clang/docs/FAQ.rst
+
2
−
2
View file @
50e5924e
...
@@ -51,10 +51,10 @@ driver and add the option you need. Alternatively, you can run
...
@@ -51,10 +51,10 @@ driver and add the option you need. Alternatively, you can run
``clang -Xclang <option> ...`` to force the driver pass ``<option>`` to
``clang -Xclang <option> ...`` to force the driver pass ``<option>`` to
``clang -cc1``.
``clang -cc1``.
I get errors about some headers being missing (``stddef.h``, ``stdar
d
.h``)
I get errors about some headers being missing (``stddef.h``, ``stdar
g
.h``)
--------------------------------------------------------------------------
--------------------------------------------------------------------------
Some header files (``stddef.h``, ``stdar
d
.h``, and others) are shipped with
Some header files (``stddef.h``, ``stdar
g
.h``, and others) are shipped with
Clang --- these are called builtin includes. Clang searches for them in a
Clang --- these are called builtin includes. Clang searches for them in a
directory relative to the location of the ``clang`` binary. If you moved the
directory relative to the location of the ``clang`` binary. If you moved the
``clang`` binary, you need to move the builtin headers, too.
``clang`` binary, you need to move the builtin headers, too.
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment