From: Joe <joeja@mindspring.com>
To: linux-kernel@vger.kernel.org
Subject: emu10k1.o and 2.4.8 don't compile
Date: Sat, 11 Aug 2001 21:21:55 -0700 [thread overview]
Message-ID: <3B760463.4A4E0CC9@mindspring.com> (raw)
I have a SB LIve sound card and now I cannot compile the emu10k soudn
driver to run it in 2.2.8.
Apparantly someone defined MODULE_AUTHOR, MODULE_DESCRIPTION,
init_module and cleanup_module in both the main.c and joystick.c files
not sure what else is defined twice either.
I think I can just comment out one definition / function but not sure
which one. Does anyone know or has anyone seen this yet?
I patch a 2.4.7 kernel with the patch from ftp.kernel.org.
Joe (cc me I am not on the list)
The following is the compiler message:
main.o(.modinfo+0x20): multiple definition of `__module_author'
joystick.o(.modinfo+0x80): first defined here
ld: Warning: size of symbol `__module_author' changed from 67 to 81 in
main.o
main.o(.modinfo+0x80): multiple definition of `__module_description'
joystick.o(.modinfo+0xe0): first defined here
ld: Warning: size of symbol `__module_description' changed from 83 to 96
in main.o
main.o: In function `init_module':
main.o(.text+0x1a70): multiple definition of `init_module'
joystick.o(.text+0x2d0): first defined here
main.o: In function `cleanup_module':
main.o(.text+0x1ab0): multiple definition of `cleanup_module'
joystick.o(.text+0x310): first defined here
make[3]: *** [emu10k1.o] Error 1
make[2]: *** [_modsubdir_emu10k1] Error 2
make[1]: *** [_modsubdir_sound] Error 2
make: *** [_mod_drivers] Error 2
cp: cannot stat `emu10k1.o': No such file or directory
make[3]: *** [_modinst__] Error 1
make[2]: *** [_modinst_emu10k1] Error 2
make[1]: *** [_modinst_sound] Error 2
make: *** [_modinst_drivers] Error 2
reply other threads:[~2001-08-12 4:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3B760463.4A4E0CC9@mindspring.com \
--to=joeja@mindspring.com \
--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