From: Jie Jiang <jjinfo@nudt.edu.cn>
To: alsa-devel@alsa-project.org
Subject: Cross-compile problem with alsa-driver version 1.0.22
Date: Sun, 03 Jan 2010 01:38:41 +0800 [thread overview]
Message-ID: <462453116.31236@nudt.edu.cn> (raw)
Message-ID: <1262453921.27961.1.camel@UT43> (raw)
Hi all,
Recently I downloaded alsa-driver 1.0.22 and tried to build for i.MX27
platform.
The "INSTALL" file enclosed in this release requires
"--with-cross=arm-linux-" configuration option to cross-compile alsa
driver for this ARM platform.
Here is my build process
#./configure --with-cross=arm-linux-
--with-kernel=/home/working/bsp/Kernel/linux-2.6.19.2
--with-build=/home/working/bsp/ Kernel/linux-2.6.19.2
--with-moddir=/home/working/bsp/tmp --with-debug=full
--enable-dynamic-minors --with-cards=all
checking for gcc... arm-linux-gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... configure: error: cannot run C
compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.
It seems that "--host=arm-linux" should be provided to configure script.
However, when given the --host option, in the generated "Makefile.conf",
I saw the following outputs, which are very confusing:
NEW_KBUILD =
mainsrcdir = .
MAINSRCDIR = /work/63/alsa/alsa-driver-1.0.22
CROSS_COMPILE ?= arm-linux-
ARCH ?=
ifdef NEW_KBUILD
CC = $(CROSS_COMPILE)arm-linux-gcc
CPP = $(CROSS_COMPILE)arm-linux-gcc -E
export CROSS_COMPILE ARCH
else
AS = $(CROSS_COMPILE)as
LD = $(CROSS_COMPILE)ld
CC = $(CROSS_COMPILE)arm-linux-gcc
CPP = $(CROSS_COMPILE)arm-linux-gcc -E
AR = $(CROSS_COMPILE)ar
MODFLAGS = -DMODULE=1
CFLAGS_KERNEL =
GENKSYMS = /sbin/genksyms -k 0.0.0
endif
Obviously, the CC and CPP variables are not expected as "arm-linux-gcc".
(There is one more $(CROSS_COMPILE)!)
I overcome this problem by providing CC and CROSS_COMPILE variables with
configure script:
CC=gcc CROSS_COMPILE=arm-linux-gcc ./configure --with-cross=arm-linux-
--with-kernel=/home/working/bsp/Kernel/linux-2.6.19.2
--with-build=/home/working/bsp/Kernel/linux-2.6.19.2
--with-moddir=/home/working/bsp/tmp --with-debug=full
--enable-dynamic-minors --with-cards=all
Then things become OK.
What's wrong with the "INSTALL" file?
Another problem.
Even if "--with-cards=all" is given, codes in soc/codecs, soc/imx, and
many other subdirs are not built. It seems that the configure script
sets some variables according to the kernel version and target platform
and outputs into "toplevel.config". Is it possible to manually edit
"toplevel.config" file (after configure process) to get soc/codecs,
soc/imx codes compiled?
Regards,
Jie
next reply other threads:[~2010-01-02 17:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-02 17:38 Jie Jiang [this message]
2010-01-02 17:38 ` Cross-compile problem with alsa-driver version 1.0.22 Jie Jiang
2010-01-03 11:09 ` Marek Vasut
-- strict thread matches above, loose matches on Subject: below --
2010-01-03 3:08 Jie Jiang
2010-01-03 3:08 ` Jie Jiang
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=462453116.31236@nudt.edu.cn \
--to=jjinfo@nudt.edu.cn \
--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.