JakeHillion/nixpkgs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix a few typos

Browse Source
This commit is contained in:
Ivan Kozik 2013-08-11 10:47:09 +00:00
parent d068505b2f
commit 1866619acc
4 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/stdenv.xml
View File

@ -6,7 +6,7 @@
<para>The standard build environment in the Nix Packages collection
provides a environment for building Unix packages that does a lot of
provides an environment for building Unix packages that does a lot of
common build tasks automatically. In fact, for Unix packages that use
the standard <literal>./configure; make; make install</literal> build
interface, you don’t need to write a build script at all; the standard

6
maintainers/docs/cross.txt
View File

@ -41,7 +41,7 @@ NB:
Keep in mind that many programs are not very well suited for cross
compilation. Either they are not intended to run on other platforms,
because the code is highly platform specific, or the configuration proces
because the code is highly platform specific, or the configuration process
is not written with cross compilation in mind.
Nix will not solve these problems for you!
@ -290,7 +290,7 @@ this compiler and verified to be working on a HP Jornada 820 running Linux
are "patch", "make" and "wget".
If we want to build C++ programs it gets a lot more difficult. GCC has a
three step compilation proces. In the first step a simple compiler, called
three step compilation process. In the first step a simple compiler, called
xgcc, that can compile only C programs is built. With that compiler it
compiles itself two more times: one time to build a full compiler, and another
time to build a full compiler once again with the freshly built compiler from
@ -318,7 +318,7 @@ with compilation flags. This is still work in progress for Nix.
---
After succesfully completing the whole toolchain you can start building
After successfully completing the whole toolchain you can start building
packages with the newly built tools. To make everything build correctly
you will need a stdenv for your target platform. Setting up this platform
will take some effort. Right now there is a very experimental setup for

2
pkgs/build-support/fetchmtn/builder.sh
View File

@ -24,7 +24,7 @@ for source in $dbs; do
echo "selector $selector does not match any revision";
fi
else
echo "pulling branch $branch wasn't succesfull";
echo "pulling branch $branch wasn't successful";
fi;
if test -n "$done"; then
break;

2
pkgs/development/libraries/libxml2/setup-hook.sh
View File

@ -11,7 +11,7 @@ addXMLCatalogs () {
if test -z "$libxmlHookDone"; then
libxmlHookDone=1
# Set http_proxy and ftp_proxy to a invalid host to prevent
# Set http_proxy and ftp_proxy to an invalid host to prevent
# xmllint and xsltproc from trying to download DTDs from the
# network even when --nonet is not given. That would be impure.
# (Note that .invalid is a reserved domain guaranteed not to