From: Leonid <leonopulos@gmail.com>
To: alsa-devel@alsa-project.org
Subject: Re: [Alsa-devel] how to cross compile the alsa util?
Date: Fri, 04 Feb 2011 16:05:10 +0300 [thread overview]
Message-ID: <4D4BF986.8030603@gmail.com> (raw)
Hello alls:
Please help.
I also cross compiled alsa utils trhough CodeSourcery:
PATH=$PATH:/opt/arm-2007q1/bin
CC=arm-none-linux-gnueabi-gcc ./configure --host=i686-pc-linux-gnu \
--target=arm-none-linux-gnueabi \
--with-alsa-prefix=/usr/lib \
--with-alsa-inc-prefix=/usr/include/alsa
configure out...
--cut
checking for ncursesw5-config... yes
checking for curses library... ncursesw
checking for curses header name...<ncurses.h>
checking for curses compiler flags... -I/usr/include/ncursesw
checking for curses NLS support... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking panel.h usability... no
checking panel.h presence... no
checking for panel.h... no
configure: error: required curses helper header not found
but libncursesw5 and aibncursesw5-dev is installed to host:
more...
I changet the configuration and add option --with-curses=ncurses
(libncurses5-dev also installed):
PATH=$PATH:/opt/arm-2007q1/bin
CC=arm-none-linux-gnueabi-gcc ./configure --host=i686-pc-linux-gnu \
--target=arm-none-linux-gnueabi \
--with-alsa-prefix=/usr/lib \
--with-alsa-inc-prefix=/usr/include/alsa \
--with-curses=ncurses
out...
--cut
checking for ncurses5-config... yes
checking for curses library... ncurses
checking for curses header name...<ncurses.h>
checking for curses compiler flags...
checking for curses NLS support... no
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking panel.h usability... no
checking panel.h presence... no
checking for panel.h... no
configure: error: required curses helper header not found
the same effect.
what am i doing wrong?
can be cross compiled ncurses?
--
with best wishes
Leonid
On Mon, 31 May 2004, Roc Wu wrote:
> Hello alls:
>
> Sorry for post the mail again. I posted it several
> days ago, but no response. Anybody can give me some
> hints?
>
> I cross compiled the alsa-lib-1.04 to arm platform.
> The 2.6.6 kernel including alsa driver is ok on our
> ARM board, so I want to test the driver. how to do it?
>
> I think maybe the first step is to crosscompile the
> alsa utils to play a wave audio file.
>
> CC=arm-linux-gcc ./configure --host=i686-linux
> --target=arm-linux
./configure --help
--- cut ---
--with-alsa-prefix=PFX Prefix where Alsa library is installed
(optional)
--with-alsa-inc-prefix=PFX Prefix where include libraries are
(optional)
--- cut ---
Jaroslav
-----
Jaroslav Kysela<[EMAIL PROTECTED]>
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs
next reply other threads:[~2011-02-04 13:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-04 13:05 Leonid [this message]
2011-02-04 13:22 ` [Alsa-devel] how to cross compile the alsa util? Clemens Ladisch
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=4D4BF986.8030603@gmail.com \
--to=leonopulos@gmail.com \
--cc=alsa-devel@alsa-project.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.