From: Paul Collins <paul@briny.ondioline.org>
To: johannes@sipsolutions.net
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: all-modular snd-aoa
Date: Fri, 23 Jun 2006 19:14:45 +1000 [thread overview]
Message-ID: <87hd2cz116.fsf@briny.internal.ondioline.org> (raw)
I get this when building from Linus's current git tree:
LD sound/built-in.o
ld: sound/aoa/built-in.o: No such file: No such file or directory
make[1]: *** [sound/built-in.o] Error 1
make: *** [sound] Error 2
Doing "touch sound/aoa/built-in.o" lets the build continue and
complete successfully.
--
Paul Collins
Melbourne, Australia
Dag vijandelijk luchtschip de huismeester is dood
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
WARNING: multiple messages have this Message-ID (diff)
From: Paul Collins <paul@briny.ondioline.org>
To: johannes@sipsolutions.net
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: all-modular snd-aoa
Date: Fri, 23 Jun 2006 19:14:45 +1000 [thread overview]
Message-ID: <87hd2cz116.fsf@briny.internal.ondioline.org> (raw)
I get this when building from Linus's current git tree:
LD sound/built-in.o
ld: sound/aoa/built-in.o: No such file: No such file or directory
make[1]: *** [sound/built-in.o] Error 1
make: *** [sound] Error 2
Doing "touch sound/aoa/built-in.o" lets the build continue and
complete successfully.
--
Paul Collins
Melbourne, Australia
Dag vijandelijk luchtschip de huismeester is dood
next reply other threads:[~2006-06-23 9:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-23 9:14 Paul Collins [this message]
2006-06-23 9:14 ` all-modular snd-aoa Paul Collins
2006-06-23 14:14 ` Johannes Berg
2006-06-23 14:14 ` Johannes Berg
2006-06-23 14:30 ` Takashi Iwai
2006-06-23 14:30 ` [Alsa-devel] " Takashi Iwai
2006-06-23 14:36 ` Johannes Berg
2006-06-23 14:36 ` [Alsa-devel] " Johannes Berg
2006-06-23 14:50 ` Takashi Iwai
2006-06-23 14:50 ` [Alsa-devel] " Takashi Iwai
2006-06-23 14:54 ` Johannes Berg
2006-06-23 14:54 ` [Alsa-devel] " Johannes Berg
2006-06-23 15:00 ` Takashi Iwai
2006-06-23 15:00 ` [Alsa-devel] " Takashi Iwai
2006-06-23 15:03 ` Johannes Berg
2006-06-23 15:03 ` [Alsa-devel] " Johannes Berg
2006-06-23 15:07 ` Paul Collins
2006-06-26 6:22 ` Johannes Berg
2006-06-26 6:22 ` [Alsa-devel] " Johannes Berg
2006-06-23 15:07 ` Paul Collins
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=87hd2cz116.fsf@briny.internal.ondioline.org \
--to=paul@briny.ondioline.org \
--cc=alsa-devel@alsa-project.org \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.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.