build system internals: Linux doesn't use Android libc

The Linux kernel doesn't use a libc to be built.

Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>

1 files changed, 4 insertions, 5 deletions

diff --git a/full-description.md b/full-description.md
index d7f965e..89ad553 100644
--- a/full-description.md
+++ b/full-description.md
@@ -44,11 +44,10 @@ distribution. The output of the build ends up in a directory that is then used
 to create the distribution image that are to be installed on a device.
 
 Besides the core components of AOSP, community distributions tend to use several
-external projects like Mesa and the Linux kernel. These must usually be
-integrated into the build tree as they depend on AOSP's libc. In such cases,
-Google expects the project maintainers to keep their project compatible with
-AOSP's build system, i.e. nowadays they expect the project to have its own
-Blueprint files.
+external projects like Mesa. These must usually be integrated into the build
+tree as they depend on AOSP's libc. In such cases, Google expects the project
+maintainers to keep their project compatible with AOSP's build system,
+i.e. nowadays they expect the project to have its own Blueprint files.
 This contrasts with GNU/Linux distributions, which provide ways to build each
 project in its own native build system and then incorporate it into the distro
 image as an independent package.