From: WANG Cong <xiyou.wangcong@gmail.com>
To: Adrian Bunk <bunk@kernel.org>
Cc: WANG Cong <xiyou.wangcong@gmail.com>,
Sam Ravnborg <sam@ravnborg.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-kbuild@vger.kernel.org
Subject: Re: The latest linus tree can't build
Date: Sun, 27 Jan 2008 10:14:29 +0800 [thread overview]
Message-ID: <20080127021429.GA2495@hacking> (raw)
In-Reply-To: <20080126104514.GA18170@does.not.exist>
On Sat, Jan 26, 2008 at 12:45:14PM +0200, Adrian Bunk wrote:
>On Sat, Jan 26, 2008 at 06:38:45PM +0800, WANG Cong wrote:
>>
>> Hi, Sam!
>>
>> When I built the latest linus tree, I got this error:
>>
>> ...
>> CC sound/oss/msnd.o
>> make[2]: *** No rule to make target `/etc/sound/msndperm.bin', needed by `sound/oss/msndperm.c'. Stop.
>> make[1]: *** [sound/oss] Error 2
>> make: *** [sound] Error 2
>>
>> My .config is just the one I sent to you in another thread.
>>...
>
>It's expected that CONFIG_STANDALONE=n allows configurations that won't
>compile.
Oh, thank you!
prev parent reply other threads:[~2008-01-27 2:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-26 10:38 The latest linus tree can't build WANG Cong
2008-01-26 10:45 ` Adrian Bunk
2008-01-27 2:14 ` WANG Cong [this message]
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=20080127021429.GA2495@hacking \
--to=xiyou.wangcong@gmail.com \
--cc=bunk@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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.