Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Hofman <pavel.hofman@ivitera.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Compilation procedure from git/tiwai/sound-2.6.git
Date: Thu, 01 Oct 2009 22:06:56 +0200	[thread overview]
Message-ID: <4AC50BE0.9050206@ivitera.com> (raw)
In-Reply-To: <s5h4oqwxfoq.wl%tiwai@suse.de>

Takashi Iwai wrote:
> At Mon, 21 Sep 2009 20:38:08 +0200,
> 
> Use sound-2.6.git tree on kernel.org together with alsa-driver-build.git
> tree:
>   git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-2.6.git
>   git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/alsa-driver-build.git
> 

Hi Takashi,

I am sorry if I overlooked something but the gitcompile in
alsa-driver-build.git does not work with the sound-2.6.git:

The command is:
pavel@nahore:~/projects/alsa-git/alsa-driver-build$\
ALSAKERNELDIR=/home/pavel/projects/alsa-git/sound-2.6/sound/\
./gitcompile --with-cards="ice1724,usb-audio"

(backslash stands for one line)

gitcompile ends up with:

Hacking autoconf.h...
make[1]: Entering directory
`/home/pavel/projects/alsa-git/alsa-driver-build/include'
make -C sound prepare
make[2]: Entering directory
`/home/pavel/projects/alsa-git/alsa-driver-build/include/sound'
make prepare2
make[3]: Entering directory
`/home/pavel/projects/alsa-git/alsa-driver-build/include/sound'
cp ../../alsa-kernel/include/*.h .
cp: cannot stat `../../alsa-kernel/include/*.h': No such file or directory
make[3]: *** [*.h] Error 1
make[3]: Leaving directory
`/home/pavel/projects/alsa-git/alsa-driver-build/include/sound'
make[2]: *** [prepare] Error 2
make[2]: Leaving directory
`/home/pavel/projects/alsa-git/alsa-driver-build/include/sound'
make[1]: *** [prepare] Error 2
make[1]: Leaving directory
`/home/pavel/projects/alsa-git/alsa-driver-build/include'
make: *** [dep] Error 1


Thanks a lot for a brief description of the compilation procedure.

Best regards,


Pavel Hofman.

  parent reply	other threads:[~2009-10-01 20:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-16 20:25 [PATCH 1/7] ak4114 - fix errors in output selector bits pavel.hofman
2009-09-16 20:25 ` [PATCH 2/7] ak4620 support, codec regs listed in proc pavel.hofman
2009-09-16 20:25   ` [PATCH 3/7] ak4113 support pavel.hofman
2009-09-16 20:25     ` [PATCH 4/7] ice1724 - adding GPIO routines for mask and direction pavel.hofman
2009-09-16 20:25       ` [PATCH 5/7] ice1724 - pro-rate-locking makes sense only for internal clock mode pavel.hofman
2009-09-16 20:25         ` [PATCH 6/7] Support for multiple external clock types pavel.hofman
2009-09-16 20:25           ` [PATCH 7/7] Infrasonic Quartet support pavel.hofman
2009-09-21 14:10 ` [PATCH 1/7] ak4114 - fix errors in output selector bits Takashi Iwai
2009-09-21 18:38   ` Pavel Hofman
2009-09-21 19:26     ` Takashi Iwai
2009-09-23  9:16       ` Pavel Hofman
2009-09-23  9:21         ` Takashi Iwai
2009-09-23  9:32           ` Pavel Hofman
2009-09-23  9:56             ` Takashi Iwai
2009-10-01 20:06       ` Pavel Hofman [this message]
2009-10-02  5:49         ` Compilation procedure from git/tiwai/sound-2.6.git Takashi Iwai
2009-10-02  9:32           ` Pavel Hofman
2009-10-06 13:28             ` 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=4AC50BE0.9050206@ivitera.com \
    --to=pavel.hofman@ivitera.com \
    --cc=alsa-devel@alsa-project.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox