From: Evgeny Polyakov <johnpol@2ka.mipt.ru>
To: linux-kernel@vger.kernel.org
Subject: esssound.o once more
Date: Fri, 10 Aug 2001 04:08:35 +0400 [thread overview]
Message-ID: <200108100008.f7A08Zl16648@www.2ka.mipt.ru> (raw)
Hello.
Some days ago problem with compiling esssound driver was erised.
And Alan Cox sad that in his -ac1 path this problem was solved, but....
Here is messages, that was occured while 2.4.7-ac9 was compiling:
drivers/sound/sounddrivers.o: In function `solo1_update_ptr':
drivers/sound/sounddrivers.o(.text+0xd6e): undefined reference to `clear_advance'
drivers/sound/sounddrivers.o: In function `solo1_write':
drivers/sound/sounddrivers.o(.text+0x2162): undefined reference to `prog_dmabuf_dac'
drivers/sound/sounddrivers.o: In function `solo1_poll':
drivers/sound/sounddrivers.o(.text+0x23b2): undefined reference to `prog_dmabuf_dac'
drivers/sound/sounddrivers.o: In function `solo1_mmap':
drivers/sound/sounddrivers.o(.text+0x2411): undefined reference to `prog_dmabuf_dac'
drivers/sound/sounddrivers.o: In function `solo1_ioctl':
drivers/sound/sounddrivers.o(.text+0x2902): undefined reference to `prog_dmabuf_dac'
drivers/sound/sounddrivers.o(.text+0x2b05): undefined reference to `prog_dmabuf_dac'
drivers/sound/sounddrivers.o(.text+0x2c38): more undefined references to `prog_dmabuf_dac' fol
And in -ac1 this messages appear once more.
But( I don't know how can I do this) I had compiled 2.4.7-ac1 some days ago with esssound support:
Linux Sombre.2ka.mipt.ru 2.4.7-ac1 #4 Fri Jul 27 06:17:13 MSD 2001 i686 unknown
but after it i can't do this once more.
Any suggestions, help and advices are wellcome :).
---
WBR. //s0mbre
next reply other threads:[~2001-08-10 0:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-10 0:08 Evgeny Polyakov [this message]
[not found] <no.id>
2001-08-10 0:22 ` esssound.o once more Alan Cox
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=200108100008.f7A08Zl16648@www.2ka.mipt.ru \
--to=johnpol@2ka.mipt.ru \
--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;
as well as URLs for NNTP newsgroup(s).