From: Saul Wold <sgw@linux.intel.com>
To: Nobuhiro Iwamatsu <nobuhiro.iwamatsu.yj@renesas.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] alsa-tools: Update autotools.patch
Date: Sat, 16 Mar 2013 16:04:19 -0700 [thread overview]
Message-ID: <5144FA73.4040204@linux.intel.com> (raw)
In-Reply-To: <CABMQnVKVnoMH1B1Ri-Qmjec30BFX1TaosGq0b1Hc641m3490hA@mail.gmail.com>
On 03/13/2013 06:43 PM, Nobuhiro Iwamatsu wrote:
> Hi,
>
> When I build alsa-tools, I could not build this with following error:
> ----
> checking for i586-oe-linux-pkg-config... no
> checking for pkg-config...
> /home/iwamatsu/yocto/alsa/tmp-eglibc/sysroots/x86_64-linux/usr/bin/pkg-config
> configure: WARNING: using cross tools not prefixed with host triplet
> checking pkg-config is at least version 0.9.0... yes
> checking for ENVY24CONTROL... no
> configure: error: Package requirements (gtk+-2.0 alsa >= 0.9.0) were not met:
>
> No package 'gtk+-2.0' found
>
What kind of image/packages are you building, it's possible that your
image does not have gtk+ included and it looks like alsa-tools should
depend on gtk+.
It might be better to add a PACKAGECONFIG with gtk+ for these instead of
just removing them.
You can see python-smartpm_1.4.1.bb as example of how it's done.
Sau!
> Consider adjusting the PKG_CONFIG_PATH environment variable if you
> installed software in a non-standard prefix.
>
> Alternatively, you may set the environment variables ENVY24CONTROL_CFLAGS
> and ENVY24CONTROL_LIBS to avoid the need to call pkg-config.
> See the pkg-config man page for more details.
> make: *** [all] Error 1
> ----
>
> The original patch is deleted from the list in the software depending on gtk.
> However, envy24control etc. are dependent on gtk.
> The patch which I created deletes these from a list.
> I checked with openembedded-core (375ed2eaef10dd7d8f46badca6d779708724e5f6).
>
> Does my environment have a problem?
>
> Best regards,
> Nobuhiro
>
> On Wed, Mar 13, 2013 at 8:02 PM, Iorga, Cristian
> <cristian.iorga@intel.com> wrote:
>> Hello Nobuhiro-san,
>>
>> Can you please explain your patch?
>> As far as I know, the alsa-tools present as targets were all buildable.
>> This was verified by me at last update.
>>
>> Regards,
>> Cristian
>>
>> -----Original Message-----
>> From: Nobuhiro Iwamatsu [mailto:iwamatsu@nigauri.org] On Behalf Of Nobuhiro Iwamatsu
>> Sent: Wednesday, March 13, 2013 4:09 AM
>> To: openembedded-core@lists.openembedded.org
>> Cc: Iorga, Cristian; Nobuhiro Iwamatsu
>> Subject: [PATCH] alsa-tools: Update autotools.patch
>>
>> envy24control, rmedigicontrol and echomixer require gtk+-2.0.
>> Remove envy24control rmedigicontrol and echomixer from list of tools.
>>
>> CC: Cristian Iorga <cristian.iorga@intel.com>
>> Signed-off-by: Nobuhiro Iwamatsu <nobuhiro.iwamatsu.yj@renesas.com>
>> ---
>> .../alsa/alsa-tools/autotools.patch | 6 +++---
>> .../recipes-multimedia/alsa/alsa-tools_1.0.26.1.bb | 2 +-
>> 2 files changed, 4 insertions(+), 4 deletions(-)
>>
>> diff --git a/meta/recipes-multimedia/alsa/alsa-tools/autotools.patch b/meta/recipes-multimedia/alsa/alsa-tools/autotools.patch
>> index 294e970..08dd9de 100644
>> --- a/meta/recipes-multimedia/alsa/alsa-tools/autotools.patch
>> +++ b/meta/recipes-multimedia/alsa/alsa-tools/autotools.patch
>> @@ -26,9 +26,9 @@ diff -ruN alsa-tools-1.0.24.1-orig//Makefile alsa-tools-1.0.24.1/Makefile
>> - mixartloader pcxhrloader rmedigicontrol sb16_csp seq sscape_ctl \
>> - us428control usx2yloader vxloader echomixer ld10k1 qlo10k1 \
>> - hwmixvolume hdajackretask hda-verb
>> -+SUBDIRS = ac3dec as10k1 envy24control \
>> -+ mixartloader pcxhrloader rmedigicontrol sb16_csp seq sscape_ctl \
>> -+ us428control usx2yloader vxloader echomixer \
>> ++SUBDIRS = ac3dec as10k1 \
>> ++ mixartloader pcxhrloader sb16_csp seq sscape_ctl \
>> ++ us428control usx2yloader vxloader \
>> + hwmixvolume hda-verb
>>
>> all:
>> diff --git a/meta/recipes-multimedia/alsa/alsa-tools_1.0.26.1.bb b/meta/recipes-multimedia/alsa/alsa-tools_1.0.26.1.bb
>> index 0fe4bee..4b4f29b 100644
>> --- a/meta/recipes-multimedia/alsa/alsa-tools_1.0.26.1.bb
>> +++ b/meta/recipes-multimedia/alsa/alsa-tools_1.0.26.1.bb
>> @@ -5,7 +5,7 @@ SECTION = "console/utils"
>> LICENSE = "GPLv2 & LGPLv2+"
>> DEPENDS = "alsa-lib ncurses"
>>
>> -PR = "r0"
>> +PR = "r1"
>>
>> LIC_FILES_CHKSUM = "file://hdsploader/COPYING;md5=94d55d512a9ba36caa9b7df079bae19f \
>> file://ld10k1/COPYING.LIB;md5=7fbc338309ac38fefcd64b04bb903e34"
>> --
>> 1.7.9.5
>>
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
>
next prev parent reply other threads:[~2013-03-16 23:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 2:09 [PATCH] alsa-tools: Update autotools.patch Nobuhiro Iwamatsu
2013-03-13 11:02 ` Iorga, Cristian
2013-03-14 1:43 ` Nobuhiro Iwamatsu
2013-03-16 23:04 ` Saul Wold [this message]
2013-03-18 6:31 ` Nobuhiro Iwamatsu
2013-03-29 13:18 ` Trevor Woerner
2013-04-02 15:59 ` Saul Wold
2013-04-02 17:46 ` Otavio Salvador
-- strict thread matches above, loose matches on Subject: below --
2013-04-03 0:30 Rogerio Nunes
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=5144FA73.4040204@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=nobuhiro.iwamatsu.yj@renesas.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