From: Kai Kang <kai.kang@windriver.com>
To: <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH] Remove hdajacksensetest for framebuffer build
Date: Mon, 1 Jun 2015 15:23:52 +0800 [thread overview]
Message-ID: <1433143433-528-1-git-send-email-kai.kang@windriver.com> (raw)
Hi Richard,
I made some modification after make the commit, but I forgot to add it to the
commit for makefile_no_gtk.patch.
It requires glib for framebuffer build:
| checking for GLIB... no
| configure: error: Package requirements (glib-2.0) were not met:
|
| No package 'glib-2.0' found
|
Update makefile_no_gtk.patch again to remove the hdajacksensetest for
framebuffer build.
Sorry for inconvenient.
--Kai
Kai Kang (1):
alsa-tools: remove hdajacksensetest for framebuffer build
meta/recipes-multimedia/alsa/alsa-tools/makefile_no_gtk.patch | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
1.9.1
next reply other threads:[~2015-06-01 7:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-01 7:23 Kai Kang [this message]
2015-06-01 7:23 ` [PATCH] alsa-tools: remove hdajacksensetest for framebuffer build Kai Kang
2015-06-02 10:28 ` Burton, Ross
2015-06-03 23:25 ` Kang Kai
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=1433143433-528-1-git-send-email-kai.kang@windriver.com \
--to=kai.kang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.