From: Esben Haabendal <esben.haabendal@prevas.dk>
To: crossgcc@sourceware.org
Subject: [PATCH] Add a few log messages for messing with glibc addons dirs and symlinks
Date: Fri, 07 Oct 2011 13:25:00 -0000 [thread overview]
Message-ID: <1317993932.2519.4.camel@arh128> (raw)
# 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
@@ -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}"
fi
- ln -s "${addon}" "${CT_LIBC}-${addon}-${CT_LIBC_VERSION}"
+ CT_DoExecLog FILE ln -s "${addon}"
"${CT_LIBC}-${addon}-${CT_LIBC_VERSION}"
CT_Patch nochdir "${CT_LIBC}" "${addon}-${CT_LIBC_VERSION}"
--
ESBEN HAABENDAL, Senior Software Designer
Prevas A/S, Hedeager 1, DK-8200 Aarhus N, www.prevas.dk
Central: +45 87 43 80 70 Direct: +45 51 92 53 93
E-mail: esben.haabendal@prevas.dk
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next reply other threads:[~2011-10-07 13:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-07 13:25 Esben Haabendal [this message]
2011-10-08 15:35 ` Yann E. MORIN
2011-10-08 16:57 ` Esben Haabendal
2011-10-08 15:43 ` Yann E. MORIN
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=1317993932.2519.4.camel@arh128 \
--to=esben.haabendal@prevas.dk \
--cc=crossgcc@sourceware.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).