From: Takashi Iwai <tiwai@suse.de>
To: Eliot Blennerhassett <bigblen@icqmail.com>
Cc: eliot@blennerhassett.gen.nz, alsa-devel@lists.sourceforge.net
Subject: Re: Building alsa with kernel 2.6 when O= option used.
Date: Tue, 27 Jul 2004 15:56:44 +0200 [thread overview]
Message-ID: <s5h8yd55zab.wl@alsa2.suse.de> (raw)
In-Reply-To: <20040725195633.16610.h003.c012.wm@mail.icqmail.com.criticalpath.net>
At Sun, 25 Jul 2004 19:56:27 -0700 (PDT),
Eliot Blennerhassett wrote:
>
> Well it seems I am talking to myself here... and so I shall continue.
>
> The only way I have got alsa 1.0.5 driver to compile as an ordinary user is to
> get my own copy of the source tree, configure and build that, then continue to
> build the alsa driver.
>
> Following the instructions here helped
> http://alsa.opensrc.org/index.php?page=AlsaBuild2.6
>
> So I am on my way again, but I still think there is a bug in the build system
> that doesn't allow for Alsa build to work with "O=<path to my dir" kernel
> builds. I.e. avoiding taking an actual copy of the whole kernel source tree into
> <path to my dir>
A kind of 'O=' hack was added for SUSE kernel in the recent version.
It would be nicer to have a generic solution for such a situation,
though, e.g. a new configure option.
Takashi
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
next prev parent reply other threads:[~2004-07-27 13:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-26 2:56 Building alsa with kernel 2.6 when O= option used Eliot Blennerhassett
2004-07-27 13:56 ` Takashi Iwai [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-23 2:13 Eliot Blennerhassett
2004-07-23 1:59 Eliot Blennerhassett
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=s5h8yd55zab.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=bigblen@icqmail.com \
--cc=eliot@blennerhassett.gen.nz \
/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.