From: "Wilco Dijkstra" <wdijkstr@arm.com>
To: "'Petar Jovanovic'" <petar.jovanovic@rt-rk.com>
Cc: <libc-alpha@sourceware.org>
Subject: RE: build break in strcpy.c
Date: Mon, 24 Nov 2014 21:48:00 -0000 [thread overview]
Message-ID: <000701d00830$59b9b6e0$0d2d24a0$@com> (raw)
In-Reply-To: <002f01d0081f$567941a0$036bc4e0$@rt-rk.com>
> Petar Jovanovic wrote:
>
> Can you actually build the code after this change?
>
> You may want to follow up with:
>
> diff --git a/string/strcpy.c b/string/strcpy.c
> index 91f9cc6..94ca1df 100644
> --- a/string/strcpy.c
> +++ b/string/strcpy.c
> @@ -24,6 +24,6 @@
> char *
> strcpy (char *dest, const char *src)
> {
> - return memcpy (dest, src, strlen (src) + 1));
> + return memcpy (dest, src, strlen (src) + 1);
> }
> libc_hidden_builtin_def (strcpy)
Sorry, not sure where that extra character came from - it seems to
be in the email with the patch but not in my original code...
Anyway, committed as obvious, and it builds again now.
Wilco
prev parent reply other threads:[~2014-11-24 21:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-24 19:46 Petar Jovanovic
2014-11-24 21:48 ` Wilco Dijkstra [this message]
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='000701d00830$59b9b6e0$0d2d24a0$@com' \
--to=wdijkstr@arm.com \
--cc=libc-alpha@sourceware.org \
--cc=petar.jovanovic@rt-rk.com \
/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).