Re: [PATCH 1/2] alsa-tools: fix build when x11 and gtk+ not available

[Saul Wold <saul.wold@intel.com>]

On 04/08/2013 06:33 AM, Trevor Woerner wrote:
> With a rather recent HEAD
>
> Build Configuration:
> BB_VERSION        = "1.17.1"
> BUILD_SYS         = "x86_64-linux"
> NATIVELSBSTRING   = "openSUSE-project-12.3"
> TARGET_SYS        = "x86_64-poky-linux"
> MACHINE           = "qemux86-64"
> DISTRO            = "poky"
> DISTRO_VERSION    = "1.3+snapshot-20130407"
> TUNE_FEATURES     = "m64"
> TARGET_FPU        = ""
> meta
> meta-yocto
> meta-yocto-bsp    = "master:813127247a1100b1abe179dfba25795560eac864"
>
> I am able to successfully perform a "bitbake world" on a number of
> different targets:
>
> - qemux86
> - qemuarm
> - qemumips
> - qemux86-64
>
> Unfortunately qemuppcfails when building alsa-tools. Is anyone else
> seeing the same thing?
>
> | make[1]: Entering directory
> `/home/trevor/build/yocto/fullbuild/qemuppc/work/ppc603e-poky-linux/alsa-tools/1.0.26.1-r1/alsa-tools-1.0.26.1/hda-verb'
> | make[1]: warning: jobserver unavailable: using -j1.  Add `+' to parent
> make rule.
> | powerpc-poky-linux-gcc  -m32 -mhard-float  -mcpu=603e
> --sysroot=/home/trevor/build/yocto/fullbuild/qemuppc/sysroots/qemuppc
> -DPACKAGE_NAME=\"\" -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\"
> -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\"
> -DPACKAGE=\"hda-verb\" -DVERSION=\"0.4\" -DSTDC_HEADERS=1 -I.     -O2
> -Wall -pipe -g -MT hda-verb.o -MD -MP -MF .deps/hda-verb.Tpo -c -o
> hda-verb.o hda-verb.c
> | hda-verb.c:17:20: fatal error: sys/io.h: No such file or directory
> | compilation terminated.
> | make[1]: *** [hda-verb.o] Error 1
> | make[1]: Leaving directory
> `/home/trevor/build/yocto/fullbuild/qemuppc/work/ppc603e-poky-linux/alsa-tools/1.0.26.1-r1/alsa-tools-1.0.26.1/hda-verb'
> | make: *** [all] Error 1
> | ERROR: oe_runmake failed

I recall doing a patch for this, I just reviewed it and it seems I did 
not do the right #if directive.

I was fixing the mips build which had the same problem and did not 
correctly retest.

Patch out shortly.

Sau!