From: Jeff Law <law@redhat.com>
To: ma.jiang@zte.com.cn, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] remove invalid "tail +16c"
Date: Thu, 01 Dec 2016 23:03:00 -0000 [thread overview]
Message-ID: <0d93262f-1977-e53a-5536-862864e34807@redhat.com> (raw)
In-Reply-To: <OF3FBC6FFD.5DB39B2E-ON48258074.000FDB3B-48258074.0022F05F@zte.com.cn>
On 11/22/2016 11:22 PM, ma.jiang@zte.com.cn wrote:
> Hi all,
> In "config/acx.m4", there are still some "tail +16c" which are invalid
> on POSIX systems.
> In my opinion拢卢 all "tail +16c" should be changed to "tail -c +16"
> directly, as most systems has accept the latter.
> And, to skip first 16 bytes, we should use "tail -c +17" instead of
> "tail -c +16".
>
> * config/acx.m4:Change "tail +16c" to "tail -c +17".
> * configure: Regenerate.
Thanks. I've installed this on the trunk after bootstrap & regression
testing on x86_64-linux-gnu.
jeff
next prev parent reply other threads:[~2016-12-01 23:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 6:26 ma.jiang
2016-12-01 23:03 ` Jeff Law [this message]
2016-12-02 10:29 ` ma.jiang
2016-11-28 2:49 ma.jiang
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=0d93262f-1977-e53a-5536-862864e34807@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=ma.jiang@zte.com.cn \
/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).