All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Fernando Pablo Lopez-Lezcano <nando@ccrma.Stanford.EDU>
Cc: Alsa-Devel <alsa-devel@lists.sourceforge.net>
Subject: Re: configuring for a different architecture
Date: Wed, 22 Jan 2003 10:14:18 +0100	[thread overview]
Message-ID: <s5h3cnl7dhx.wl@alsa2.suse.de> (raw)
In-Reply-To: <1043184753.26774.18.camel@cmn37.Stanford.EDU>

At 21 Jan 2003 13:32:33 -0800,
Fernando Pablo Lopez-Lezcano wrote:
> 
> It would be useful to have an option to force the alsa-driver configure
> script to use a target architecture for the build different from the
> architecture of the running kernel (ie: I'm running a i386 kernel but
> want to build for the same kernel, but with the i686 architecture). 
> 
> Or is there a way to do that already that I have missed?

the architecture must be anyway specified in the kernel source tree.
using a different architecture in the alsa-driver configuration will
confuse the compilation, which one should be picked up actually.

please note that the kernel tree doesn't have to be identical with the
one for the running kernel.  you can use a different kernel tree via
--with-kernel option of alsa-driver's configure script.
thus, a solution is to make a mirror of kernel-tree and change
linux/autoconf.h and linux/version.h to reflect the preferred
architecture target.


ciao,

Takashi


-------------------------------------------------------
This SF.net email is sponsored by: Scholarships for Techies!
Can't afford IT training? All 2003 ictp students receive scholarships.
Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more.
www.ictp.com/training/sourceforge.asp

      reply	other threads:[~2003-01-22  9:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-21 21:32 configuring for a different architecture Fernando Pablo Lopez-Lezcano
2003-01-22  9:14 ` Takashi Iwai [this message]

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=s5h3cnl7dhx.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=nando@ccrma.Stanford.EDU \
    /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.