All of lore.kernel.org
 help / color / mirror / Atom feed
From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] docs: update URL to uClibc-ng homepage
Date: Fri, 14 Oct 2016 11:29:04 +0200	[thread overview]
Message-ID: <20161014092904.GA32247@waldemar-brodkorb.de> (raw)

It is not necessary to update all mentioning of uClibc, but
at least we should point to the right homepage of the used
project.

Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
---
 docs/manual/configure.txt | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/manual/configure.txt b/docs/manual/configure.txt
index 0cd9f82..0739bc7 100644
--- a/docs/manual/configure.txt
+++ b/docs/manual/configure.txt
@@ -31,7 +31,7 @@ code for your system. It consists of a compiler (in our case, +gcc+),
 binary utils like assembler and linker (in our case, +binutils+) and a
 C standard library (for example
 http://www.gnu.org/software/libc/libc.html[GNU Libc],
-http://www.uclibc.org/[uClibc]).
+http://www.uclibc-ng.org/[uClibc-ng]).
 
 The system installed on your development station certainly already has
 a compilation toolchain that you can use to compile an application
@@ -81,7 +81,7 @@ by itself a cross-compilation toolchain, before building the userspace
 applications and libraries for your target embedded system.
 
 This backend supports several C libraries:
-http://www.uclibc.org[uClibc],
+http://www.uclibc-ng.org[uClibc-ng],
 http://www.gnu.org/software/libc/libc.html[glibc] and
 http://www.musl-libc.org[musl].
 
-- 
2.1.4

             reply	other threads:[~2016-10-14  9:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-14  9:29 Waldemar Brodkorb [this message]
2016-10-14 13:53 ` [Buildroot] [PATCH] docs: update URL to uClibc-ng homepage Arnout Vandecappelle
2016-10-14 14:50 ` Peter Korsgaard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20161014092904.GA32247@waldemar-brodkorb.de \
    --to=wbx@openadk.org \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.