From: David Ronis <ronis@ronispc.chem.mcgill.ca>
To: linux-kernel@vger.kernel.org
Subject: RE: Build Failure in 2.6.21
Date: Fri, 27 Apr 2007 14:42:43 -0400 [thread overview]
Message-ID: <1177699363.32236.15.camel@ronispc.chem.mcgill.ca> (raw)
I just found the problem--one of the patches was rejected. I patched by hand
(patch_realtek.c) and things now build. Now to see if it runs.
David
I've just tried to upgrade the kernel from 2.6.19.9 to 2.6.21. The
build dies in "make modules" at:
sound/pci/hda/patch_realtek.c:4174: error: array type has incomplete
element type
sound/pci/hda/patch_realtek.c:4175: error: field name not in record or
union initializer
sound/pci/hda/patch_realtek.c:4175: error: (near initialization for
'alc260_cfg_tbl')
sound/pci/hda/patch_realtek.c:4175: error: field name not in record or
union initializer
sound/pci/hda/patch_realtek.c:4175: error: (near initialization for
'alc260_cfg_tbl')
[lots more like the above].
sound/pci/hda/patch_realtek.c: In function 'patch_alc260':
sound/pci/hda/patch_realtek.c:4300: error: 'alc260_models' undeclared
(first use in this function)
sound/pci/hda/patch_realtek.c:4300: error: (Each undeclared identifier
is reported only once
sound/pci/hda/patch_realtek.c:4300: error: for each function it appears
in.)
make[3]: *** [sound/pci/hda/patch_realtek.o] Error 1
make[2]: *** [sound/pci/hda] Error 2
make[1]: *** [sound/pci] Error 2
make: *** [sound] Error 2
I'm on a i686, slackware-11.0 with gcc-4.1.2 box. Things built fine on
another box (albeit with a different sound card and hence driver
options).
Please CC me on any reply.
David
next reply other threads:[~2007-04-27 18:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 18:42 David Ronis [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-04-27 18:00 David Ronis
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=1177699363.32236.15.camel@ronispc.chem.mcgill.ca \
--to=ronis@ronispc.chem.mcgill.ca \
--cc=David.Ronis@McGill.CA \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®