Problem building alsa-utils

GabrielO — Wed, 21 Mar 2012 16:49:45 GMT

Hi,

I can't build alsa-utils. I've managed to build alsa-lib in ltib but I'm getting an error when I'm trying to build alsa-utils:

lucid@ubuntu:~/ltib$ ./ltib -m scbuild -p alsa-utils.spec

Processing: alsa-utils
========================
Build path taken because: directory build, build key set, no prebuilt rpm,

rpmbuild --dbpath /home/lucid/ltib/rootfs//var/lib/rpm --target arm --define '_unpackaged_files_terminate_build 0' --define '_target_cpu arm' --define '__strip strip' --define '_topdir /home/lucid/ltib/rpm' --define '_prefix /usr' --define '_tmppath /home/lucid/ltib/tmp' --define '_rpmdir /home/lucid/ltib/rpm/RPMS' --define '_mandir /usr/share/man' --define '_sysconfdir /etc' --define '_localstatedir /var' -bc --short-circuit /home/lucid/ltib/dist/lfs-5.1/alsa-utils/alsa-utils.spec
Building target platforms: arm
Building for target arm
Executing(%build): /bin/sh -e /home/lucid/ltib/tmp/rpm-tmp.49584
+ umask 022
+ cd /home/lucid/ltib/rpm/BUILD
+ cd alsa-utils-1.0.11rc2
+ [ -n ]
+ [ arm = m68knommu ]
+ eval ./configure --prefix=/usr --host=arm-linux --build=i686-pc-linux-gnu -C
+ ./configure --prefix=/usr --host=arm-linux --build=i686-pc-linux-gnu -C
configure: loading cache config.cache
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for arm-linux-strip... arm-linux-strip
checking whether NLS is requested... yes
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/msgfmt
checking for xgettext... /usr/bin/xgettext
checking for msgmerge... /usr/bin/msgmerge
checking for style of include used by make... GNU
checking for arm-linux-gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... yes
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking dependency style of gcc... gcc3
checking build system type... i686-pc-linux-gnu
checking host system type... arm-unknown-linux-gnu
checking for ld used by GCC... ld
checking if the linker (ld) is GNU ld... yes
checking for shared library run path origin... done
checking whether NLS is requested... yes
checking for GNU gettext in libc... yes
checking whether to use NLS... yes
checking where the gettext function comes from... libc
checking for cross-compiler... gcc
checking for arm-linux-gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ANSI C... (cached) none needed
checking dependency style of gcc... (cached) gcc3
checking for a BSD-compatible install... /usr/bin/install -c
checking whether ln -s works... yes
checking for ALSA CFLAGS...
checking for ALSA LDFLAGS... -lasound -lm -ldl -lpthread
checking for libasound headers version >= 1.0.9... found.
checking for snd_ctl_open in -lasound... yes
checking how to run the C preprocessor... gcc -E
checking for egrep... grep -E
checking for ANSI C header files... yes
checking for initscr in -lncurses... no
checking for initscr in -lcurses... no
configure: error: this packages requires a curses library
error: Bad exit status from /home/lucid/ltib/tmp/rpm-tmp.49584 (%build)

Can any one help me?

Re: Problem building alsa-utils

dingram1z — Wed, 21 Mar 2012 17:30:17 GMT

Hi Gabriel:

If you run './ltib -c', scroll down to the "Package list", highlight "alsa-utils" and select "Help", "Selects: PKG_ALSA_LIB && PKG_NCURSES" tells you these are required. When you select "alsa-utils", the two requirements will be selected automatically [...]. When 'ltib' rebuilds, this should fix your "configure: error: this packages requires a curses library".

Good luck,

Darrell

Re: Problem building alsa-utils

GabrielO — Wed, 21 Mar 2012 19:10:29 GMT

Hi dingram,

Thanks a lot for the reply. I've managed to build alsa-utils after I've checked the prerequirements packs.

But now I have another problem with arecord.

I'm trying to test the board mic and speakers with arecord and apaly.

this are my board sound devices:

**** List of CAPTURE Hardware Devices ****
card 0: mxsevk [mxs-evk], device 0: SGTL5000 SGTL5000-0 []
Subdevices: 1/1
Subdevice #0: subdevice #0

**** List of PLAYBACK Hardware Devices ****
card 0: mxsevk [mxs-evk], device 0: SGTL5000 SGTL5000-0 []
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: mxsevk_1 [mxs-evk], device 0: MXS SPDIF mxs spdif-0 []
Subdevices: 1/1
Subdevice #0: subdevice #0

Now when I try to record a file with:

arecord -d 5 -c 2 -f S16_LE -N -M -r 8000 -D hw:0,0 file.wav

the file is created but when i play it :

aplay file.wav

no sound is heard.

I've tested aplay with an downloaded .wav file and it work OK.

But the file created by arecord has no sound or I'm not setting the params correctly.

If some one could help me with this I will highly appreciate it.

Thanks,

Gabriel

i.MX ProcessorsのトピックProblem building alsa-utils

Problem building alsa-utils

Re: Problem building alsa-utils

Re: Problem building alsa-utils