From: Adrian McMenamin <adrian@mcmen.demon.co.uk>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Cross compiling alsa-driver
Date: Thu, 06 Apr 2006 23:27:16 +0100 [thread overview]
Message-ID: <1144362437.9219.11.camel@localhost.localdomain> (raw)
In-Reply-To: <1144362206.9219.9.camel@localhost.localdomain>
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
next prev parent reply other threads:[~2006-04-06 22:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-04 21:56 Cross compiling alsa-driver Adrian McMenamin
2006-04-05 11:27 ` Takashi Iwai
2006-04-06 22:16 ` Adrian McMenamin
2006-04-06 22:23 ` Adrian McMenamin
2006-04-06 22:27 ` Adrian McMenamin [this message]
2006-04-06 22:25 ` Lee Revell
2006-04-06 22:29 ` Adrian McMenamin
2006-04-06 22:52 ` Lee Revell
2006-04-06 22:57 ` Lee Revell
2006-04-06 23:10 ` Adrian McMenamin
2006-04-06 23:15 ` Lee Revell
2006-04-06 23:25 ` Adrian McMenamin
2006-04-06 23:55 ` Lee Revell
2006-04-07 5:55 ` Manuel Jander
2006-04-06 22:46 ` Adrian McMenamin
2006-04-06 22:54 ` Lee Revell
2006-04-07 9:12 ` Takashi Iwai
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=1144362437.9219.11.camel@localhost.localdomain \
--to=adrian@mcmen.demon.co.uk \
--cc=alsa-devel@lists.sourceforge.net \
--cc=tiwai@suse.de \
/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.