Fixed minor typo.

Removed a duplicate sentence and re-worded the other.
Changed signal 12 -> signal 11 in questions section.
This commit is contained in:
Mark Ovens 2000-10-03 23:21:35 +00:00
parent a029e97906
commit 7d900ddfb4
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=8088
2 changed files with 18 additions and 24 deletions

View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/cutting-edge/chapter.sgml,v 1.55 2000/08/21 19:10:18 ben Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/cutting-edge/chapter.sgml,v 1.56 2000/08/22 05:54:59 kuriyama Exp $
-->
<chapter id="cutting-edge">
@ -525,18 +525,15 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
default defines &ndash; most of which are commented out. To
make use of them when you rebuild your system from source, add
them to <filename>/etc/make.conf</filename>. Keep in mind that
anything to add to <filename>/etc/make.conf</filename> is also
anything you add to <filename>/etc/make.conf</filename> is also
used every time you run <command>make</command>, so it is a good
idea to set them to something sensible for your system. As a
typical user (not a FreeBSD developer), you will probably want
to add the <makevar>CFLAGS</makevar> and
<makevar>NOPROFILE</makevar> lines found in
<filename>/etc/defaults/make.conf</filename>.</para>
idea to set them to something sensible for your system.</para>
<para>Everything is, by default, commented out. Uncomment those
entries that look useful. For a typical user (not a developer),
you will probably want to uncomment the CFLAGS and NOPROFILE
definitions.</para>
<para>As a typical user (not a FreeBSD developer), you will
probably want to copy the <makevar>CFLAGS</makevar> and
<makevar>NOPROFILE</makevar> lines found in
<filename>/etc/defaults/make.conf</filename> to
<filename>/etc/make.conf</filename> and uncomment them.</para>
<note>
<title/Version 2.1.7 and below/
@ -1266,7 +1263,7 @@ Script done, &hellip;</screen>
<qandaentry>
<question>
<para>My compile failed with lots of signal 12 (or other signal
<para>My compile failed with lots of signal 11 (or other signal
number) errors. What has happened?</para>
</question>

View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/cutting-edge/chapter.sgml,v 1.55 2000/08/21 19:10:18 ben Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/cutting-edge/chapter.sgml,v 1.56 2000/08/22 05:54:59 kuriyama Exp $
-->
<chapter id="cutting-edge">
@ -525,18 +525,15 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></scr
default defines &ndash; most of which are commented out. To
make use of them when you rebuild your system from source, add
them to <filename>/etc/make.conf</filename>. Keep in mind that
anything to add to <filename>/etc/make.conf</filename> is also
anything you add to <filename>/etc/make.conf</filename> is also
used every time you run <command>make</command>, so it is a good
idea to set them to something sensible for your system. As a
typical user (not a FreeBSD developer), you will probably want
to add the <makevar>CFLAGS</makevar> and
<makevar>NOPROFILE</makevar> lines found in
<filename>/etc/defaults/make.conf</filename>.</para>
idea to set them to something sensible for your system.</para>
<para>Everything is, by default, commented out. Uncomment those
entries that look useful. For a typical user (not a developer),
you will probably want to uncomment the CFLAGS and NOPROFILE
definitions.</para>
<para>As a typical user (not a FreeBSD developer), you will
probably want to copy the <makevar>CFLAGS</makevar> and
<makevar>NOPROFILE</makevar> lines found in
<filename>/etc/defaults/make.conf</filename> to
<filename>/etc/make.conf</filename> and uncomment them.</para>
<note>
<title/Version 2.1.7 and below/
@ -1266,7 +1263,7 @@ Script done, &hellip;</screen>
<qandaentry>
<question>
<para>My compile failed with lots of signal 12 (or other signal
<para>My compile failed with lots of signal 11 (or other signal
number) errors. What has happened?</para>
</question>