From: Keith Owens <kaos@ocs.com.au>
To: Bill Pringlemeir <bpringle@sympatico.ca>
Cc: "David S. Miller" <davem@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: [patch] 2.4.6-pre3 unresolved symbol do_softirq
Date: Thu, 14 Jun 2001 00:39:09 +1000 [thread overview]
Message-ID: <10690.992443149@ocs4.ocs-net> (raw)
In-Reply-To: Your message of "13 Jun 2001 10:31:22 -0400." <m2zobcxxhh.fsf@sympatico.ca>
On 13 Jun 2001 10:31:22 -0400,
Bill Pringlemeir <bpringle@sympatico.ca> wrote:
>Try ye' olde STRINGIFY and string concatenation? Well, at least I try...
>
> #define my_symbol my_symbol_versioned
> #define STRINGIFY(a) STRINGIFY1(a)
> #define STRINGIFY1(a) #a
> extern void my_symbol(void);
>
> void foo(void)
> {
> __asm__("call " STRINGIFY(my_symbol) "\n");
> }
>
> [bpringle@localhost bpringle]$ gcc -o x x.c
> /usr/lib/crt1.o(.text+0x18): undefined reference to `main'
> /tmp/ccIj9Cit.o: In function `foo':
> /tmp/ccIj9Cit.o(.text+0x4): undefined reference to `my_symbol_versioned'
Only at the cost of polluting every .h file that calls a symbol from
__asm__. The whole pre-processor kludge for symbol versions goes away
in 2.5 so live with _novers for now.
next prev parent reply other threads:[~2001-06-13 14:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-13 12:07 [patch] 2.4.6-pre3 unresolved symbol do_softirq Keith Owens
2001-06-13 12:13 ` David S. Miller
2001-06-13 13:48 ` Jeff Garzik
2001-06-13 14:03 ` Keith Owens
2001-06-13 14:06 ` David S. Miller
2001-06-13 14:11 ` Keith Owens
2001-06-13 14:15 ` David S. Miller
2001-06-13 14:37 ` Keith Owens
2001-06-13 13:58 ` Keith Owens
2001-06-13 13:58 ` David S. Miller
2001-06-13 14:01 ` David S. Miller
2001-06-13 14:09 ` Keith Owens
2001-06-13 14:31 ` Bill Pringlemeir
2001-06-13 14:39 ` Keith Owens [this message]
2001-06-13 14:21 ` David S. Miller
2001-06-13 14:37 ` Andrew Morton
2001-06-13 14:44 ` Andreas Schwab
2001-06-13 14:53 ` Russell King
2001-06-13 14:52 ` Russell King
2001-06-13 14:55 ` David S. Miller
2001-06-13 16:39 ` Keith Owens
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=10690.992443149@ocs4.ocs-net \
--to=kaos@ocs.com.au \
--cc=bpringle@sympatico.ca \
--cc=davem@redhat.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;
as well as URLs for NNTP newsgroup(s).