diff mbox

docs: update URL to uClibc-ng homepage

Message ID 20161014092904.GA32247@waldemar-brodkorb.de
State Accepted
Commit 3aa01695eabb9183ffb804337924a7bd649be9ec
Headers show

Commit Message

Waldemar Brodkorb Oct. 14, 2016, 9:29 a.m. UTC
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(-)

Comments

Arnout Vandecappelle Oct. 14, 2016, 1:53 p.m. UTC | #1
On 14-10-16 11:29, Waldemar Brodkorb wrote:
> 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>

Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>

 Can you also update the BR2_TOOLCHAIN_EXTERNAL_CUSTOM_UCLIBC in
toolchain/toolchain-external/Config.in to mention both uClibc and uClibc-ng?

 Regards,
 Arnout

> ---
>  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].
>  
>
Peter Korsgaard Oct. 14, 2016, 2:50 p.m. UTC | #2
>>>>> "Waldemar" == Waldemar Brodkorb <wbx@openadk.org> writes:

 > 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>

Committed, thanks.
diff mbox

Patch

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].