From: Chen Qi <Qi.Chen@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Cc: chi.xu@windriver.com
Subject: [PATCH 0/1] bind: fix compile failure when building path is long
Date: Wed, 9 Sep 2015 13:40:02 +0800 [thread overview]
Message-ID: <cover.1441777155.git.Qi.Chen@windriver.com> (raw)
The following changes since commit 8402958cd2cb87b8283c8ee4e2d08e1a6717d67a:
pseudo_1.7.3.bb: New version of pseudo (2015-09-06 15:24:28 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib ChenQi/bind-long-path
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=ChenQi/bind-long-path
Chen Qi (1):
bind: fix compile failure when building path is long
...-gen.c-extend-DIRNAMESIZE-from-256-to-512.patch | 25 ++++++++++++++++++++++
meta/recipes-connectivity/bind/bind_9.10.2-P3.bb | 1 +
2 files changed, 26 insertions(+)
create mode 100644 meta/recipes-connectivity/bind/bind/0001-gen.c-extend-DIRNAMESIZE-from-256-to-512.patch
--
1.9.1
next reply other threads:[~2015-09-09 5:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-09 5:40 Chen Qi [this message]
2015-09-09 5:40 ` [PATCH 1/1] bind: fix compile failure when building path is long Chen Qi
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=cover.1441777155.git.Qi.Chen@windriver.com \
--to=qi.chen@windriver.com \
--cc=chi.xu@windriver.com \
--cc=openembedded-core@lists.openembedded.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