From: Takashi Iwai <tiwai@suse.de>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: latest git compile error in sound/drivers/opl3/opl3_synth.c
Date: Sun, 03 Feb 2008 10:10:27 +0100 [thread overview]
Message-ID: <s5hejbue77g.wl%tiwai@suse.de> (raw)
In-Reply-To: <47A55176.8050004@cn.fujitsu.com>
At Sun, 03 Feb 2008 13:30:30 +0800,
Li Zefan wrote:
>
>
> sound/drivers/opl3/opl3_synth.c: In function 'snd_opl3_find_patch':
> sound/drivers/opl3/opl3_synth.c:308: error: 'OPL3_PATCH_HASH_SIZE' undeclared (first use in this function)
> sound/drivers/opl3/opl3_synth.c:308: error: (Each undeclared identifier is reported only once
> sound/drivers/opl3/opl3_synth.c:308: error: for each function it appears in.)
> sound/drivers/opl3/opl3_synth.c:311: error: 'struct snd_opl3' has no member named 'patch_table'
> sound/drivers/opl3/opl3_synth.c:323: error: 'struct snd_opl3' has no member named 'patch_table'
> sound/drivers/opl3/opl3_synth.c:324: error: 'struct snd_opl3' has no member named 'patch_table'
> sound/drivers/opl3/opl3_synth.c: In function 'snd_opl3_clear_patches':
> sound/drivers/opl3/opl3_synth.c:335: error: 'OPL3_PATCH_HASH_SIZE' undeclared (first use in this function)
> sound/drivers/opl3/opl3_synth.c:337: error: 'struct snd_opl3' has no member named 'patch_table'
> sound/drivers/opl3/opl3_synth.c:342: error: 'struct snd_opl3' has no member named 'patch_table'
> sound/drivers/opl3/opl3_synth.c:342: error: 'struct snd_opl3' has no member named 'patch_table'
>
> seems it's caused by the following config options:
> # CONFIG_SND_SEQUENCER is not set
> CONFIG_SND_OPL3_LIB=m
Thanks, it's already fixed on ALSA tree for the next push.
http://lkml.org/lkml/2008/2/1/152
Takashi
prev parent reply other threads:[~2008-02-03 9:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-03 5:30 latest git compile error in sound/drivers/opl3/opl3_synth.c Li Zefan
2008-02-03 9:10 ` Takashi Iwai [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=s5hejbue77g.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.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