From: Brad Figg <brad.figg@canonical.com>
To: alsa-devel@alsa-project.org
Subject: Problems building the daily snapshot...
Date: Wed, 16 Jun 2010 15:05:29 -0700 [thread overview]
Message-ID: <4C194AA9.205@canonical.com> (raw)
I had been building the daily snapshot from:
http://kernel.org/pub/linux/kernel/people/tiwai/snapshot/
Sometime recently this has stopped working. I am doing:
./configure --with-debug=verbose --with-kernel=/lib/modules/2.6.32-23-generic/build
make
The make fails with:
make[3]: Leaving directory `/karmic/home/work/alsa/alsa-driver/usb/usx2y'
make[2]: Leaving directory `/karmic/home/work/alsa/alsa-driver/usb'
make[2]: Entering directory `/karmic/home/work/alsa/alsa-driver/pcmcia'
make[3]: Entering directory `/karmic/home/work/alsa/alsa-driver/pcmcia/pdaudiocf'
make[3]: Leaving directory `/karmic/home/work/alsa/alsa-driver/pcmcia/pdaudiocf'
make[3]: Entering directory `/karmic/home/work/alsa/alsa-driver/pcmcia/vx'
make[3]: Leaving directory `/karmic/home/work/alsa/alsa-driver/pcmcia/vx'
make[2]: Leaving directory `/karmic/home/work/alsa/alsa-driver/pcmcia'
make[2]: Entering directory `/karmic/home/work/alsa/alsa-driver/misc'
make[2]: Leaving directory `/karmic/home/work/alsa/alsa-driver/misc'
make[1]: Leaving directory `/karmic/home/work/alsa/alsa-driver'
make -C SUBDIRS=/karmic/home/work/alsa/alsa-driver CPP="gcc -E" CC="gcc" modules
make: *** SUBDIRS=/karmic/home/work/alsa/alsa-driver: No such file or directory. Stop.
make: *** [compile] Error 2
(The full build log can be found at: http://kernel.ubuntu.com/~bradf/build.log)
I would have expected this make invocation to have been:
make SUBDIRS=/karmic/home/work/alsa/alsa-driver CPP="gcc -E" CC="gcc" -C modules
However, I believe this has worked this way for quite a while so that is probably
not the issue. I'd be interested in looking into this further but I don't understand
how the daily snapshot is created nor where the build infrastructure files (configure, et.)
come from.
Brad
--
Brad Figg brad.figg@canonical.com http://www.canonical.com
next reply other threads:[~2010-06-16 22:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-16 22:05 Brad Figg [this message]
2010-06-22 23:15 ` Problems building the daily snapshot Brad Figg
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=4C194AA9.205@canonical.com \
--to=brad.figg@canonical.com \
--cc=alsa-devel@alsa-project.org \
/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.