Cross compiling alsa-driver

Cross compiling alsa-driver

[Adrian McMenamin]

Cannot get this to work.

Doing it from cvs and from the package gives the same result...

./configure
--with-cross=~/buildroot/build_sh4/staging_dir/bin/sh4-linux-
--with-build=/home/adrian/linux-2.6.15.2

gives...

make[3]: Entering directory
`/home/adrian/alsa-driver-1.0.11rc4/pci/vx222'
make[3]: Leaving directory
`/home/adrian/alsa-driver-1.0.11rc4/pci/vx222'
make[3]: Entering directory
`/home/adrian/alsa-driver-1.0.11rc4/pci/ymfpci'
make[3]: Leaving directory
`/home/adrian/alsa-driver-1.0.11rc4/pci/ymfpci'
make[2]: Leaving directory `/home/adrian/alsa-driver-1.0.11rc4/pci'
make[1]: Leaving directory `/home/adrian/alsa-driver-1.0.11rc4'
make -C /lib/modules/2.6.12-10-686/build
SUBDIRS=/home/adrian/alsa-driver-1.0.11rc4 O=/home/adrian/linux-2.6.15.2
modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.12-10-686'
/usr/src/linux-headers-2.6.12-10-686/Makefile:530: /usr/src/linux-headers-2.6.12-10-686/arch//Makefile: No such file or directory
/bin/sh: /home/adrian/buildroot/build_sh4/staging_dir/bin/sh4-linux-gcc-3.4: No such file or directory
make[2]: *** No rule to make target
`/usr/src/linux-headers-2.6.12-10-686/arch//Makefile'.  Stop.
make[1]: *** [modules] Error 2
make[1]: Leaving directory `/usr/src/linux-headers-2.6.12-10-686'
make: *** [compile] Error 2

ie it is still looking for headers on the building machine.

Building from cvs gives a similar result.

The configure script appears to be broken...as this segment of output
suggests - as even though I specify a kernel directory it is still
looking elsewhere

checking for current directory... /home/adrian/alsa-driver-1.0.11rc4
checking cross
compile... /home/adrian/buildroot/build_sh4/staging_dir/bin/sh4-linux-
checking for directory with kernel
source... /lib/modules/2.6.12-10-686/build
checking for directory with kernel build... /home/adrian/linux-2.6.15.2







-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

Re: Cross compiling alsa-driver

[Takashi Iwai]

At Tue, 04 Apr 2006 22:56:59 +0100,
Adrian McMenamin wrote:
> 
> Cannot get this to work.
> 
> Doing it from cvs and from the package gives the same result...
> 
> ./configure
> --with-cross=~/buildroot/build_sh4/staging_dir/bin/sh4-linux-
> --with-build=/home/adrian/linux-2.6.15.2
> 
> gives...
> 
> make[3]: Entering directory
> `/home/adrian/alsa-driver-1.0.11rc4/pci/vx222'
> make[3]: Leaving directory
> `/home/adrian/alsa-driver-1.0.11rc4/pci/vx222'
> make[3]: Entering directory
> `/home/adrian/alsa-driver-1.0.11rc4/pci/ymfpci'
> make[3]: Leaving directory
> `/home/adrian/alsa-driver-1.0.11rc4/pci/ymfpci'
> make[2]: Leaving directory `/home/adrian/alsa-driver-1.0.11rc4/pci'
> make[1]: Leaving directory `/home/adrian/alsa-driver-1.0.11rc4'
> make -C /lib/modules/2.6.12-10-686/build
> SUBDIRS=/home/adrian/alsa-driver-1.0.11rc4 O=/home/adrian/linux-2.6.15.2
> modules
> make[1]: Entering directory `/usr/src/linux-headers-2.6.12-10-686'
> /usr/src/linux-headers-2.6.12-10-686/Makefile:530: /usr/src/linux-headers-2.6.12-10-686/arch//Makefile: No such file or directory
> /bin/sh: /home/adrian/buildroot/build_sh4/staging_dir/bin/sh4-linux-gcc-3.4: No such file or directory
> make[2]: *** No rule to make target
> `/usr/src/linux-headers-2.6.12-10-686/arch//Makefile'.  Stop.
> make[1]: *** [modules] Error 2
> make[1]: Leaving directory `/usr/src/linux-headers-2.6.12-10-686'
> make: *** [compile] Error 2
> 
> ie it is still looking for headers on the building machine.
> 
> Building from cvs gives a similar result.
> 
> The configure script appears to be broken...as this segment of output
> suggests - as even though I specify a kernel directory it is still
> looking elsewhere
> 
> checking for current directory... /home/adrian/alsa-driver-1.0.11rc4
> checking cross
> compile... /home/adrian/buildroot/build_sh4/staging_dir/bin/sh4-linux-
> checking for directory with kernel
> source... /lib/modules/2.6.12-10-686/build
> checking for directory with kernel build... /home/adrian/linux-2.6.15.2

You didn't pass a proper --with-kernel option.
See alsa-driver/INSTALL.


Takashi


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

Re: Cross compiling alsa-driver

[Adrian McMenamin]

On Wed, 2006-04-05 at 13:27 +0200, Takashi Iwai wrote:
> At Tue, 04 Apr 2006 22:56:59 +0100,

> 
> You didn't pass a proper --with-kernel option.
> See alsa-driver/INSTALL.
> 

Makes no difference. Still broken.

Long outputs follow - configure appears to ignore the specified
--with-build and --with-kernel options. I'll have a look at the script

adrian@bossclass:~/alsa-driver-1.0.11rc4$ ./configure
--with-cross=/home/adrian/buildroot/build_sh4/staging_dir/bin/sh4-linux-
--with-build=/home/adrian/linux-2.6.15.2 --with-cards=snd-aica
--with-kernel=/home/adrian/linux-2.6.15.2
checking for 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... no
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 for ranlib... ranlib
checking for a BSD-compatible install... /usr/bin/install -c
checking how to run the C preprocessor... gcc -E
checking for egrep... grep -E
checking for ANSI C header files... yes
checking for an ANSI C-conforming const... yes
checking for inline... inline
checking whether time.h and sys/time.h may both be included... yes
checking whether gcc needs -traditional... no
checking for current directory... /home/adrian/alsa-driver-1.0.11rc4
checking cross
compile... /home/adrian/buildroot/build_sh4/staging_dir/bin/sh4-linux-
checking for directory with kernel source... /home/adrian/linux-2.6.15.2
checking for directory with kernel build... /home/adrian/linux-2.6.15.2
checking for kernel linux/version.h... yes
checking for kernel linux/autoconf.h... yes
checking for kernel version... 2.6.15-sh
checking for GCC version... Kernel compiler: gcc 3.4.2 Used compiler:
sh4-linux-gcc (GCC) 3.4.2
checking for built-in ALSA... no
checking for existing ALSA module... yes
checking for Red Hat kernel... auto
checking for Red Hat kernel... no
checking for SUSE kernel... auto
checking for SUSE kernel... no
checking to modify of kernel linux/kmod.h... no
checking for kernel linux/compiler.h... yes
checking for kernel linux/pm.h... yes
checking for kernel linux/spinlock.h... yes
checking for kernel linux/irq.h... yes
checking for kernel linux/threads.h... yes
checking for kernel linux/rwsem.h... yes
checking for kernel linux/gameport.h... yes
checking for kernel linux/devfs_fs_kernel.h... yes
checking for kernel linux/highmem.h... yes
checking for kernel linux/workqueue.h... yes
checking for kernel linux/dma-mapping.h... yes
checking for kernel asm/hw_irq.h... yes
checking for kernel linux/device.h... yes
checking for kernel linux/platform_device.h... yes
checking for kernel linux/jiffies.h... yes
checking for kernel linux/compat.h... yes
checking for kernel linux/adb.h... yes
checking for kernel linux/cuda.h... yes
checking for kernel linux/pmu.h... yes
checking for kernel linux/moduleparam.h... yes
checking for kernel linux/syscalls.h... yes
checking for kernel linux/firmware.h... yes
checking for kernel linux/err.h... yes
checking for kernel linux/bitmap.h... yes
checking for kernel linux/mutex.h... no
Creating <linux/mutex.h>...
checking for kernel module symbol versions... no
checking for PCI support in kernel... yes
checking for I2C driver in kernel... unknown
checking for firmware loader... yes
checking for input subsystem in kernel... yes
checking for directory to store kernel
modules... /lib/modules/2.6.15-sh/kernel/sound
checking for verbose procfs... on
checking for verbose printk... on
checking for debug level... none
checking for ISA support in kernel... no
checking for processor type... unknown
checking for ISA DMA API... no
checking for SMP... no
checking for Video device support in kernel... no
checking for ISA PnP driver in kernel... yes
checking for PnP driver in kernel... yes
checking for Kernel ISA-PnP support... no
checking for Kernel ISA-PnP module support... no
checking for strlcpy... yes
checking for snprintf... yes
checking for vsnprintf... yes
checking for scnprintf... yes
checking for sscanf... yes
checking for vmalloc_to_page... yes
checking for old kmod... no
checking for PDE... yes
checking for pci_set_consistent_dma_mask... yes
checking for pci_dev_present... yes
checking for msleep... yes
checking for msleep_interrupt... yes
checking for msecs_to_jiffies... yes
checking for tty->count is the atomic type... no
checking for io_remap_pfn_range... yes
checking for kcalloc... yes
checking for kstrdup... yes
checking for kzalloc... yes
checking for create_workqueue with flags... no
checking for saved_config_space in pci_dev... yes
checking for new pci_save_state... yes
checking for register_sound_special_device... yes
checking for driver version... 1.0.11rc4
checking for sequencer support... yes
checking for OSS/Free emulation... yes
checking for OSS PCM plugin system inclusion... yes
checking for RTC callback support in kernel... yes
checking for HPET support... no
checking for dynamic minor numbers... no
checking for support of old API... yes
checking for Procfs support... yes
checking for USB support... no
checking for USB module support... no
checking for class_simple... no
checking for old driver suspend/resume callbacks... no
checking for removal of page-reservation for nopage/mmap... yes
checking for nested class_device... yes
checking for PnP suspend/resume... no
checking for new unlocked/compat_ioctl... yes
checking for PC-Speaker hook... no
checking for kernel PCMCIA
checking for PCMCIA support... no
checking for PCMCIA module support... no
checking for PC9800 support in kernel... no
checking for parallel port support... no
checking for parallel port module support... no
checking for which soundcards to compile driver for... configure: error:
Unknown soundcard snd-aica
adrian@bossclass:~/alsa-driver-1.0.11rc4$





-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

Re: Cross compiling alsa-driver

[Adrian McMenamin]

On Thu, 2006-04-06 at 23:16 +0100, Adrian McMenamin wrote:
> On Wed, 2006-04-05 at 13:27 +0200, Takashi Iwai wrote:
> > At Tue, 04 Apr 2006 22:56:59 +0100,
> 
> > 
> > You didn't pass a proper --with-kernel option.
> > See alsa-driver/INSTALL.
> > 
> 
> Makes no difference. Still broken.
> 
> Long outputs follow - configure appears to ignore the specified
> --with-build and --with-kernel options. I'll have a look at the script
> 
Appears to be broken

echo "$as_me:$LINENO: checking for directory with kernel source" >&5
echo $ECHO_N "checking for directory with kernel source... $ECHO_C" >&6
if test -d "/lib/modules/`uname -r`/source" -o -L "/lib/modules/`uname
-r`/source"; then
  DEFAULT_KERNEL_DIR="/lib/modules/`uname -r`/source"
  DEFAULT_KERNEL_BUILD="/lib/modules/`uname -r`/build"
elif test -d "/lib/modules/`uname -r`/build" -o -L "/lib/modules/`uname
-r`/build"; then
  DEFAULT_KERNEL_DIR="/lib/modules/`uname -r`/build"
else
  DEFAULT_KERNEL_DIR="/usr/src/linux"
fi



I know nothing about configure scripts but this looks to me like it just
assumes we're building for the current machine and ignores the cross
options. Is that right?



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

Re: Cross compiling alsa-driver

[Adrian McMenamin]

On Thu, 2006-04-06 at 23:23 +0100, Adrian McMenamin wrote:
> On Thu, 2006-04-06 at 23:16 +0100, Adrian McMenamin wrote:
> > On Wed, 2006-04-05 at 13:27 +0200, Takashi Iwai wrote:
> > > At Tue, 04 Apr 2006 22:56:59 +0100,
> > 
> > > 
> > > You didn't pass a proper --with-kernel option.
> > > See alsa-driver/INSTALL.
> > > 
> > 
> > Makes no difference. Still broken.
> > 
> > Long outputs follow - configure appears to ignore the specified
> > --with-build and --with-kernel options. I'll have a look at the script
> > 
> Appears to be broken
> 
> echo "$as_me:$LINENO: checking for directory with kernel source" >&5
> echo $ECHO_N "checking for directory with kernel source... $ECHO_C" >&6
> if test -d "/lib/modules/`uname -r`/source" -o -L "/lib/modules/`uname
> -r`/source"; then
>   DEFAULT_KERNEL_DIR="/lib/modules/`uname -r`/source"
>   DEFAULT_KERNEL_BUILD="/lib/modules/`uname -r`/build"
> elif test -d "/lib/modules/`uname -r`/build" -o -L "/lib/modules/`uname
> -r`/build"; then
>   DEFAULT_KERNEL_DIR="/lib/modules/`uname -r`/build"
> else
>   DEFAULT_KERNEL_DIR="/usr/src/linux"
> fi
> 
> 

Scrub the above... this appears later

CONFIG_SND_KERNELDIR="$kerneldir"
echo "$as_me:$LINENO: result: $kerneldir" >&5
echo "${ECHO_T}$kerneldir" >&6

echo "$as_me:$LINENO: checking for directory with kernel build" >&5
echo $ECHO_N "checking for directory with kernel build... $ECHO_C" >&6

# Check whether --with-build or --without-build was given.
if test "${with_build+set}" = set; then
  withval="$with_build"
  kernelbuild="$withval"
else
  kernelbuild="$DEFAULT_KERNEL_BUILD"

fi;
CONFIG_SND_KERNELBUILD="$kernelbuild"
echo "$as_me:$LINENO: result: $kernelbuild" >&5
echo "${ECHO_T}$kernelbuild" >&6


> 
> I know nothing about configure scripts but this looks to me like it just
> assumes we're building for the current machine and ignores the cross
> options. Is that right?
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting language
> that extends applications into web and mobile media. Attend the live webcast
> and join the prime developer group breaking into this new coding territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/alsa-devel



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

Re: Cross compiling alsa-driver

[Lee Revell]

On Thu, 2006-04-06 at 23:16 +0100, Adrian McMenamin wrote:
> checking for directory with kernel
> source... /home/adrian/linux-2.6.15.2
> checking for directory with kernel
> build... /home/adrian/linux-2.6.15.2 

It's not ignoring them.  It sounds like you just need to add aica to the
build scripts.

What is the output of "grep aica ./configure"?

Lee



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

Re: Cross compiling alsa-driver

[Adrian McMenamin]

On Thu, 2006-04-06 at 18:25 -0400, Lee Revell wrote:
> On Thu, 2006-04-06 at 23:16 +0100, Adrian McMenamin wrote:
> > checking for directory with kernel
> > source... /home/adrian/linux-2.6.15.2
> > checking for directory with kernel
> > build... /home/adrian/linux-2.6.15.2 
> 
> It's not ignoring them.  It sounds like you just need to add aica to the
> build scripts.
> 
> What is the output of "grep aica ./configure"?
> 


I know that aica isn't in there - but the general build should still
work and it doesn't...

make[2]: Leaving directory `/home/adrian/alsa-driver-1.0.11rc4/pci'
make[1]: Leaving directory `/home/adrian/alsa-driver-1.0.11rc4'
make -C /lib/modules/2.6.12-10-686/build
SUBDIRS=/home/adrian/alsa-driver-1.0.11rc4 O=/home/adrian/linux-2.6.15.2
modules
make[1]: Entering directory `/usr/src/linux-headers-2.6.12-10-686'
/usr/src/linux-headers-2.6.12-10-686/Makefile:530: /usr/src/linux-headers-2.6.12-10-686/arch//Makefile: No such file or directory
/bin/sh: /home/adrian/buildroot/build_sh4/staging_dir/bin/sh4-linux-gcc-3.4: No such file or directory
make[2]: *** No rule to make target
`/usr/src/linux-headers-2.6.12-10-686/arch//Makefile'.  Stop.
make[1]: *** [modules] Error 2
make[1]: Leaving directory `/usr/src/linux-headers-2.6.12-10-686'




-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

Re: Cross compiling alsa-driver

[Lee Revell]

On Thu, 2006-04-06 at 23:29 +0100, Adrian McMenamin wrote:
> On Thu, 2006-04-06 at 18:25 -0400, Lee Revell wrote:
> > On Thu, 2006-04-06 at 23:16 +0100, Adrian McMenamin wrote:
> > > checking for directory with kernel
> > > source... /home/adrian/linux-2.6.15.2
> > > checking for directory with kernel
> > > build... /home/adrian/linux-2.6.15.2 
> > 
> > It's not ignoring them.  It sounds like you just need to add aica to the
> > build scripts.
> > 
> > What is the output of "grep aica ./configure"?
> > 
> 
> 
> I know that aica isn't in there - but the general build should still
> work and it doesn't...
> 
> make[2]: Leaving directory `/home/adrian/alsa-driver-1.0.11rc4/pci'
> make[1]: Leaving directory `/home/adrian/alsa-driver-1.0.11rc4'
> make -C /lib/modules/2.6.12-10-686/build
> SUBDIRS=/home/adrian/alsa-driver-1.0.11rc4 O=/home/adrian/linux-2.6.15.2
> modules
> make[1]: Entering directory `/usr/src/linux-headers-2.6.12-10-686'
> /usr/src/linux-headers-2.6.12-10-686/Makefile:530: /usr/src/linux-headers-2.6.12-10-686/arch//Makefile: No such file or directory
> /bin/sh: /home/adrian/buildroot/build_sh4/staging_dir/bin/sh4-linux-gcc-3.4: No such file or directory
> make[2]: *** No rule to make target
> `/usr/src/linux-headers-2.6.12-10-686/arch//Makefile'.  Stop.
> make[1]: *** [modules] Error 2
> make[1]: Leaving directory `/usr/src/linux-headers-2.6.12-10-686'
> 

If the configure script bombs out, then I would not expect running make
afterwards to work.  It's probably an old Makefile.

Try adding your device to ./configure



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

Re: Cross compiling alsa-driver

[Lee Revell]

On Thu, 2006-04-06 at 23:29 +0100, Adrian McMenamin wrote:
> I know that aica isn't in there - but the general build should still
> work and it doesn't... 

Nope - I just tested it by removing the Makefile and running ./configure
with a made up card and it does not generate a new Makefile.  So it must
be using an old one with incorrect kernel source locations.

Lee



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

Re: Cross compiling alsa-driver

[Adrian McMenamin]

On Thu, 2006-04-06 at 18:57 -0400, Lee Revell wrote:
> On Thu, 2006-04-06 at 23:29 +0100, Adrian McMenamin wrote:
> > I know that aica isn't in there - but the general build should still
> > work and it doesn't... 
> 
> Nope - I just tested it by removing the Makefile and running ./configure
> with a made up card and it does not generate a new Makefile.  So it must
> be using an old one with incorrect kernel source locations.
> 
Sorry, do you mean I am wrong or do you mean the configure script is
wrong?



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

Re: Cross compiling alsa-driver

[Lee Revell]

On Fri, 2006-04-07 at 00:10 +0100, Adrian McMenamin wrote:
> On Thu, 2006-04-06 at 18:57 -0400, Lee Revell wrote:
> > On Thu, 2006-04-06 at 23:29 +0100, Adrian McMenamin wrote:
> > > I know that aica isn't in there - but the general build should still
> > > work and it doesn't... 
> > 
> > Nope - I just tested it by removing the Makefile and running ./configure
> > with a made up card and it does not generate a new Makefile.  So it must
> > be using an old one with incorrect kernel source locations.
> > 
> Sorry, do you mean I am wrong or do you mean the configure script is
> wrong?
> 
> 

http://www.alsa-project.org/~iwai/writing-an-alsa-driver/x1658.htm




-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

Re: Cross compiling alsa-driver

[Adrian McMenamin]

On Thu, 2006-04-06 at 19:15 -0400, Lee Revell wrote:
> On Fri, 2006-04-07 at 00:10 +0100, Adrian McMenamin wrote:
> > On Thu, 2006-04-06 at 18:57 -0400, Lee Revell wrote:
> > > On Thu, 2006-04-06 at 23:29 +0100, Adrian McMenamin wrote:
> > > > I know that aica isn't in there - but the general build should still
> > > > work and it doesn't... 
> > > 
> > > Nope - I just tested it by removing the Makefile and running ./configure
> > > with a made up card and it does not generate a new Makefile.  So it must
> > > be using an old one with incorrect kernel source locations.
> > > 
> > Sorry, do you mean I am wrong or do you mean the configure script is
> > wrong?
> > 
> > 
> 
> http://www.alsa-project.org/~iwai/writing-an-alsa-driver/x1658.htm
> 

And your point is?

I've written those files. cvscompile bombs



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

Re: Cross compiling alsa-driver

[Lee Revell]

On Fri, 2006-04-07 at 00:25 +0100, Adrian McMenamin wrote:
> And your point is?
> 
> I've written those files. cvscompile bombs 

It looks like you just need to add something like:

ifeq (y,$(CONFIG_SH))
SUBDIRS  += sh
endif

to alsa-driver/Makefile, then create alsa-driver/sh/Makefile like:

ifndef SND_TOPDIR
SND_TOPDIR=..
endif

include $(SND_TOPDIR)/toplevel.config
include $(SND_TOPDIR)/Makefile.conf

include $(SND_TOPDIR)/alsa-kernel/sh/Makefile

include $(SND_TOPDIR)/Rules.make

Then create alsa-kernel/sh/Makefile:

#
# Makefile for ALSA
#

snd-aica-objs := aica.o

# Toplevel Module Dependency
obj-$(CONFIG_SND_AICA) += snd-aica.o

and put your code and Kconfig file in alsa-kernel/sh/






-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

Re: Cross compiling alsa-driver

[Manuel Jander]

Hi,

On Thu, 2006-04-06 at 23:29 +0100, Adrian McMenamin wrote:
> I know that aica isn't in there - but the general build should still
> work and it doesn't...
> 
> make[2]: Leaving directory `/home/adrian/alsa-driver-1.0.11rc4/pci'
> make[1]: Leaving directory `/home/adrian/alsa-driver-1.0.11rc4'
> make -C /lib/modules/2.6.12-10-686/build
> SUBDIRS=/home/adrian/alsa-driver-1.0.11rc4 O=/home/adrian/linux-2.6.15.2
> modules
> make[1]: Entering directory `/usr/src/linux-headers-2.6.12-10-686'
> /usr/src/linux-headers-2.6.12-10-686/Makefile:530: /usr/src/linux-headers-2.6.12-10-686/arch//Makefile: No such file or directory
> /bin/sh: /home/adrian/buildroot/build_sh4/staging_dir/bin/sh4-linux-gcc-3.4: No such file or directory
> make[2]: *** No rule to make target
> `/usr/src/linux-headers-2.6.12-10-686/arch//Makefile'.  Stop.
> make[1]: *** [modules] Error 2
> make[1]: Leaving directory `/usr/src/linux-headers-2.6.12-10-686'
> 

I had this same problem while crosscompiling, and the only way to get
around I found was specifying an appropriate ARCH environment variable
(ARCH=arm).

The path:
/usr/src/linux-headers-2.6.12-10-686/arch//Makefile

would become:

/usr/src/linux-headers-2.6.12-10-686/arch/arm/Makefile
or
/usr/src/linux-headers-2.6.12-10-686/arch/sh4/Makefile

Best Regards,
Manuel




-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

Re: Cross compiling alsa-driver

[Adrian McMenamin]

On Thu, 2006-04-06 at 18:25 -0400, Lee Revell wrote:
> On Thu, 2006-04-06 at 23:16 +0100, Adrian McMenamin wrote:
> > checking for directory with kernel
> > source... /home/adrian/linux-2.6.15.2
> > checking for directory with kernel
> > build... /home/adrian/linux-2.6.15.2 
> 
> It's not ignoring them.  It sounds like you just need to add aica to the
> build scripts.
> 
> What is the output of "grep aica ./configure"?
> 
How do I add aica to it anyway? :)



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

Re: Cross compiling alsa-driver

[Lee Revell]

On Thu, 2006-04-06 at 23:46 +0100, Adrian McMenamin wrote:
> On Thu, 2006-04-06 at 18:25 -0400, Lee Revell wrote:
> > On Thu, 2006-04-06 at 23:16 +0100, Adrian McMenamin wrote:
> > > checking for directory with kernel
> > > source... /home/adrian/linux-2.6.15.2
> > > checking for directory with kernel
> > > build... /home/adrian/linux-2.6.15.2 
> > 
> > It's not ignoring them.  It sounds like you just need to add aica to the
> > build scripts.
> > 
> > What is the output of "grep aica ./configure"?
> > 
> How do I add aica to it anyway? :)
> 

I'm not sure (is it in the driver guide?).  For starters I would just
copy the "emu10k1" entry in ./configure and substitute "aica" etc

Lee



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

Re: Cross compiling alsa-driver

[Takashi Iwai]

At Thu, 06 Apr 2006 23:16:49 +0100,
Adrian McMenamin wrote:
> 
> On Wed, 2006-04-05 at 13:27 +0200, Takashi Iwai wrote:
> > At Tue, 04 Apr 2006 22:56:59 +0100,
> 
> > 
> > You didn't pass a proper --with-kernel option.
> > See alsa-driver/INSTALL.
> > 
> 
> Makes no difference. Still broken.
> 
> Long outputs follow - configure appears to ignore the specified
> --with-build and --with-kernel options. I'll have a look at the script
> 
> adrian@bossclass:~/alsa-driver-1.0.11rc4$ ./configure
> --with-cross=/home/adrian/buildroot/build_sh4/staging_dir/bin/sh4-linux-
> --with-build=/home/adrian/linux-2.6.15.2 --with-cards=snd-aica
> --with-kernel=/home/adrian/linux-2.6.15.2
(snip)
> checking for processor type... unknown
                                 ^^^^^^^
configure doesn't know yet sh arch.

And, the below is a different problem.  Is the path correct?

/bin/sh: /home/adrian/buildroot/build_sh4/staging_dir/bin/sh4-linux-gcc-3.4: No such file or directory


Takashi


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642