[PATCH] Add a few log messages for messing with glibc addons dirs and symlinks

[Yann E. MORIN]

Esben, All,

On Friday 07 October 2011 15:25:32 Esben Haabendal wrote:
> # HG changeset patch
> # User Esben Haabendal <esben.haabendal@prevas.dk>
> # Date 1317993827 -7200
> # Node ID e524e3b6cb28b5e9ffc2d404e7c4fc73d53aa0a3
> # Parent  34d13602e8cc46247f19a2c498df0cf060064d3d
> Add a few log messages for messing with glibc addons dirs and symlinks
> 
> Signed-off-by: "Esben Haabendal" <esben.haabendal@prevas.dk>
> 
> diff -r 34d13602e8cc -r e524e3b6cb28
> scripts/build/libc/glibc-eglibc.sh-common
> --- a/scripts/build/libc/glibc-eglibc.sh-common	Fri Oct 07 15:06:44 2011
> +0200
> +++ b/scripts/build/libc/glibc-eglibc.sh-common	Fri Oct 07 15:23:47 2011
> +0200

Linewrap-carnage...

> @@ -29,10 +29,10 @@
>          # either the 'long' or 'short' name, whatever the addons name
>          # but we prefer the 'short' name and avoid duplicates.
>          if [ -d "${CT_LIBC}-${addon}-${CT_LIBC_VERSION}" ]; then
> -            mv "${CT_LIBC}-${addon}-${CT_LIBC_VERSION}" "${addon}"
> +            CT_DoExecLog FILE mv
> "${CT_LIBC}-${addon}-${CT_LIBC_VERSION}" "${addon}"

Ditto...

>          fi
>  
> -        ln -s "${addon}" "${CT_LIBC}-${addon}-${CT_LIBC_VERSION}"
> +        CT_DoExecLog FILE ln -s "${addon}"
> "${CT_LIBC}-${addon}-${CT_LIBC_VERSION}"

Ditto...

>  
>          CT_Patch nochdir "${CT_LIBC}" "${addon}-${CT_LIBC_VERSION}"
>  

I fixed it.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

--
For unsubscribe information see http://sourceware.org/lists.html#faq