Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@fs.tum.de>
To: alsa-devel@alsa-project.org
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: ALSA .text.exit compile errors in 2.5.14-dj2
Date: Thu, 9 May 2002 13:26:34 +0200 (CEST)	[thread overview]
Message-ID: <acqdom$e2q$2@main.gmane.org> (raw)

Hi,

while trying to compile a non-modular 2.5.14-dj2 kernel I got the
following ALSA-related .text.exit errors at the final linking:


<--  snip  -->

...
sound/sound.o: In function `snd_card_es968_probe':
sound/sound.o(.text.init+0x22222): undefined reference to `local symbols
in discarded section .text.exit'
sound/sound.o: In function `alsa_rme9652_mem_init':
sound/sound.o(.text.init+0x2b78a): undefined reference to `local symbols
in discarded section .text.exit'
sound/sound.o(.data+0x36fd4): undefined reference to `local symbols in
discarded section .text.exit'
...

<--  snip  -->

The problems are

In sound/isa/sb/es968.c:
snd_card_es968_probe isn't __exit (more exactly it's __init) but it calls
snd_card_es968_free that is __exit

In sound/pci/rme9652/rme9652_mem.c:
alsa_rme9652_mem_init isn't __exit (more exactly it's __init) but it calls
rme9652_free_buffers that is __exit


I'm not sure whether removing the __exit is the right solution or whether
there's a better solution.


cu
Adrian

-- 

You only think this is a free country. Like the US the UK spends a lot of
time explaining its a free country because its a police state.
								Alan Cox


_______________________________________________________________

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm

                 reply	other threads:[~2002-05-09 11:31 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='acqdom$e2q$2@main.gmane.org' \
    --to=bunk@fs.tum.de \
    --cc=alsa-devel@alsa-project.org \
    --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