Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Stanley <Ben.Stanley@exemail.com.au>
To: Eliot Blennerhassett <linux@audioscience.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: HG -> GIT migration
Date: Fri, 23 May 2008 12:31:08 +1000	[thread overview]
Message-ID: <1211509868.3811.119.camel@localhost> (raw)
In-Reply-To: <200805221016.27143.linux@audioscience.com>

I get the same problem as Eliot. The procedure 
$ git clone git://git.alsa-project.org/alsa-kmirror.git alsa-kmirror
$ git clone git://git.alsa-project.org/alsa-driver.git alsa-driver  
$ cd alsa-driver
$ ./gitcompile

results in

No alsa-kernel is found.
Please specify the correct location via ALSAKERNELDIR environment variable.

The problem is masked once alsa-driver/alsa-kernel exists, 
which can be arranged by running once

$ ALSAKERNELDIR=../alsa-kmirror ./gitcompile

I haven't found how this creates the link though.

The Makefile references ../alsa-kmirror by default, 
but the gitcompile (and probably other stuff too) needs to be updated to agree. 

This solves one of the problems mentioned in my other post. Now that I
know how to get around this, I'll try it on the RH kernel.

Ben Stanley.


On Thu, 2008-05-22 at 10:16 +1200, Eliot Blennerhassett wrote:
> On Wednesday 21 May 2008 18:09:17 you wrote:
> > It's not required to set ALSAKERNELDIR to ../alsa-kmirror - it's default
> > now.
> 
> Without it I get this:
> 
> cd alsa-driver/
> eliot@zaphod:~/src/alsagit/alsa-driver$ ./gitcompile
> No alsa-kernel is found.
> Please specify the correct location via ALSAKERNELDIR environment variable.
> 
> 
> Looking at gitcompile script it doesn't mention alsa-kmirror
> 
> Meanwhile I will avoid the error by specifying the cards I'm interested in.
> 
> --
> Eliot
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2008-05-23  2:31 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-20 11:21 HG -> GIT migration Jaroslav Kysela
2008-05-20 14:12 ` Ben Stanley
2008-05-20 14:24   ` Jaroslav Kysela
2008-05-21  2:30 ` Eliot Blennerhassett
2008-05-21  6:09   ` Jaroslav Kysela
2008-05-21 10:28     ` Takashi Iwai
2008-05-21 12:30       ` Rene Herman
2008-05-21 12:37         ` Takashi Iwai
2008-05-21 13:04           ` Rene Herman
2008-05-21 13:48             ` [alsa-devel] " Jaroslav Kysela
2008-05-21 14:40               ` Rene Herman
2008-05-21 14:52                 ` Takashi Iwai
2008-05-21 15:29                   ` Rene Herman
2008-05-22  1:24                     ` [alsa-devel] " Stephen Rothwell
2008-05-22 20:43                       ` Rene Herman
2008-05-22 23:40                         ` Stephen Rothwell
2008-05-21 14:47             ` Takashi Iwai
2008-05-21 15:40               ` Rene Herman
2008-05-21 16:02                 ` Takashi Iwai
2008-05-21 16:16                   ` [alsa-devel] " Linus Torvalds
2008-05-21 16:51                     ` Takashi Iwai
2008-05-21 17:07                       ` Tobin Davis
2008-05-21 17:19                         ` Jaroslav Kysela
2008-05-21 17:22                         ` Rene Herman
2008-05-21 17:43                       ` [alsa-devel] " Linus Torvalds
2008-05-21 18:11                         ` Linus Torvalds
2008-05-21 18:25                           ` [alsa-devel] " david
2008-05-21 18:39                             ` Linus Torvalds
2008-05-21 18:49                             ` Takashi Iwai
2008-05-21 18:47                         ` Takashi Iwai
2008-05-21 19:02                           ` Linus Torvalds
2008-05-21 21:08                             ` Takashi Iwai
2008-05-22 14:23               ` [alsa-devel] " Dmitry Torokhov
2008-05-21 22:16     ` Eliot Blennerhassett
2008-05-23  2:31       ` Ben Stanley [this message]
2008-05-23  6:38         ` Jaroslav Kysela

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=1211509868.3811.119.camel@localhost \
    --to=ben.stanley@exemail.com.au \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux@audioscience.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox